notifications  

Messages by Thread

• Re: [I] request help: how to configure route without upstream (`aws-lambda` plugin) [apisix-ingress-controller] via GitHub
  • Re: [I] request help: how to configure route without upstream (`aws-lambda` plugin) [apisix-ingress-controller] via GitHub
  • Re: [I] request help: how to configure route without upstream (`aws-lambda` plugin) [apisix-ingress-controller] via GitHub
• (apisix) branch master updated: docs: remove LLM variable in access log examples young
• [I] feat: opentelemetry plugin give traces to all other plugin that are added into route [apisix] via GitHub
  • Re: [I] feat: opentelemetry plugin give traces of all other plugin that are added into route [apisix] via GitHub
  • Re: [I] feat: opentelemetry plugin give traces of all other plugin that are added into route [apisix] via GitHub
  • Re: [I] feat: opentelemetry plugin give traces of all other plugin that are added into route [apisix] via GitHub
• (apisix-dashboard) branch dependabot/npm_and_yarn/tanstack/react-query-5.84.1 deleted (was ea5d4fadb) github-bot
• (apisix-dashboard) branch dependabot/npm_and_yarn/tanstack/react-query-5.84.2 created (now 3a9206cdb) github-bot
• [PR] chore(deps): bump @tanstack/react-query from 5.74.4 to 5.84.2 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump @tanstack/react-query from 5.74.4 to 5.84.2 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump @tanstack/react-query from 5.74.4 to 5.84.2 [apisix-dashboard] via GitHub
• [PR] chore(deps-dev): bump @tanstack/react-query-devtools from 5.74.4 to 5.84.2 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps-dev): bump @tanstack/react-query-devtools from 5.74.4 to 5.84.2 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps-dev): bump @tanstack/react-query-devtools from 5.74.4 to 5.84.2 [apisix-dashboard] via GitHub
• (apisix-dashboard) branch dependabot/npm_and_yarn/tanstack/react-query-devtools-5.84.1 deleted (was 60d184442) github-bot
• (apisix-dashboard) branch dependabot/npm_and_yarn/tanstack/react-query-devtools-5.84.2 created (now 222534698) github-bot
• [PR] feat(ai-proxy-multi): add support for healthcheck [apisix] via GitHub
  • Re: [PR] feat(ai-proxy-multi): add support for healthcheck [apisix] via GitHub
  • Re: [PR] feat(ai-proxy-multi): add support for healthcheck [apisix] via GitHub
  • Re: [PR] feat(ai-proxy-multi): add support for healthcheck [apisix] via GitHub
  • Re: [PR] feat(ai-proxy-multi): add support for healthcheck [apisix] via GitHub
  • Re: [PR] feat(ai-proxy-multi): add support for healthcheck [apisix] via GitHub
  • Re: [PR] feat(ai-proxy-multi): add support for healthcheck [apisix] via GitHub
  • Re: [PR] feat(ai-proxy-multi): add support for healthcheck [apisix] via GitHub
  • Re: [PR] feat(ai-proxy-multi): add support for healthcheck [apisix] via GitHub
  • Re: [PR] feat(ai-proxy-multi): add support for healthcheck [apisix] via GitHub
  • Re: [PR] feat(ai-proxy-multi): add support for healthcheck [apisix] via GitHub
  • Re: [PR] feat(ai-proxy-multi): add support for healthcheck [apisix] via GitHub
• Re: [I] bug: cors plug-in problem [apisix] via GitHub
  • Re: [I] bug: cors plug-in problem [apisix] via GitHub
• (apisix-ingress-controller) branch docs/rc3-lb-fix deleted (was 17fabd6e) traky
• (apisix-ingress-controller) branch master updated: docs: update load balancing Gateway API doc for RC3 fix (#2506) traky
• 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
  • 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] help request: Set request rate limit by service or upstream via Ingress Controller [apisix-ingress-controller] via GitHub
  • Re: [I] help request: Set request rate limit by service or upstream via Ingress Controller [apisix-ingress-controller] via GitHub
  • Re: [I] help request: Set request rate limit by service or upstream via Ingress Controller [apisix-ingress-controller] via GitHub
