notifications  

Messages by Thread

• • Re: [PR] fix: typos in k8s discovery code [apisix] via GitHub
  • Re: [PR] fix: typos in k8s discovery code [apisix] via GitHub
  • Re: [PR] fix: typos in k8s discovery code [apisix] via GitHub
• Re: [I] Migrate from Bitnami etcd images - no longer freely available [apisix-docker] via GitHub
  • Re: [I] Migrate from Bitnami etcd images - no longer freely available [apisix-docker] via GitHub
  • Re: [I] Migrate from Bitnami etcd images - no longer freely available [apisix-docker] via GitHub
• [PR] docs: update apisix ingress controller docs helm repo [apisix-ingress-controller] via GitHub
  • Re: [PR] docs: update apisix ingress controller docs helm repo [apisix-ingress-controller] via GitHub
• (apisix-helm-chart) branch gh-pages updated: change repo url traky
• (apisix-ingress-controller) branch docs-repo created (now a5f41cf0) traky
  • (apisix-ingress-controller) 01/01: change aic helm repo traky
• Re: [I] APISIX Dashboard Tests [apisix-dashboard] via GitHub
  • Re: [I] APISIX Dashboard Tests [apisix-dashboard] via GitHub
  • Re: [I] APISIX Dashboard Tests [apisix-dashboard] via GitHub
  • Re: [I] APISIX Dashboard Tests [apisix-dashboard] via GitHub
  • Re: [I] APISIX Dashboard Tests [apisix-dashboard] via GitHub
• [I] help request: Is the support for the Kubernetes Gateway API in the latest GA release (1.8) of the apisix-ingress-controller still not GA-ready? If not, are there any plans for it in the future? [apisix] via GitHub
• Re: [I] Test(resource): consumer groups [apisix-dashboard] via GitHub
  • Re: [I] Test(resource): consumer groups [apisix-dashboard] via GitHub
