notifications  

Messages by Thread

• • Re: [PR] docs: update load balancing Gateway API doc for RC3 fix [apisix-ingress-controller] via GitHub
  • Re: [PR] docs: update load balancing Gateway API doc for RC3 fix [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch docs/rc3-lb-fix created (now 17fabd6e) traky
  • (apisix-ingress-controller) 01/01: Update load balancing Gateway API doc (RC3 fix) traky
• Re: [I] bug: controller Unexplained hanging [apisix-ingress-controller] via GitHub
  • Re: [I] bug: controller Unexplained hanging [apisix-ingress-controller] via GitHub
• Re: [I] Autogenerated upstream from (service) backend does not match name from CRD: upstream doesn't exist [apisix-ingress-controller] via GitHub
  • Re: [I] Autogenerated upstream from (service) backend does not match name from CRD: upstream doesn't exist [apisix-ingress-controller] via GitHub
  • Re: [I] Autogenerated upstream from (service) backend does not match name from CRD: upstream doesn't exist [apisix-ingress-controller] via GitHub
• Re: [I] help request: apisix pods are forwarded after rolling updates and return 503 [apisix-ingress-controller] via GitHub
  • Re: [I] help request: apisix pods are forwarded after rolling updates and return 503 [apisix-ingress-controller] via GitHub
  • Re: [I] help request: apisix pods are forwarded after rolling updates and return 503 [apisix-ingress-controller] via GitHub
• [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
  • Re: [PR] feat: add new plugin sse to support Server-Sent Events (SSE) [apisix] via GitHub
• Re: [I] How to set the PVC storage of etcd when deploying apisix-helm-chart? [apisix-helm-chart] via GitHub
  • Re: [I] How to set the PVC storage of etcd when deploying apisix-helm-chart? [apisix-helm-chart] via GitHub
• Re: [I] PVC problems in etcd deployment [apisix-helm-chart] via GitHub
  • Re: [I] PVC problems in etcd deployment [apisix-helm-chart] via GitHub
• Re: [I] etcd-server start failure [apisix-helm-chart] via GitHub
  • Re: [I] etcd-server start failure [apisix-helm-chart] via GitHub
• Re: [I] apisix-ingress install fail because of etcd not start [apisix-helm-chart] via GitHub
  • Re: [I] apisix-ingress install fail because of etcd not start [apisix-helm-chart] via GitHub
• Re: [I] apisix-etcd 3个节点，俩个一直失败 [apisix-helm-chart] via GitHub
  • Re: [I] apisix-etcd 3个节点，俩个一直失败 [apisix-helm-chart] via GitHub
• Re: [I] apisix error:failed to fetch data from etcd: xxxx could not be resolved [apisix-helm-chart] via GitHub
  • Re: [I] apisix error:failed to fetch data from etcd: xxxx could not be resolved [apisix-helm-chart] via GitHub
• Re: [I] etcd Back-off restarting failed container [apisix-helm-chart] via GitHub
  • Re: [I] etcd Back-off restarting failed container [apisix-helm-chart] via GitHub
• Re: [I] How should I restore ETCD deployed in K8S? [apisix-helm-chart] via GitHub
  • Re: [I] How should I restore ETCD deployed in K8S? [apisix-helm-chart] via GitHub
• Re: [I] apisix etcd in crashloopback [apisix-helm-chart] via GitHub
  • Re: [I] apisix etcd in crashloopback [apisix-helm-chart] via GitHub
• Re: [I] Help: Upgrading using Helm Chart 2.0.0 giving ETCD errors in decoupled mode [apisix-helm-chart] via GitHub
  • Re: [I] Help: Upgrading using Helm Chart 2.0.0 giving ETCD errors in decoupled mode [apisix-helm-chart] via GitHub
• Re: [I] install ingress-apisix without new etcd error [apisix-helm-chart] via GitHub
  • Re: [I] install ingress-apisix without new etcd error [apisix-helm-chart] via GitHub
• Re: [I] Run ApiSix Helm chart without etcd Dependency [apisix-helm-chart] via GitHub
  • Re: [I] Run ApiSix Helm chart without etcd Dependency [apisix-helm-chart] via GitHub
• Re: [I] Apisix-Etcd-0 CrashLoopBackOff [apisix-helm-chart] via GitHub
  • Re: [I] Apisix-Etcd-0 CrashLoopBackOff [apisix-helm-chart] via GitHub
• [I] bug: Plugin logs missing but request still routed incorrectly in APISIX 2.13.2 [apisix] via GitHub
  • Re: [I] bug: Plugin logs missing but request still routed incorrectly in APISIX 2.13.1 [apisix] via GitHub
  • Re: [I] bug: Plugin logs missing but request still routed incorrectly in APISIX 2.13.1 [apisix] via GitHub
  • Re: [I] bug: Plugin logs missing but request still routed incorrectly in APISIX 2.13.1 [apisix] via GitHub
  • Re: [I] bug: Plugin logs missing but request still routed incorrectly in APISIX 2.13.1 [apisix] via GitHub
  • Re: [I] bug: Plugin logs missing but request still routed incorrectly in APISIX 2.13.1 [apisix] via GitHub
  • Re: [I] bug: Plugin logs missing but request still routed incorrectly in APISIX 2.13.1 [apisix] via GitHub
• Re: [I] request help: after using mock etcd, I found that the error "etcdserver: duplicate key given in txn requests" would appear regularly [apisix-ingress-controller] via GitHub
  • Re: [I] request help: after using mock etcd, I found that the error "etcdserver: duplicate key given in txn requests" would appear regularly [apisix-ingress-controller] via GitHub
• Re: [I] help request: Apisix ETCD going into Crash loop back off [apisix] via GitHub
  • Re: [I] help request: Apisix ETCD going into Crash loop back off [apisix] via GitHub
  • Re: [I] help request: Apisix ETCD going into Crash loop back off [apisix] via GitHub
  • Re: [I] help request: Apisix ETCD going into Crash loop back off [apisix] via GitHub
  • Re: [I] help request: Apisix ETCD going into Crash loop back off [apisix] via GitHub
• [I] help request: Slack invitation [apisix] via GitHub
  • Re: [I] help request: Slack invitation [apisix] via GitHub
  • Re: [I] help request: Slack invitation [apisix] via GitHub
• [I] help request: OIDC Login Loop & Refresh Token Failures with openid-connect Plugin for SPA + API Gateway Pattern [apisix] via GitHub
  • Re: [I] help request: OIDC Login Loop & Refresh Token Failures with openid-connect Plugin for SPA + API Gateway Pattern [apisix] via GitHub
  • Re: [I] help request: OIDC Login Loop & Refresh Token Failures with openid-connect Plugin for SPA + API Gateway Pattern [apisix] via GitHub
  • Re: [I] help request: OIDC Login Loop & Refresh Token Failures with openid-connect Plugin for SPA + API Gateway Pattern [apisix] via GitHub
  • Re: [I] help request: OIDC Login Loop & Refresh Token Failures with openid-connect Plugin for SPA + API Gateway Pattern [apisix] via GitHub
  • Re: [I] help request: OIDC Login Loop & Refresh Token Failures with openid-connect Plugin for SPA + API Gateway Pattern [apisix] via GitHub
  • Re: [I] help request: OIDC Login Loop & Refresh Token Failures with openid-connect Plugin for SPA + API Gateway Pattern [apisix] via GitHub
• [I] help request: I have encountered a questions? [apisix] via GitHub
  • Re: [I] help request: I have encountered a questions? [apisix] via GitHub
  • Re: [I] help request: quickstart doesn't work as expected [apisix] via GitHub
  • Re: [I] help request: quickstart doesn't work as expected [apisix] via GitHub
• [I] get_by_id return different values [apisix] via GitHub
  • Re: [I] get_by_id return different values [apisix] via GitHub
  • Re: [I] get_by_id return different values [apisix] via GitHub
  • Re: [I] get_by_id return different values [apisix] via GitHub
  • Re: [I] get_by_id return different values [apisix] via GitHub
  • Re: [I] get_by_id return different values [apisix] via GitHub
  • Re: [I] get_by_id return different values [apisix] via GitHub
  • Re: [I] get_by_id return different values [apisix] via GitHub
  • Re: [I] get_by_id return different values [apisix] via GitHub
  • Re: [I] get_by_id return different values [apisix] via GitHub
• [I] [Docs]: Broken links to multiples docs [apisix-ingress-controller] via GitHub
  • Re: [I] [Docs]: Broken links to multiples docs [apisix-ingress-controller] via GitHub
  • Re: [I] [Docs]: Broken links to multiples docs [apisix-ingress-controller] via GitHub
• [I] The "Include LLM Information in Access Log" feature doesn't seem to be working. [apisix] via GitHub
  • Re: [I] The "Include LLM Information in Access Log" feature doesn't seem to be working. [apisix] via GitHub
  • Re: [I] The "Include LLM Information in Access Log" feature doesn't seem to be working. [apisix] via GitHub
  • Re: [I] The "Include LLM Information in Access Log" feature doesn't seem to be working. [apisix] via GitHub
  • Re: [I] The "Include LLM Information in Access Log" feature doesn't seem to be working. [apisix] via GitHub
  • Re: [I] The "Include LLM Information in Access Log" feature doesn't seem to be working. [apisix] via GitHub
  • Re: [I] The "Include LLM Information in Access Log" feature doesn't seem to be working. [apisix] via GitHub
  • Re: [I] The "Include LLM Information in Access Log" feature doesn't seem to be working. [apisix] via GitHub
  • Re: [I] The "Include LLM Information in Access Log" feature doesn't seem to be working. [apisix] via GitHub
  • Re: [I] The "Include LLM Information in Access Log" feature doesn't seem to be working. [apisix] via GitHub
  • Re: [I] The "Include LLM Information in Access Log" feature doesn't seem to be working. [apisix] via GitHub
  • Re: [I] The "Include LLM Information in Access Log" feature doesn't seem to be working. [apisix] via GitHub
• Re: [I] bug: when ApisixPluginConfig resource update fails, it will not be retried [apisix-ingress-controller] via GitHub
  • Re: [I] bug: when ApisixPluginConfig resource update fails, it will not be retried [apisix-ingress-controller] via GitHub
• [PR] chore(deps-dev): bump yaml from 2.7.1 to 2.8.1 [apisix-dashboard] via GitHub
• Re: [PR] chore(deps-dev): bump yaml from 2.7.1 to 2.8.0 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps-dev): bump yaml from 2.7.1 to 2.8.0 [apisix-dashboard] via GitHub
• (apisix-dashboard) branch dependabot/npm_and_yarn/yaml-2.8.0 deleted (was d1bed04d5) github-bot
• (apisix-dashboard) branch dependabot/npm_and_yarn/yaml-2.8.1 created (now f7683b114) github-bot
• Re: [I] bug: ApisixIngress ApisixIngress synced failed, with error: upstream doesn't exist. [apisix-ingress-controller] via GitHub
  • Re: [I] bug: ApisixIngress ApisixIngress synced failed, with error: upstream doesn't exist. [apisix-ingress-controller] via GitHub
  • Re: [I] bug: ApisixIngress ApisixIngress synced failed, with error: upstream doesn't exist. [apisix-ingress-controller] via GitHub
• Re: [I] request help: if the service contains multiple ports, but the backends of apisixroute do not specify all the ports of the service, apisixupstream will report a NotFound error [apisix-ingress-controller] via GitHub
  • Re: [I] request help: if the service contains multiple ports, but the backends of apisixroute do not specify all the ports of the service, apisixupstream will report a NotFound error [apisix-ingress-controller] via GitHub
  • Re: [I] request help: if the service contains multiple ports, but the backends of apisixroute do not specify all the ports of the service, apisixupstream will report a NotFound error [apisix-ingress-controller] via GitHub
• (apisix) branch master updated: feat: support limit-conn in workflow plugin (#12465) nic443
• [I] bug: error logs are generated regularly in the current master branch code [apisix] via GitHub
  • Re: [I] bug: error logs are generated regularly in the current master branch code [apisix] via GitHub
  • Re: [I] bug: error logs are generated regularly in the current master branch code [apisix] via GitHub
• (apisix-ingress-controller) branch master updated: chore(test): Refactor loop to use range over integer in test (#2494) ashishtiwari
• (apisix-ingress-controller) branch master updated: chore: add test cases for external service (#2500) ashishtiwari
• [PR] Bzp/fix grpc web missing trailers [apisix] via GitHub
  • Re: [PR] fix(grpc-web): missing trailers when empty resp body [apisix] via GitHub
  • Re: [PR] fix(grpc-web): missing trailers when empty resp body [apisix] via GitHub
  • Re: [PR] fix(grpc-web): missing trailers when empty resp body [apisix] via GitHub
  • Re: [PR] fix(grpc-web): missing trailers when empty resp body [apisix] via GitHub
• Re: [PR] Refactor the apisix route validation test function [apisix-ingress-controller] via GitHub
  • Re: [PR] Refactor the apisix route validation test function [apisix-ingress-controller] via GitHub
• [I] help request: How to config below nginx nonfiguration in APISIX or use plugin? [apisix] via GitHub
  • Re: [I] help request: How to config below nginx nonfiguration in APISIX or use plugin? [apisix] via GitHub
  • Re: [I] help request: How to config below nginx nonfiguration in APISIX or use plugin? [apisix] via GitHub
• Re: [I] bug: unable to sync apisix upstream and route crd using name same as kubernetes service [apisix-ingress-controller] via GitHub
  • Re: [I] bug: unable to sync apisix upstream and route crd using name same as kubernetes service [apisix-ingress-controller] via GitHub
  • Re: [I] bug: unable to sync apisix upstream and route crd using name same as kubernetes service [apisix-ingress-controller] via GitHub
• [I] feat: As a user, I want to the load balancer to support subset matching, so that I can quickly setup multiple service lanes [apisix] via GitHub
  • Re: [I] feat: As a user, I want to the load balancer to support subset matching, so that I can quickly setup multiple service lanes [apisix] via GitHub
  • Re: [I] feat: As a user, I want to the load balancer to support subset matching, so that I can quickly setup multiple service lanes [apisix] via GitHub
  • Re: [I] feat: As a user, I want to the load balancer to support subset matching, so that I can quickly setup multiple service lanes [apisix] via GitHub
  • Re: [I] feat: As a user, I want to the load balancer to support subset matching, so that I can quickly setup multiple service lanes [apisix] via GitHub
• (apisix-helm-chart) tag apisix-2.11.4 created (now 57c4f6d) github-bot
• (apisix-helm-chart) branch feat/apisix-ic-rc3 deleted (was 750df7a) juzhiyuan
• (apisix-helm-chart) branch master updated: chore: update apisix helm chart with ingress controller rc3 (#858) juzhiyuan
• (apisix-helm-chart) branch feat/apisix-ic-rc3 updated (e78e392 -> 750df7a) juzhiyuan
• [PR] chore: update apisix helm chart with ingress controller rc3 [apisix-helm-chart] via GitHub
  • Re: [PR] chore: update apisix helm chart with ingress controller rc3 [apisix-helm-chart] via GitHub
  • Re: [PR] chore: update apisix helm chart with ingress controller rc3 [apisix-helm-chart] via GitHub
  • Re: [PR] chore: update apisix helm chart with ingress controller rc3 [apisix-helm-chart] via GitHub
• (apisix-helm-chart) branch feat/apisix-ic-rc3 created (now e78e392) juzhiyuan
  • (apisix-helm-chart) 01/01: chore: update helm chart juzhiyuan
• [I] bug: ApisixRoutes are not synced to apisix ingress controller / admin [apisix-ingress-controller] via GitHub
  • Re: [I] bug: ApisixRoutes are not synced to apisix ingress controller / admin [apisix-ingress-controller] via GitHub
  • Re: [I] bug: ApisixRoutes are not synced to apisix ingress controller / admin [apisix-ingress-controller] via GitHub
  • Re: [I] bug: ApisixRoutes are not synced to apisix ingress controller / admin [apisix-ingress-controller] via GitHub
  • Re: [I] bug: ApisixRoutes are not synced to apisix ingress controller / admin [apisix-ingress-controller] via GitHub
  • Re: [I] bug: ApisixRoutes are not synced to apisix ingress controller / admin [apisix-ingress-controller] via GitHub
  • Re: [I] bug: ApisixRoutes are not synced to apisix ingress controller / admin [apisix-ingress-controller] via GitHub
• [I] [Docs]: Broken links to multiples docs [apisix-website] via GitHub
• Re: [PR] Use named context for check_standalong_config.sh [apisix-docker] via GitHub
• Re: [I] request help: Release new version of APISIX ingress controller [apisix-ingress-controller] via GitHub
  • Re: [I] request help: Release new version of APISIX ingress controller [apisix-ingress-controller] via GitHub
• (apisix-helm-chart) tag apisix-ingress-controller-1.0.4 created (now e0f24ce) github-bot
• (apisix-helm-chart) branch master updated: feat: release apisix-ingress-controller 2.0.0-rc3 (#854) alinsran
• (apisix-dashboard) branch dependabot/npm_and_yarn/tanstack/react-query-devtools-5.84.1 created (now 60d184442) github-bot
• (apisix-dashboard) branch dependabot/npm_and_yarn/tanstack/react-query-devtools-5.84.0 deleted (was cbe71cc4f) github-bot
• [PR] chore(deps-dev): bump @tanstack/react-query-devtools from 5.74.4 to 5.84.1 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps-dev): bump @tanstack/react-query-devtools from 5.74.4 to 5.84.1 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps-dev): bump @tanstack/react-query-devtools from 5.74.4 to 5.84.1 [apisix-dashboard] via GitHub
• Re: [PR] docs: add mermaid diagrams for AI Gateway blogs [apisix-website] via GitHub
• (apisix-dashboard) branch dependabot/npm_and_yarn/tanstack/react-query-5.84.0 deleted (was 8107480a1) github-bot
• (apisix-dashboard) branch dependabot/npm_and_yarn/tanstack/react-query-5.84.1 created (now ea5d4fadb) github-bot
• [PR] chore(deps): bump @tanstack/react-query from 5.74.4 to 5.84.1 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump @tanstack/react-query from 5.74.4 to 5.84.1 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump @tanstack/react-query from 5.74.4 to 5.84.1 [apisix-dashboard] via GitHub
• Re: [PR] fix: namespace controller memory leak [apisix-ingress-controller] via GitHub
• Re: [I] Consider removing easyjson dependency due to sanction concerns [apisix-ingress-controller] via GitHub
  • Re: [I] Consider removing easyjson dependency due to sanction concerns [apisix-ingress-controller] via GitHub
• Re: [I] bug: if one route synchronization error occurs, the other routes will not be synchronized [apisix-ingress-controller] via GitHub
  • Re: [I] bug: if one route synchronization error occurs, the other routes will not be synchronized [apisix-ingress-controller] via GitHub
  • Re: [I] bug: if one route synchronization error occurs, the other routes will not be synchronized [apisix-ingress-controller] via GitHub
  • Re: [I] bug: if one route synchronization error occurs, the other routes will not be synchronized [apisix-ingress-controller] via GitHub
• Re: [I] bug: when the ingress controller has a leader election, the namespace controller goroutine does not exit normally [apisix-ingress-controller] via GitHub
  • Re: [I] bug: when the ingress controller has a leader election, the namespace controller goroutine does not exit normally [apisix-ingress-controller] via GitHub
  • Re: [I] bug: when the ingress controller has a leader election, the namespace controller goroutine does not exit normally [apisix-ingress-controller] via GitHub
• Re: [I] docs: missing resources fields in References section [apisix-ingress-controller] via GitHub
  • Re: [I] docs: missing resources fields in References section [apisix-ingress-controller] via GitHub
  • Re: [I] docs: missing resources fields in References section [apisix-ingress-controller] via GitHub
• [PR] fix: avoid restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub
  • Re: [PR] fix: restart errors from yaml config rewrite [apisix] via GitHub

• Earlier messages
• Later messages