notifications  

Messages by Thread

• (apisix-ingress-controller) branch v2.0.0 updated: chore: unified logger print (#2456) alinsran
• (apisix-ingress-controller) branch master updated: fix: should not contain plaintext token in log message. (#2462) alinsran
• [PR] feat: add a global switch to disable upstream health check [apisix] via GitHub
  • Re: [PR] feat: add a global switch to disable upstream health check [apisix] via GitHub
  • Re: [PR] feat: add a global switch to disable upstream health check [apisix] via GitHub
  • Re: [PR] feat: add a global switch to disable upstream health check [apisix] via GitHub
  • Re: [PR] feat: add a global switch to disable upstream health check [apisix] via GitHub
• (apisix-dashboard) branch dependabot/github_actions/apache/skywalking-eyes-049742de2276515409e3109ca2a91934053e080d created (now 8c53d3e1c) github-bot
• (apisix-dashboard) branch dependabot/github_actions/apache/skywalking-eyes-a62f574f0eb113e306a860014d7ce38aea00f78d deleted (was 47939d68d) github-bot
• [PR] chore(deps): bump apache/skywalking-eyes from 9f0a5c0571ed1a0c13a16808cd8f59bc22f03883 to 049742de2276515409e3109ca2a91934053e080d [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump apache/skywalking-eyes from 9f0a5c0571ed1a0c13a16808cd8f59bc22f03883 to 049742de2276515409e3109ca2a91934053e080d [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump apache/skywalking-eyes from 9f0a5c0571ed1a0c13a16808cd8f59bc22f03883 to 049742de2276515409e3109ca2a91934053e080d [apisix-dashboard] via GitHub
• Re: [I] help request: Need to download the offline version of Apisix 3.2.2 [apisix] via GitHub
• [PR] chore(ci): remove add-pr-comment step [apisix-ingress-controller] via GitHub
  • Re: [PR] chore(ci): remove add-pr-comment step [apisix-ingress-controller] via GitHub
• [PR] chore: should not contain plaintext token in log message. [apisix-ingress-controller] via GitHub
  • Re: [PR] chore: should not contain plaintext token in log message. [apisix-ingress-controller] via GitHub
  • Re: [PR] chore: should not contain plaintext token in log message. [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: should not contain plaintext token in log message. [apisix-ingress-controller] via GitHub
• [PR] fix(request-validation): support Content-Type header with charset for urlencoded data [apisix] via GitHub
  • Re: [PR] fix(request-validation): support Content-Type header with charset for urlencoded data [apisix] via GitHub
• (apisix-ingress-controller) branch chore/fix_adc_log created (now 581f1fe0) ronething
• (apisix) branch master updated: revert: fix: forward-auth request body too large (#12404) ashishtiwari
• [PR] chore: adcConfig implemenet marshalJSON for security reason [apisix-ingress-controller] via GitHub
  • Re: [PR] chore: adcConfig implemenet marshalJSON for security reason [apisix-ingress-controller] via GitHub
  • Re: [PR] chore: should not contain plaintext token in log message. [apisix-ingress-controller] via GitHub
• (apisix) branch master updated: feat: support multiple json.delay_encode objects in single log (#12395) ashishtiwari
• [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
  • Re: [PR] feat: add support for extra_headers in forward-auth plugin [apisix] via GitHub
• (apisix-ingress-controller) branch v2.0.0 updated: feat: add synchronization status to CRD (#2460) alinsran
• (apisix-ingress-controller) branch feat/add-sync-status deleted (was be490d55) alinsran
• (apisix-ingress-controller) branch master updated: feat: add synchronization status to CRD (#2460) alinsran
• [PR] chore: remove empty lines from configmap [apisix-helm-chart] via GitHub
  • Re: [PR] chore: remove empty lines from configmap [apisix-helm-chart] via GitHub
• (apisix-ingress-controller) branch feat/add-sync-status updated (11364316 -> be490d55) alinsran
• [PR] revert: fix: forward-auth request body too large [apisix] via GitHub
  • Re: [PR] revert: fix: forward-auth request body too large [apisix] via GitHub
• (apisix-ingress-controller) branch feat/add-sync-status updated (88f42d67 -> 11364316) alinsran
• (apisix) branch master updated (4dc0a067b -> 518d86fc7) traky
• [PR] fix: zipkin trace_id and span_id format in ngx_var [apisix] via GitHub
  • Re: [PR] fix: zipkin trace_id and span_id format in ngx_var [apisix] via GitHub
• (apisix-website) branch SkyeYoung-patch-2 updated (88be46df2df -> 9b103893861) young
• [I] bug: openelemetry set_ngx_var option causes errors [apisix] via GitHub
  • Re: [I] bug: openelemetry set_ngx_var option causes errors [apisix] via GitHub
  • Re: [I] bug: openelemetry set_ngx_var option causes errors [apisix] via GitHub
  • Re: [I] bug: openelemetry set_ngx_var option causes errors [apisix] via GitHub
• (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
  • 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

• Earlier messages
• Later messages