• [PR] test: add E2E tests for Consumer Groups (#3086) [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for Consumer Groups (#3086) [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for Consumer Groups (#3086) [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for Consumer Groups [apisix-dashboard] via GitHub
• Re: [I] Test(resource): ssls [apisix-dashboard] via GitHub
  • Re: [I] Test(resource): ssls [apisix-dashboard] via GitHub
• [PR] test: add E2E tests for SSLs (#3087) [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for SSLs (#3087) [apisix-dashboard] via GitHub
• [I] upstream resolve domain is empty [apisix] via GitHub
  • Re: [I] upstream resolve domain is empty [apisix] via GitHub
  • Re: [I] upstream resolve domain is empty [apisix] via GitHub
  • Re: [I] upstream resolve domain is empty [apisix] via GitHub
• [I] [Site]: 404 when clicking on ingress-controller from docs page. [apisix-website] via GitHub
  • Re: [I] [Site]: 404 when clicking on ingress-controller from docs page. [apisix-website] via GitHub
  • Re: [I] [Site]: 404 when clicking on ingress-controller from docs page. [apisix-website] via GitHub
  • Re: [I] [Site]: 404 when clicking on ingress-controller from docs page. [apisix-website] via GitHub
• [I] help request: Unable to request embedded dashboard interface [apisix] via GitHub
  • Re: [I] help request: Unable to request embedded dashboard interface [apisix] via GitHub
  • Re: [I] help request: Unable to request embedded dashboard interface [apisix] via GitHub
  • Re: [I] help request: Unable to request embedded dashboard interface [apisix] via GitHub
  • Re: [I] help request: Unable to request embedded dashboard interface [apisix] via GitHub
• Re: [PR] refactor(common): supplement missing chinese i18n translations [apisix-dashboard] via GitHub
  • Re: [PR] refactor(common): supplement missing chinese i18n translations [apisix-dashboard] via GitHub
  • Re: [PR] refactor(common): supplement missing chinese i18n translations [apisix-dashboard] via GitHub
• Re: [I] dashboard cannot encrypt password field [apisix-dashboard] via GitHub
  • Re: [I] dashboard cannot encrypt password field [apisix-dashboard] via GitHub
  • Re: [I] dashboard cannot encrypt password field [apisix-dashboard] via GitHub
• Re: [I] feat: about the stream routes button error report page in new dashboard [apisix-dashboard] via GitHub
• Re: [I] feat: As konws, we already supports ocsp-staping, but have not option on built-in dashboard when add / update a SSL Cert, so than can we add a option on dashboard? [apisix] via GitHub
  • Re: [I] feat: As konws, we already supports ocsp-staping, but have not option on built-in dashboard when add / update a SSL Cert, so than can we add a option on dashboard? [apisix] via GitHub
• [I] feat: As a user, I want to use clientset, informers for Apisix resources in 2.0 [apisix-ingress-controller] via GitHub
  • Re: [I] feat: As a user, I want to use clientset, informers for Apisix resources in 2.0 [apisix-ingress-controller] via GitHub
  • Re: [I] feat: As a user, I want to use clientset, informers for Apisix resources in 2.0 [apisix-ingress-controller] via GitHub
  • Re: [I] feat: As a user, I want to use clientset, informers for Apisix resources in 2.0 [apisix-ingress-controller] via GitHub
  • Re: [I] feat: As a user, I want to use clientset, informers for Apisix resources in 2.0 [apisix-ingress-controller] via GitHub
• Re: [I] Hope "forward auth" can set cache time，and, Options requests can be approved [apisix] via GitHub
• Re: [I] Pulling images from secured/non-public repositories from apisix-ingress-controller helm chart [apisix-helm-chart] via GitHub
  • Re: [I] Pulling images from secured/non-public repositories from apisix-ingress-controller helm chart [apisix-helm-chart] via GitHub
• [I] help request: After the consumer creates and associates the plugin, the code retrieves the consumer as empty based on the plugin [apisix] via GitHub
  • Re: [I] help request: After the consumer creates and associates the plugin, the code retrieves the consumer as empty based on the plugin [apisix] via GitHub
  • [I] help request: After the consumer creates and associates the plugin, the code retrieves the consumer as empty based on the plugin [apisix] via GitHub
  • Re: [I] help request: After the consumer creates and associates the plugin, the code retrieves the consumer as empty based on the plugin [apisix] via GitHub
• [I] help request: Dynamic Upstream Routing [apisix] via GitHub
  • Re: [I] help request: Dynamic Upstream Routing [apisix] via GitHub
  • Re: [I] help request: Dynamic Upstream Routing [apisix] via GitHub
• [I] bug: Consumer creates and selects the key-auth plugin to submit a front-end error [apisix] via GitHub
  • Re: [I] bug: Consumer creates and selects the key-auth plugin to submit a front-end error [apisix] via GitHub
  • Re: [I] bug: Consumer creates and selects the key-auth plugin to submit a front-end error [apisix] via GitHub
• Re: [I] Test(resource): global rules [apisix-dashboard] via GitHub
  • Re: [I] Test(resource): global rules [apisix-dashboard] via GitHub
• [PR] test: add E2E tests for global rules (#3088) [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for global rules [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for global rules [apisix-dashboard] via GitHub
• Re: [I] Test(resource): plugin metadata [apisix-dashboard] via GitHub
  • Re: [I] Test(resource): plugin metadata [apisix-dashboard] via GitHub
• [PR] test: add E2E tests for plugin metadata resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for plugin metadata resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for plugin metadata resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for plugin metadata resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for plugin metadata resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for plugin metadata resource [apisix-dashboard] via GitHub
• Re: [I] Test(resource): plugin configs [apisix-dashboard] via GitHub
  • Re: [I] Test(resource): plugin configs [apisix-dashboard] via GitHub
• [PR] test: add comprehensive E2E tests for plugin configs. [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for plugin configs [apisix-dashboard] via GitHub
• [I] help request: The custom directory development plugin fails to load consistently even after modifying the configuration and restarting the service/application. [apisix] via GitHub
  • Re: [I] help request: The custom directory development plugin fails to load consistently even after modifying the configuration and restarting the service/application. [apisix] via GitHub
  • Re: [I] help request: The custom directory development plugin fails to load consistently even after modifying the configuration and restarting the service/application. [apisix] via GitHub
  • Re: [I] help request: The custom directory development plugin fails to load consistently even after modifying the configuration and restarting the service/application. [apisix] via GitHub
  • Re: [I] help request: The custom directory development plugin fails to load consistently even after modifying the configuration and restarting the service/application. [apisix] via GitHub
  • Re: [I] help request: The custom directory development plugin fails to load consistently even after modifying the configuration and restarting the service/application. [apisix] via GitHub
  • Re: [I] help request: The custom directory development plugin fails to load consistently even after modifying the configuration and restarting the service/application. [apisix] via GitHub
• Re: [PR] docs: store secrets in vault [apisix] via GitHub
  • Re: [PR] docs: store secrets in vault [apisix] via GitHub
  • Re: [PR] docs: store secrets in vault [apisix] via GitHub
  • Re: [PR] docs: store secrets in vault [apisix] via GitHub
  • Re: [PR] docs: store secrets in vault [apisix] via GitHub
  • Re: [PR] docs: store secrets in vault [apisix] via GitHub
  • Re: [PR] docs: store secrets in vault [apisix] via GitHub
• Re: [PR] feat: add new plugin sse to support Server-Sent Events (SSE) [apisix] via GitHub
  • Re: [PR] feat: add new plugin sse to support Server-Sent Events (SSE) [apisix] via GitHub
  • Re: [PR] feat: add new plugin sse to support Server-Sent Events (SSE) [apisix] via GitHub
• [I] help request: AI-rate-limiting [apisix] via GitHub
  • Re: [I] help request: AI-rate-limiting [apisix] via GitHub
  • Re: [I] help request: AI-rate-limiting [apisix] via GitHub
• [I] help request: AI-Proxy / AI-Proxy-Multi [apisix] via GitHub
  • Re: [I] help request: AI-Proxy / AI-Proxy-Multi [apisix] via GitHub
  • Re: [I] help request: AI-Proxy / AI-Proxy-Multi [apisix] via GitHub
  • Re: [I] help request: AI-Proxy / AI-Proxy-Multi [apisix] via GitHub
• Re: [I] bug: Unable to add route with "upstream_id" from dashboard ui [apisix-dashboard] via GitHub
• Re: [I] Make Dashboard Work With Standalone Mode [apisix-dashboard] via GitHub
  • Re: [I] Make Dashboard Work With Standalone Mode [apisix-dashboard] via GitHub
  • Re: [I] Make Dashboard Work With Standalone Mode [apisix-dashboard] via GitHub
• Re: [I] Test(resource): secrets [apisix-dashboard] via GitHub
  • Re: [I] Test(resource): secrets [apisix-dashboard] via GitHub
• [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
  • Re: [PR] test: add comprehensive E2E tests for Secrets resource [apisix-dashboard] via GitHub
• Re: [I] Test(resource): protos [apisix-dashboard] via GitHub
  • Re: [I] Test(resource): protos [apisix-dashboard] via GitHub
• [PR] feat: add E2E tests for protos resource (#3092) [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for protos resource (#3092) [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for protos resource (#3092) [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for protos resource (#3092) [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for protos resource (#3092) [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for protos resource (#3092) [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for protos resource (#3092) [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for protos resource (#3092) [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for protos resource (#3092) [apisix-dashboard] via GitHub
  • Re: [PR] test: add E2E tests for protos [apisix-dashboard] via GitHub
• Re: [I] Test(resource): consumer and credentials [apisix-dashboard] via GitHub
  • Re: [I] Test(resource): consumer and credentials [apisix-dashboard] via GitHub
• [PR] test(e2e): Add E2E tests for consumer and credentials [apisix-dashboard] via GitHub
  • Re: [PR] test(e2e): Add E2E tests for consumer and credentials [apisix-dashboard] via GitHub
• [PR] feat(e2e): add E2E tests for Consumers resource [apisix-dashboard] via GitHub
  • Re: [PR] feat(e2e): add E2E tests for Consumers resource [apisix-dashboard] via GitHub
• Re: [I] request help: How to configure mTLS between ingress controller and apisix control plane [apisix-ingress-controller] via GitHub
• Re: [I] Test(resource): stream routes [apisix-dashboard] via GitHub
  • Re: [I] Test(resource): stream routes [apisix-dashboard] via GitHub
  • Re: [I] Test(resource): stream routes [apisix-dashboard] via GitHub
• [PR] feat: support deployment of multiple data plane modes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support deployment of multiple data plane modes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support deployment of multiple data plane modes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support deployment of multiple data plane modes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support deployment of multiple data plane modes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support deployment of multiple data plane modes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support deployment of multiple data plane modes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support deployment of multiple data plane modes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support deployment of multiple data plane modes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support deployment of multiple data plane modes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support deployment of multiple data plane modes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support deployment of multiple data plane modes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support deployment of multiple data plane modes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support deployment of multiple data plane modes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support deployment of multiple data plane modes [apisix-ingress-controller] via GitHub
• [PR] fix: nacos service discovery request lacks retries after failure [apisix] via GitHub
  • Re: [PR] fix: nacos service discovery request lacks retries after failure [apisix] via GitHub
  • Re: [PR] fix: nacos service discovery request lacks retries after failure [apisix] via GitHub
  • Re: [PR] fix: nacos service discovery request lacks retries after failure [apisix] via GitHub
  • Re: [PR] fix: nacos service discovery request lacks retries after failure [apisix] via GitHub
  • Re: [PR] fix: nacos service discovery request lacks retries after failure [apisix] via GitHub
  • Re: [PR] fix: nacos service discovery request lacks retries after failure [apisix] via GitHub
  • Re: [PR] fix: nacos service discovery request lacks retries after failure [apisix] via GitHub
  • Re: [PR] fix: nacos service discovery request lacks retries after failure [apisix] via GitHub
  • Re: [PR] fix: nacos service discovery request lacks retries after failure [apisix] via GitHub
  • Re: [PR] fix: nacos service discovery request lacks retries after failure [apisix] via GitHub
• Re: [I] docker-compose -p docker-apisix up -d 报错了 [apisix-docker] via GitHub
  • Re: [I] docker-compose -p docker-apisix up -d 报错了 [apisix-docker] via GitHub
• (apisix) branch master updated: chore: remove fast return to flush current queue log data during shutdown (#12711) nic443
• [PR] chore(deps): bump apache/skywalking-eyes from 9f0a5c0571ed1a0c13a16808cd8f59bc22f03883 to 21648e752a1dad42cb46b50b38e77f0a8f15219c [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump apache/skywalking-eyes from 9f0a5c0571ed1a0c13a16808cd8f59bc22f03883 to 21648e752a1dad42cb46b50b38e77f0a8f15219c [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump apache/skywalking-eyes from 9f0a5c0571ed1a0c13a16808cd8f59bc22f03883 to 21648e752a1dad42cb46b50b38e77f0a8f15219c [apisix-dashboard] via GitHub
• (apisix-dashboard) branch dependabot/github_actions/apache/skywalking-eyes-21648e752a1dad42cb46b50b38e77f0a8f15219c created (now 78dcf195a) github-bot
• (apisix-website) branch master updated: blog: add cve-2025-62232 post (#1971) traky
• [I] bug: Potential Parsing Failure in ai-drivers/open-base.lua at Line 116 Due to Incomplete Data Chunks [apisix] via GitHub
  • Re: [I] bug: Potential Parsing Failure in ai-drivers/open-base.lua at Line 116 Due to Incomplete Data Chunks [apisix] via GitHub
  • Re: [I] bug: Potential Parsing Failure in ai-drivers/open-base.lua at Line 116 Due to Incomplete Data Chunks [apisix] via GitHub
  • Re: [I] bug: Potential Parsing Failure in ai-drivers/open-base.lua at Line 116 Due to Incomplete Data Chunks [apisix] via GitHub
• Re: [PR] fix: openid foward original id token [apisix] via GitHub
  • Re: [PR] fix: openid foward original id token [apisix] via GitHub

• Earlier messages
• Later messages