• (apisix) branch 3.13-docs-patch deleted (was ffa1d8d1e) traky
• (apisix) branch release/3.13 updated: docs: remove LLM variable in access log examples (#12503) traky
• Re: [I] bug: Basic authentication requests are case-insensitive both in scheme and parameters, but this isn't supported by APISIX [apisix] via GitHub
  • Re: [I] bug: Basic authentication requests are case-insensitive both in scheme and parameters, but this isn't supported by APISIX [apisix] via GitHub
• Re: [I] bug: OOM with Dubbo Proxy Plugin [apisix] via GitHub
• [I] help request: apisix-runtime build failed, want help from community [apisix] via GitHub
  • Re: [I] help request: apisix-runtime build failed, want help from community [apisix] via GitHub
  • Re: [I] help request: apisix-runtime build failed, want help from community [apisix] via GitHub
  • Re: [I] help request: apisix-runtime build failed, want help from community [apisix] via GitHub
  • Re: [I] help request: apisix-runtime build failed, want help from community [apisix] via GitHub
  • Re: [I] help request: apisix-runtime build failed, want help from community [apisix] via GitHub
• Re: [I] bug: plugin limit-conn will keep rejecting the requests in some condition [apisix] via GitHub
  • Re: [I] bug: plugin limit-conn will keep rejecting the requests in some condition [apisix] via GitHub
  • Re: [I] bug: plugin limit-conn will keep rejecting the requests in some condition [apisix] via GitHub
• [I] feat: Changes to Bitnami Image Catalog and Bitnami Chart [apisix] via GitHub
  • Re: [I] feat: Changes to Bitnami Image Catalog and Bitnami Chart [apisix] via GitHub
  • Re: [I] feat: Changes to Bitnami Image Catalog and Bitnami Chart [apisix] via GitHub
  • Re: [I] feat: Changes to Bitnami Image Catalog and Bitnami Chart [apisix] via GitHub
  • Re: [I] feat: Changes to Bitnami Image Catalog and Bitnami Chart [apisix] via GitHub
  • Re: [I] feat: Changes to Bitnami Image Catalog and Bitnami Chart [apisix] via GitHub
• Re: [I] request help: How to configure TLS communication between ingress controller and control plane? [apisix-ingress-controller] via GitHub
  • Re: [I] request help: How to configure TLS communication between ingress controller and control plane? [apisix-ingress-controller] via GitHub
• [I] help request: SM4-CBC encryption in resty.openssl.cipher produces incompatible output with Java due to padding discrepancy [apisix] via GitHub
  • Re: [I] help request: SM4-CBC encryption in resty.openssl.cipher produces incompatible output with Java due to padding discrepancy [apisix] via GitHub
  • Re: [I] help request: SM4-CBC encryption in resty.openssl.cipher produces incompatible output with Java due to padding discrepancy [apisix] via GitHub
• (apisix-ingress-controller) branch master updated: chore(deps): bump golang.org/x/oauth2 from 0.24.0 to 0.27.0 (#2485) baoyuan
• (apisix-ingress-controller) branch dependabot/go_modules/golang.org/x/oauth2-0.27.0 deleted (was c142a378) baoyuan
• (apisix) branch 3.13-docs-patch updated: remove example in ai-proxy-multi.md traky
• (apisix) branch 3.13-docs-patch created (now 39bbaee64) traky
  • (apisix) 01/01: remove example in ai-proxy.md traky
• [PR] docs: remove LLM variable in access log examples [apisix] via GitHub
  • Re: [PR] docs: remove LLM variable in access log examples [apisix] via GitHub
  • Re: [PR] docs: remove LLM variable in access log examples [apisix] via GitHub
  • [PR] docs: remove LLM variable in access log examples [apisix] via GitHub
  • Re: [PR] docs: remove LLM variable in access log examples [apisix] via GitHub
• Re: [I] request help: Dashboard plugin configuration is lost after CRD-based ApisixRoute updates — need best practice for sync and separation of responsibilities [apisix-ingress-controller] via GitHub
  • Re: [I] request help: Dashboard plugin configuration is lost after CRD-based ApisixRoute updates — need best practice for sync and separation of responsibilities [apisix-ingress-controller] via GitHub
  • Re: [I] request help: Dashboard plugin configuration is lost after CRD-based ApisixRoute updates — need best practice for sync and separation of responsibilities [apisix-ingress-controller] via GitHub
• Re: [I] request help: How to configure mTLS between ingress controller and apisix control plane [apisix-ingress-controller] via GitHub
• Re: [I] request help: deletion of apisix crd is not idempotent [apisix-ingress-controller] via GitHub
  • Re: [I] request help: deletion of apisix crd is not idempotent [apisix-ingress-controller] via GitHub
• [I] Bitnami etcd image - August 28 [apisix-helm-chart] via GitHub
  • Re: [I] Bitnami etcd image - August 28 [apisix-helm-chart] via GitHub
  • Re: [I] Bitnami etcd image - August 28 [apisix-helm-chart] via GitHub
  • Re: [I] Bitnami etcd image - August 28 [apisix-helm-chart] via GitHub
• (apisix) branch master updated: refactor: add healthcheck manager to decouple upstream (#12426) ashishtiwari
• Re: [I] 项目还在维护吗？ [apisix-dashboard] via GitHub
  • Re: [I] 项目还在维护吗？ [apisix-dashboard] via GitHub
  • Re: [I] 项目还在维护吗？ [apisix-dashboard] via GitHub
• [I] bug: Internal Server Error when call an API created with Admin UI to https upstream [apisix] via GitHub
  • Re: [I] bug: Internal Server Error when call an API created with Admin UI to https upstream [apisix] via GitHub
  • Re: [I] bug: Internal Server Error when call an API created with Admin UI to https upstream [apisix] via GitHub
  • Re: [I] bug: Internal Server Error when call an API created with Admin UI to https upstream [apisix] via GitHub
• Re: [I] bug: failed to list routes: Get http://apisix-admin:9180/apisix/admin/routes: context canceled [apisix-ingress-controller] via GitHub
  • Re: [I] bug: failed to list routes: Get http://apisix-admin:9180/apisix/admin/routes: context canceled [apisix-ingress-controller] via GitHub
• Re: [I] bug: Deleting `ApisixRoute` will delete only one `upstream`. [apisix-ingress-controller] via GitHub
• [I] bug: When the redirect plugin is used, requests with the 'x-forwarded-proto: http' header to access the https port will still be redirected [apisix] via GitHub
  • Re: [I] bug: When the redirect plugin is used, requests with the 'x-forwarded-proto: http' header to access the https port will still be redirected [apisix] via GitHub
  • Re: [I] bug: When the redirect plugin is used, requests with the 'x-forwarded-proto: http' header to access the https port will still be redirected [apisix] via GitHub
  • Re: [I] bug: When the redirect plugin is used, requests with the 'x-forwarded-proto: http' header to access the https port will still be redirected [apisix] via GitHub
  • Re: [I] bug: When the redirect plugin is used, requests with the 'x-forwarded-proto: http' header to access the https port will still be redirected [apisix] via GitHub
  • Re: [I] bug: When the redirect plugin is used, requests with the 'x-forwarded-proto: http' header to access the https port will still be redirected [apisix] via GitHub
  • Re: [I] bug: When the redirect plugin is used, requests with the 'x-forwarded-proto: http' header to access the https port will still be redirected [apisix] via GitHub
• Re: [I] bug: unexpected result when ingress restarted [apisix-ingress-controller] via GitHub
  • Re: [I] bug: unexpected result when ingress restarted [apisix-ingress-controller] via GitHub
• Re: [I] request help: failed to sync SSL to APISIX label exceeds the maximum length of the schema. [apisix-ingress-controller] via GitHub
• Re: [I] bug: Some CRD missing status sub-resource [apisix-ingress-controller] via GitHub
• Re: [I] bug: ApisixIngress synced failed, with error: not found [apisix-ingress-controller] via GitHub
  • Re: [I] bug: ApisixIngress synced failed, with error: not found [apisix-ingress-controller] via GitHub
  • Re: [I] bug: ApisixIngress synced failed, with error: not found [apisix-ingress-controller] via GitHub
  • Re: [I] bug: ApisixIngress synced failed, with error: not found [apisix-ingress-controller] via GitHub
• [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
  • 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: [PR] feat: add new plugin sse to support Server-Sent Events (SSE) [apisix] via GitHub
• Re: [I] helm 部署完apisix ingress 创建route访问404 [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] 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] feat: add support for installing apisix ingress composite mode via helm chart [apisix-ingress-controller] 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

• Earlier messages
• Later messages