notifications  

Messages by Thread

• (apisix-ingress-controller) branch v2.0.0 updated (43bbe768 -> df2362b0) alinsran
  • (apisix-ingress-controller) 03/03: doc: add getting-started doc (#2450) alinsran
  • (apisix-ingress-controller) 02/03: fix: reduce the complexity of calculating route priority (#2459) alinsran
  • (apisix-ingress-controller) 01/03: fix: adc backend server on different mode (#2455) alinsran
• (apisix-ingress-controller) branch v2.0.0 updated (18f03ea6 -> 43bbe768) alinsran
  • (apisix-ingress-controller) 04/04: fix: apisixroute backend service reference to apisixupstream (#2453) alinsran
  • (apisix-ingress-controller) 02/04: fix: a failing endpoint shouldn't affect others (#2452) alinsran
  • (apisix-ingress-controller) 03/04: fix: config not provided should not be retried (#2454) alinsran
  • (apisix-ingress-controller) 01/04: fix: support filter endpoint when translate backend ref. (#2451) alinsran
• (apisix-ingress-controller) branch v2.0.0 updated (63522639 -> 18f03ea6) alinsran
  • (apisix-ingress-controller) 02/03: chore: Update artifact and report names with provider type (#2447) alinsran
  • (apisix-ingress-controller) 01/03: feat(ci): support build dev image (#2448) alinsran
  • (apisix-ingress-controller) 03/03: fix: add more event filter across controllers (#2449) alinsran
• (apisix-ingress-controller) branch v2.0.0 updated: feat: gatewayproxy controller (#2444) alinsran
• (apisix-ingress-controller) branch master updated: doc: add getting-started doc (#2450) alinsran
• Re: [I] request help: 使用mock etcd后发现会定期出现etcdserver: duplicate key given in txn reques的报错 [apisix-ingress-controller] via GitHub
• Re: [I] request help: 如果service包含多个端口，但是apisixroute的backends并没有指定该service的全部端口时，apisixupstream会出现NotFound的报错 [apisix-ingress-controller] via GitHub
• Re: [I] request help: 我发现对apisix cr的删除没有做幂等处理。也就是如果收到多个删除事件，会出现一直删除报错的日志和k8s事件。 [apisix-ingress-controller] via GitHub
• Re: [I] APISIX Consumer Naming Conflict with Hyphenated Namespaces [apisix-ingress-controller] via GitHub
• Re: [I] bug: Using the EKS quickstart creates the `apisix-gateway` service of type: NodePort instead of type: LoadBalancer [apisix-ingress-controller] via GitHub
  • Re: [I] bug: Using the EKS quickstart creates the `apisix-gateway` service of type: NodePort instead of type: LoadBalancer [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch feat/add-sync-status updated (f4e3e183 -> 88f42d67) alinsran
• Re: [PR] fix: release checker when nodes are nil [apisix] via GitHub
• Re: [PR] feat: support lua proxy upstream [apisix] via GitHub
• (apisix-ingress-controller) branch feat/add-sync-status updated (b2c608a8 -> 30e7cfeb) alinsran
• (apisix-ingress-controller) branch feat/add-sync-status updated (6487d2a0 -> b2c608a8) alinsran
• (apisix-ingress-controller) branch feat/add-sync-status updated (502cfe41 -> 6487d2a0) alinsran
• (apisix-ingress-controller) branch feat/add-sync-status updated (ba1a7d08 -> 502cfe41) alinsran
• (apisix-ingress-controller) branch feat/add-sync-status updated (bfd82c77 -> ba1a7d08) alinsran
• (apisix-ingress-controller) branch feat/add-sync-status updated (3f348b8a -> bfd82c77) alinsran
• (apisix-ingress-controller) branch feat/add-sync-status created (now 321dd242) alinsran
  • (apisix-ingress-controller) 01/01: feat: add synchronization status to CRD alinsran
• (apisix-ingress-controller) branch feat/add-sync-status updated (321dd242 -> 3f348b8a) alinsran
• [PR] feat: add synchronization status to CRD [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: add synchronization status to CRD [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: add synchronization status to CRD [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: add synchronization status to CRD [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: add synchronization status to CRD [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: add synchronization status to CRD [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: add synchronization status to CRD [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: add synchronization status to CRD [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: add synchronization status to CRD [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: add synchronization status to CRD [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: add synchronization status to CRD [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: add synchronization status to CRD [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: add synchronization status to CRD [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: add synchronization status to CRD [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: add synchronization status to CRD [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch master updated: fix: reduce the complexity of calculating route priority (#2459) ronething
• (apisix-ingress-controller) branch fix/route_pro_calc deleted (was 1d7027fb) ronething
• (apisix-ingress-controller) branch master updated: chore: unified logger print (#2456) ronething
• Re: [PR] fix: consumer key duplication check [apisix] via GitHub
• (apisix-ingress-controller) branch fix/route_pro_calc created (now 1d7027fb) ronething
• [PR] fix: reduce the complexity of calculating route priority [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: reduce the complexity of calculating route priority [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: reduce the complexity of calculating route priority [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: reduce the complexity of calculating route priority [apisix-ingress-controller] via GitHub
• [PR] fix: the problem that the method WaitControllerManagerLog dose not work [apisix-ingress-controller] via GitHub
• [PR] fix: calculate HTTPRoute Priority [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: reduce the complexity of calculating route priority [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch master updated: fix: adc backend server on different mode (#2455) ronething
• [PR] chore: unified logger print [apisix-ingress-controller] via GitHub
  • Re: [PR] chore: unified logger print [apisix-ingress-controller] via GitHub
  • Re: [PR] chore: unified logger print [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch master updated: fix: config not provided should not be retried (#2454) alinsran
• [PR] docs: correct minor typo for openwhisk [apisix] via GitHub
  • Re: [PR] docs: correct minor typo for openwhisk [apisix] via GitHub
• [I] docs: fix typo in openwhisk plugin docs [apisix] via GitHub
  • Re: [I] docs: fix typo in openwhisk plugin docs [apisix] via GitHub
• [I] [Site]: [apisix-website] via GitHub
  • Re: [I] [Site]: 404 Not Found for section of the site APISIX Ingress Controller for Kubernete [apisix-website] via GitHub
  • Re: [I] [Site]: 404 Not Found for section of the site APISIX Ingress Controller for Kubernete [apisix-website] via GitHub
  • [I] [Site]: [apisix-website] via GitHub
  • Re: [I] [Site]: [apisix-website] via GitHub
• (apisix-ingress-controller) branch master updated: fix: a failing endpoint shouldn't affect others (#2452) alinsran
• [PR] fix: adc backend server on different mode [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: adc backend server on different mode [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: adc backend server on different mode [apisix-ingress-controller] via GitHub
• [PR] fix: config not provided should not be retried [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: config not provided should not be retried [apisix-ingress-controller] via GitHub
• [PR] fix: apisixroute backend service reference to apisixupstream [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: apisixroute backend service reference to apisixupstream [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: apisixroute backend service reference to apisixupstream [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: apisixroute backend service reference to apisixupstream [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch master updated (83811134 -> ebdafea9) ronething
• [PR] fix: a failing endpoint shouldn't affect others [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: a failing endpoint shouldn't affect others [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch master updated: fix: add more event filter across controllers (#2449) ronething
• (apisix) branch master updated: docs: update changelog with breakchange notices (#12396) sunyi
• [PR] fix: skip terminating endpoint [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: skip terminating endpoint [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: skip terminating endpoint [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: support filter endpoint when translate backend ref. [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: support filter endpoint when translate backend ref. [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: support filter endpoint when translate backend ref. [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: support filter endpoint when translate backend ref. [apisix-ingress-controller] via GitHub
• [I] help request: Register custom variable via external Java plugin [apisix] via GitHub
  • Re: [I] help request: Register custom variable via external Java plugin [apisix] via GitHub
  • Re: [I] help request: Register custom variable via external Java plugin [apisix] via GitHub
  • Re: [I] help request: Register custom variable via external Java plugin [apisix] via GitHub
  • Re: [I] help request: Register custom variable via external Java plugin [apisix] via GitHub
• [PR] doc: add getting-started doc [apisix-ingress-controller] via GitHub
  • Re: [PR] doc: add getting-started doc [apisix-ingress-controller] via GitHub
  • Re: [PR] doc: add getting-started doc [apisix-ingress-controller] via GitHub
  • Re: [PR] doc: add getting-started doc [apisix-ingress-controller] via GitHub
  • Re: [PR] doc: add getting-started doc [apisix-ingress-controller] via GitHub
  • Re: [PR] doc: add getting-started doc [apisix-ingress-controller] via GitHub
  • Re: [PR] doc: add getting-started doc [apisix-ingress-controller] via GitHub
• [PR] fix: ApisixRoute controller watch annotation change [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: add more event filter across controllers [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: add more event filter across controllers [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: add more event filter across controllers [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: add more event filter across controllers [apisix-ingress-controller] via GitHub
• [I] [Site]: apisix route docs link broken [apisix-website] via GitHub
  • Re: [I] [Site]: apisix route docs link broken [apisix-website] via GitHub
  • Re: [I] [Site]: apisix route docs link broken [apisix-website] via GitHub
  • Re: [I] [Site]: apisix route docs link broken [apisix-website] via GitHub
• [I] bug: 503 errors occur after restarting APISIX when using Consul and APISIX both in Docker [apisix] via GitHub
  • Re: [I] bug: 503 errors occur after restarting APISIX when using Consul and APISIX both in Docker [apisix] via GitHub
  • Re: [I] bug: 503 errors occur after restarting APISIX when using Consul and APISIX both in Docker [apisix] via GitHub
  • Re: [I] bug: 503 errors occur after restarting APISIX when using Consul and APISIX both in Docker [apisix] via GitHub
  • Re: [I] bug: 503 errors occur after restarting APISIX when using Consul and APISIX both in Docker [apisix] via GitHub
  • Re: [I] bug: 503 errors occur after restarting APISIX when using Consul and APISIX both in Docker [apisix] via GitHub
  • Re: [I] bug: 503 errors occur after restarting APISIX when using Consul and APISIX both in Docker [apisix] via GitHub
  • Re: [I] bug: 503 errors occur after restarting APISIX when using Consul and APISIX both in Docker [apisix] via GitHub
  • Re: [I] bug: 503 errors occur after restarting APISIX when using Consul and APISIX both in Docker [apisix] via GitHub
  • Re: [I] bug: 503 errors occur after restarting APISIX when using Consul and APISIX both in Docker [apisix] via GitHub
  • Re: [I] bug: 503 errors occur after restarting APISIX when using Consul and APISIX both in Docker [apisix] via GitHub
• [I] help request: How to access the new dashboard after upgrading to APISIX v3.13.0? [apisix] via GitHub
  • Re: [I] help request: How to access the new dashboard after upgrading to APISIX v3.13.0? [apisix] via GitHub
  • Re: [I] help request: How to access the new dashboard after upgrading to APISIX v3.13.0? [apisix] via GitHub
  • Re: [I] help request: How to access the new dashboard after upgrading to APISIX v3.13.0? [apisix] via GitHub
  • Re: [I] help request: How to access the new dashboard after upgrading to APISIX v3.13.0? [apisix] via GitHub
  • Re: [I] help request: How to access the new dashboard after upgrading to APISIX v3.13.0? [apisix] via GitHub
• (apisix-helm-chart) branch master updated: chore: support standalone (#839) nic443
• (apisix-helm-chart) tag apisix-2.11.1 created (now 86013d0) github-bot
• (apisix-ingress-controller) branch master updated: chore: Update artifact and report names with provider type (#2447) ronething
• (apisix-ingress-controller) branch master updated: feat(ci): support build dev image (#2448) ronething
• [PR] feat(ci): support build dev image [apisix-ingress-controller] via GitHub
  • Re: [PR] feat(ci): support build dev image [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch master updated: feat: gatewayproxy controller (#2444) ronething
• (apisix-helm-chart) tag apisix-ingress-controller-1.0.1 created (now e511431) github-bot
• (apisix-helm-chart) branch master updated: refactor: update CRD and deployment configurations (#842) alinsran
• [PR] docs: update changelog with brekchange notices [apisix] via GitHub
  • Re: [PR] docs: update changelog with breakchange notices [apisix] via GitHub
  • Re: [PR] docs: update changelog with breakchange notices [apisix] via GitHub
• [PR] chore: Update artifact and report names with provider type [apisix-ingress-controller] via GitHub
  • Re: [PR] chore: Update artifact and report names with provider type [apisix-ingress-controller] via GitHub
• [PR] refactor: update CRD and deployment configurations [apisix-helm-chart] via GitHub
  • Re: [PR] refactor: update CRD and deployment configurations [apisix-helm-chart] via GitHub
• [I] [Docs]: Ingress-controller docs 404 [apisix-website] via GitHub
  • Re: [I] [Docs]: Ingress-controller docs 404 [apisix-website] via GitHub
• (apisix-ingress-controller) branch doc/fix-doc-description-error updated (915b4e25 -> 5ec272a2) alinsran
• (apisix-ingress-controller) branch v2.0.0 updated (66e87fcf -> 40a2d2c7) alinsran
  • (apisix-ingress-controller) 02/02: doc: add config.json (#2446) alinsran
  • (apisix-ingress-controller) 01/02: docs: add install and developer-guide doc (#2439) alinsran
• (apisix-ingress-controller) branch doc-config-json deleted (was a511e63f) alinsran
• (apisix-ingress-controller) branch master updated (e9ae56be -> b46332cb) alinsran
• [PR] feat: support multiple json.delay_encode objects in single log [apisix] via GitHub
  • Re: [PR] feat: support multiple json.delay_encode objects in single log [apisix] via GitHub
• (apisix-ingress-controller) branch doc/add-guide deleted (was 8aa14a5c) alinsran
• (apisix-ingress-controller) branch doc-config-json updated (a22682e0 -> a511e63f) alinsran
• (apisix-ingress-controller) branch master updated: docs: add install and developer-guide doc (#2439) alinsran
• [PR] doc: add config.json [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch doc-config-json created (now df1d67b3) alinsran
  • (apisix-ingress-controller) 01/01: doc: add config.json alinsran
• [PR] fix: add etcd auto compaction env [apisix-helm-chart] via GitHub
  • Re: [PR] fix: add etcd auto compaction env [apisix-helm-chart] via GitHub
  • Re: [PR] fix: add etcd auto compaction env [apisix-helm-chart] via GitHub
  • Re: [PR] fix: add etcd auto compaction env [apisix-helm-chart] via GitHub
  • Re: [PR] fix: add etcd auto compaction env [apisix-helm-chart] via GitHub
  • Re: [PR] fix: add etcd auto compaction env [apisix-helm-chart] via GitHub
  • Re: [PR] fix: add etcd auto compaction env [apisix-helm-chart] via GitHub
• Re: [PR] feat: allow to use environment variables for openid-connect plugin [apisix] via GitHub
  • Re: [PR] feat: allow to use environment variables for openid-connect plugin [apisix] via GitHub
  • Re: [PR] feat: allow to use environment variables for openid-connect plugin [apisix] via GitHub
  • Re: [PR] feat: allow to use environment variables for openid-connect plugin [apisix] via GitHub
  • Re: [PR] feat: allow to use environment variables for openid-connect plugin [apisix] via GitHub
  • Re: [PR] feat: allow to use environment variables for openid-connect plugin [apisix] via GitHub
  • Re: [PR] feat: allow to use environment variables for openid-connect plugin [apisix] via GitHub
  • Re: [PR] feat: allow to use environment variables for openid-connect plugin [apisix] via GitHub
  • Re: [PR] feat: allow to use environment variables for openid-connect plugin [apisix] via GitHub
  • Re: [PR] feat: allow to use environment variables for openid-connect plugin [apisix] via GitHub
  • Re: [PR] feat: allow to use environment variables for openid-connect plugin [apisix] via GitHub
  • Re: [PR] feat: allow to use environment variables for openid-connect plugin [apisix] via GitHub
  • Re: [PR] feat: allow to use environment variables for openid-connect plugin [apisix] via GitHub
  • Re: [PR] feat: allow to use environment variables for openid-connect plugin [apisix] via GitHub
  • Re: [PR] feat: allow to use environment variables for openid-connect plugin [apisix] via GitHub
• Re: [PR] feat: use custom auth header name [apisix] via GitHub
• (apisix) branch master updated (ff8c350a3 -> 178bc98dd) baoyuan
• (apisix-ingress-controller) branch v2.0.0 updated (bb378f8d -> 66e87fcf) alinsran
  • (apisix-ingress-controller) 01/04: chore: move doc to en/latest directory (#2443) alinsran
  • (apisix-ingress-controller) 03/04: chore: move generate-crd to assets (#2445) alinsran
  • (apisix-ingress-controller) 04/04: docs: remove unless commit in changelog 200-rc1 (#2441) alinsran
• (apisix-ingress-controller) branch doc/fix-200-rc1-changelog deleted (was c1ba71ed) alinsran
• (apisix-ingress-controller) branch master updated: docs: remove unless commit in changelog 200-rc1 (#2441) alinsran
• (apisix-ingress-controller) branch master updated: chore: move generate-crd to assets (#2445) alinsran
• (apisix-ingress-controller) branch chore/move-gen-crd-doc-dir deleted (was 7b5755dd) alinsran
• [PR] chore: move generate-crd to assets [apisix-ingress-controller] via GitHub
  • Re: [PR] chore: move generate-crd to assets [apisix-ingress-controller] via GitHub

• Earlier messages
• Later messages