notifications  

Messages by Thread

• • Re: [I] helm apisix no support multiple ports and custom http2 port [apisix-helm-chart] via GitHub
• Re: [I] upstream_proxy to support TLS over TCP [apisix-helm-chart] via GitHub
  • Re: [I] upstream_proxy to support TLS over TCP [apisix-helm-chart] via GitHub
• Re: [I] APISIX chart ingress class name support [apisix-helm-chart] via GitHub
  • Re: [I] APISIX chart ingress class name support [apisix-helm-chart] via GitHub
• Re: [I] Add IngressClass To Chart [apisix-helm-chart] via GitHub
  • Re: [I] Add IngressClass To Chart [apisix-helm-chart] via GitHub
• Re: [I] proxy protocol customization [apisix-helm-chart] via GitHub
  • Re: [I] proxy protocol customization [apisix-helm-chart] via GitHub
• Re: [I] the ClusterRole and ClusterRoleBinding are conflict when install multi ingress controller by helm [apisix-helm-chart] via GitHub
  • Re: [I] the ClusterRole and ClusterRoleBinding are conflict when install multi ingress controller by helm [apisix-helm-chart] via GitHub
• Re: [I] Allows managing keys as secrets [apisix-helm-chart] via GitHub
  • Re: [I] Allows managing keys as secrets [apisix-helm-chart] via GitHub
• Re: [I] 怎么调整 lua_shared_dict prometheus-metrics [apisix-helm-chart] via GitHub
  • Re: [I] 怎么调整 lua_shared_dict prometheus-metrics [apisix-helm-chart] via GitHub
• Re: [I] stream tcp and udp array should support the new structure [apisix-helm-chart] via GitHub
  • Re: [I] stream tcp and udp array should support the new structure [apisix-helm-chart] via GitHub
• Re: [I] gateway.annotations 这个参数为啥不开放呢？调整公有负载均衡参数的时候很有用的啊？ [apisix-helm-chart] via GitHub
  • Re: [I] gateway.annotations 这个参数为啥不开放呢？调整公有负载均衡参数的时候很有用的啊？ [apisix-helm-chart] via GitHub
• Re: [I] Apisix deployment on k8s for log collection issues [apisix-helm-chart] via GitHub
  • Re: [I] Apisix deployment on k8s for log collection issues [apisix-helm-chart] via GitHub
• Re: [I] bug: apisix control service is not installed on k8s by helm chart [apisix-helm-chart] via GitHub
  • Re: [I] bug: apisix control service is not installed on k8s by helm chart [apisix-helm-chart] via GitHub
• Re: [I] Can I add a sidecar for logging purpose [apisix-helm-chart] via GitHub
  • Re: [I] Can I add a sidecar for logging purpose [apisix-helm-chart] via GitHub
• Re: [I] Setting admin.credentials.secretName sets the admin key to {{APISIX_ADMIN_KEY}} [apisix-helm-chart] via GitHub
  • Re: [I] Setting admin.credentials.secretName sets the admin key to {{APISIX_ADMIN_KEY}} [apisix-helm-chart] via GitHub
• Re: [I] Support path_for_test in helm chart for External Plugin [apisix-helm-chart] via GitHub
  • Re: [I] Support path_for_test in helm chart for External Plugin [apisix-helm-chart] via GitHub
• Re: [I] Apisix 2.3.0 missing pdb fix [apisix-helm-chart] via GitHub
  • Re: [I] Apisix 2.3.0 missing pdb fix [apisix-helm-chart] via GitHub
• Re: [I] How to expose prometheus endpoint without ServiceMonitor ? [apisix-helm-chart] via GitHub
  • Re: [I] How to expose prometheus endpoint without ServiceMonitor ? [apisix-helm-chart] via GitHub
• Re: [I] apisix-2.4.0 chart uses deprecated poddisruptionbudget v1beta1 [apisix-helm-chart] via GitHub
  • Re: [I] apisix-2.4.0 chart uses deprecated poddisruptionbudget v1beta1 [apisix-helm-chart] via GitHub
• Re: [I] Add helm values to use an external configmap on APISIX standalone mode [apisix-helm-chart] via GitHub
  • Re: [I] Add helm values to use an external configmap on APISIX standalone mode [apisix-helm-chart] via GitHub
• Re: [I] Error if modifying http.containerPort without updating readinessProbe.tcpSocket.port [apisix-helm-chart] via GitHub
  • Re: [I] Error if modifying http.containerPort without updating readinessProbe.tcpSocket.port [apisix-helm-chart] via GitHub
• Re: [I] Add option to set ssl ciphers [apisix-helm-chart] via GitHub
  • Re: [I] Add option to set ssl ciphers [apisix-helm-chart] via GitHub
• Re: [I] Gateway nodePort setting not working [apisix-helm-chart] via GitHub
  • Re: [I] Gateway nodePort setting not working [apisix-helm-chart] via GitHub
• Re: [I] apisix topologySpreadConstraints got removed with the merge of PR 738 [apisix-helm-chart] via GitHub
  • Re: [I] apisix topologySpreadConstraints got removed with the merge of PR 738 [apisix-helm-chart] via GitHub
• Re: [PR] Update Bitnami Etcd chart to 12.0.7 [apisix-helm-chart] via GitHub
  • Re: [PR] Update Bitnami Etcd chart to 12.0.7 [apisix-helm-chart] via GitHub
• Re: [I] etcd chart is old (9.7.3) and needs an update [apisix-helm-chart] via GitHub
  • Re: [I] etcd chart is old (9.7.3) and needs an update [apisix-helm-chart] via GitHub
• Re: [I] 通过helm部署apisix etcd一直无法启动 [apisix-helm-chart] via GitHub
• Re: [I] APISIX Helm Deployment on Minikube fails [apisix-helm-chart] via GitHub
• Re: [I] Feature request: Include PrometheusRule in chart for alerting [apisix-helm-chart] via GitHub
  • Re: [I] Feature request: Include PrometheusRule in chart for alerting [apisix-helm-chart] via GitHub
• Re: [I] Support data_encryption gateway configuration [apisix-helm-chart] via GitHub
• Re: [I] feat: provide support to install apisix runtime [apisix-helm-chart] via GitHub
  • Re: [I] feat: provide support to install apisix runtime [apisix-helm-chart] via GitHub
• Re: [I] Exploring the possibility of creating consumer groups as part of apisix installation [apisix-helm-chart] via GitHub
  • Re: [I] Exploring the possibility of creating consumer groups as part of apisix installation [apisix-helm-chart] via GitHub
• Re: [I] Request help: apisix-etcd Failed to bind volumes: timed out waiting for the condition [apisix-helm-chart] via GitHub
• Re: [I] apisix deploy fail [apisix-helm-chart] via GitHub
  • Re: [I] apisix deploy fail [apisix-helm-chart] via GitHub
• Re: [I] 不能创建PV [apisix-helm-chart] via GitHub
• Re: [I] apisix-etcd 出错 [apisix-helm-chart] via GitHub
• Re: [I] Bug: Etcd Cluster State After First Install [apisix-helm-chart] via GitHub
  • Re: [I] Bug: Etcd Cluster State After First Install [apisix-helm-chart] via GitHub
• Re: [I] dashboard has no consul option, only consul kv, why? [apisix-helm-chart] via GitHub
• Re: [I] etcd chart support defrag cronjob config [apisix-helm-chart] via GitHub
  • Re: [I] etcd chart support defrag cronjob config [apisix-helm-chart] via GitHub
• Re: [I] Missing plugins field in Dashboard ConfigMap [apisix-helm-chart] via GitHub
  • Re: [I] Missing plugins field in Dashboard ConfigMap [apisix-helm-chart] via GitHub
• (apisix) branch master updated: feat(request-id): add UUID v7 generation support (#13152) baoyuan
• (apisix) branch master updated: feat: support batch TCP/UDP port ranges in stream_proxy config (#13153) baoyuan
• (apisix) branch master updated: fix: add schema compatibility for consumer and credential resources (#13154) baoyuan
• (apisix) branch master updated: fix(admin): use local config to fetch global rules in standalone mode (#13122) shreemaanabhishek
• (apisix) branch master updated: chore: upgrade lua-resty-dns-client to 7.1.1 (#13180) nic443
• [PR] fix(forward-auth): clear configured upstream headers not present in auth response [apisix] via GitHub
  • Re: [PR] fix(forward-auth): clear configured upstream headers not present in auth response [apisix] via GitHub
• Re: [I] aws-load-balancer-security-groups not working with NLB in EKS [apisix-helm-chart] via GitHub
  • Re: [I] aws-load-balancer-security-groups not working with NLB in EKS [apisix-helm-chart] via GitHub
• [PR] fix(jwt-auth): enforce algorithm match before signature verification [apisix] via GitHub
• Re: [I] Why apisix-3.8.0 does not provide image in ARM64 architecture? [apisix-helm-chart] via GitHub
• Re: [I] ApisixUpstream crds cannot change keepalive_pool [apisix-helm-chart] via GitHub
  • Re: [I] ApisixUpstream crds cannot change keepalive_pool [apisix-helm-chart] via GitHub
• Re: [I] Issue Apache Apisix gRPC transcode with AWS Networkloadbalancer [apisix-helm-chart] via GitHub
  • Re: [I] Issue Apache Apisix gRPC transcode with AWS Networkloadbalancer [apisix-helm-chart] via GitHub
• Re: [I] missing user key in JWT token [apisix-helm-chart] via GitHub
  • Re: [I] missing user key in JWT token [apisix-helm-chart] via GitHub
• [PR] feat(ai-proxy): add native Anthropic Messages API protocol support [apisix] via GitHub
  • Re: [PR] feat(ai-proxy): add native Anthropic Messages API protocol support [apisix] via GitHub
  • Re: [PR] feat(ai-proxy): add native Anthropic Messages API protocol support [apisix] via GitHub
  • Re: [PR] feat(ai-proxy): add native Anthropic Messages API protocol support [apisix] via GitHub
  • Re: [PR] feat(ai-proxy): add native Anthropic Messages API protocol support [apisix] via GitHub
  • Re: [PR] feat(ai-proxy): add native Anthropic Messages API protocol support [apisix] via GitHub
  • Re: [PR] feat(ai-proxy): add native Anthropic Messages API protocol support [apisix] via GitHub
• [PR] chore: upgrade lua-resty-dns-client to 7.1.1 [apisix] via GitHub
  • Re: [PR] chore: upgrade lua-resty-dns-client to 7.1.1 [apisix] via GitHub
• [I] feat: Why doesn't the limit-req plugin support `rules` like limit-conn and ai-rate-limiting? [apisix] via GitHub
  • Re: [I] feat: Why doesn't the limit-req plugin support `rules` like limit-conn and ai-rate-limiting? [apisix] via GitHub
  • Re: [I] feat: Why doesn't the limit-req plugin support `rules` like limit-conn and ai-rate-limiting? [apisix] via GitHub
  • Re: [I] feat: Why doesn't the limit-req plugin support `rules` like limit-conn and ai-rate-limiting? [apisix] via GitHub
  • Re: [I] feat: Why doesn't the limit-req plugin support `rules` like limit-conn and ai-rate-limiting? [apisix] via GitHub
  • Re: [I] feat: Why doesn't the limit-req plugin support `rules` like limit-conn and ai-rate-limiting? [apisix] via GitHub
  • Re: [I] feat: Why doesn't the limit-req plugin support `rules` like limit-conn and ai-rate-limiting? [apisix] via GitHub
• (apisix-ingress-controller) branch dependabot/go_modules/github.com/aws/aws-sdk-go-v2/service/s3-1.97.3 created (now c16f15f0) github-bot
• [PR] chore(deps): bump github.com/aws/aws-sdk-go-v2/service/s3 from 1.69.0 to 1.97.3 [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch dependabot/go_modules/github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream-1.7.8 created (now 4d2be12e) github-bot
• [PR] chore(deps): bump github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream from 1.6.7 to 1.7.8 [apisix-ingress-controller] via GitHub
• [PR] docs: release APISIX v3.16.0 [apisix-website] via GitHub
  • Re: [PR] docs: release APISIX v3.16.0 [apisix-website] via GitHub
• (apisix-ingress-controller) branch dependabot/go_modules/github.com/aws/aws-sdk-go-v2/service/lambda-1.88.5 created (now c8d78079) github-bot
• [PR] chore(deps): bump github.com/aws/aws-sdk-go-v2/service/lambda from 1.69.0 to 1.88.5 [apisix-ingress-controller] via GitHub
• (apisix) branch master updated: chore: release 3.16.0 (#13129) shreemaanabhishek
• [PR] chore(deps): bump github.com/aws/aws-sdk-go-v2/service/cloudwatchlogs from 1.44.0 to 1.65.0 [apisix-ingress-controller] via GitHub
• (apisix) tag 3.16.0 created (now f9c4ee371) shreemaanabhishek
• (apisix-ingress-controller) branch dependabot/go_modules/github.com/aws/aws-sdk-go-v2/service/cloudwatchlogs-1.65.0 created (now ce0da8a9) github-bot
• [PR] feat(openid-connect): update session config to support lua-resty-session, fixes deprecated session.cookie.lifetime [apisix] via GitHub
  • Re: [PR] feat(openid-connect): update session config to support lua-resty-session, fixes deprecated session.cookie.lifetime [apisix] via GitHub
  • Re: [PR] feat(openid-connect): update session config to support lua-resty-session, fixes deprecated session.cookie.lifetime [apisix] via GitHub
  • Re: [PR] feat(openid-connect): update session config to support lua-resty-session, fixes deprecated session.cookie.lifetime [apisix] via GitHub
• [I] bug: openid-connect` plugin `session.cookie.lifetime` has no effect (lua-resty-session 4.x incompatibility) [apisix] via GitHub
  • Re: [I] bug: openid-connect` plugin `session.cookie.lifetime` has no effect (lua-resty-session 4.x incompatibility) [apisix] via GitHub
• [I] Your MCP server earned an A security grade on Loaditout [apisix] via GitHub
• [I] feat: As a user, I want new upstream peers in the EWMA balancer to be initialized with a warm score derived from existing peers, so that newly added pods receive a gradual traffic ramp-up [apisix] via GitHub
  • Re: [I] feat: As a user, I want new upstream peers in the EWMA balancer to be initialized with a warm score derived from existing peers, so that newly added pods receive a gradual traffic ramp-up [apisix] via GitHub
  • Re: [I] feat: As a user, I want new upstream peers in the EWMA balancer to be initialized with a warm score derived from existing peers, so that newly added pods receive a gradual traffic ramp-up [apisix] via GitHub
• [PR] docs: add Gemini, Vertex AI, and Anthropic examples to ai-proxy plugin [apisix] via GitHub
  • Re: [PR] docs: add Gemini, Vertex AI, and Anthropic examples to ai-proxy plugin [apisix] via GitHub
  • Re: [PR] docs: add Gemini, Vertex AI, and Anthropic examples to ai-proxy plugin [apisix] via GitHub
• [PR] docs: update traffic-split plugin attribute types and valid values [apisix] via GitHub
  • Re: [PR] docs: update traffic-split plugin attribute types and valid values [apisix] via GitHub
• (apisix) branch refactor/ai-proxy-three-layer deleted (was 175b62318) nic443
• (apisix) branch refactor/ai-proxy-three-layer created (now 175b62318) nic443
• [I] help request: apisix3.15的rpm安装包下载地址在哪？ [apisix] via GitHub
  • Re: [I] help request: download link for the APISIX 3.15 RPM package [apisix] via GitHub
  • Re: [I] help request: download link for the APISIX 3.15 RPM package [apisix] via GitHub
• [PR] refactor: three-layer AI proxy architecture (protocols/providers/transport) [apisix] via GitHub
  • Re: [PR] refactor: three-layer AI proxy architecture (protocols/providers/transport) [apisix] via GitHub
  • Re: [PR] refactor: three-layer AI proxy architecture (protocols/providers/transport) [apisix] via GitHub
  • Re: [PR] refactor: three-layer AI proxy architecture (protocols/providers/transport) [apisix] via GitHub
  • Re: [PR] refactor: three-layer AI proxy architecture (protocols/providers/transport) [apisix] via GitHub
  • Re: [PR] refactor: three-layer AI proxy architecture (protocols/providers/transport) [apisix] via GitHub
  • Re: [PR] refactor: three-layer AI proxy architecture (protocols/providers/transport) [apisix] via GitHub
  • Re: [PR] refactor: three-layer AI proxy architecture (protocols/providers/transport) [apisix] via GitHub
• [PR] docs: fix broken paragraph and add custom headers example for limit-count [apisix] via GitHub
  • Re: [PR] docs: fix broken paragraph and add custom headers example for limit-count [apisix] via GitHub
  • Re: [PR] docs: fix broken paragraph and add custom headers example for limit-count [apisix] via GitHub
  • Re: [PR] docs: fix broken paragraph and add custom headers example for limit-count [apisix] via GitHub
  • Re: [PR] docs: fix broken paragraph and add custom headers example for limit-count [apisix] via GitHub
• [PR] docs: fix ai-proxy-multi attribute nesting and add missing health check sub-attributes [apisix] via GitHub
  • Re: [PR] docs: fix ai-proxy-multi attribute nesting and add missing health check sub-attributes [apisix] via GitHub
  • Re: [PR] docs: fix ai-proxy-multi attribute nesting and add missing health check sub-attributes [apisix] via GitHub
• [PR] docs: add gateway logs example to request-id plugin documentation [apisix] via GitHub
  • Re: [PR] docs: add gateway logs example to request-id plugin documentation [apisix] via GitHub
• [PR] docs: update ai-aliyun-content-moderation plugin documentation [apisix] via GitHub
• [PR] docs: fix misleading "types of Plugin" wording in lifecycle diagram [apisix] via GitHub
  • Re: [PR] docs: fix misleading "types of Plugin" wording in lifecycle diagram [apisix] via GitHub
• Re: [I] Upcoming changes to Bitnami images and charts [apisix-helm-chart] via GitHub
• (apisix) branch master updated: fix: redact sensitive data from plugin log output (#13123) baoyuan
• (apisix) branch master updated: fix(opentelemetry): coerce additional_attributes values to string (#13146) shreemaanabhishek
• (apisix) branch dependabot/github_actions/docker/login-action-4.1.0 deleted (was 22b92c893) github-bot
• (apisix-dashboard) branch dependabot/npm_and_yarn/vite-6.4.2 deleted (was 58b167dfe) github-bot
• Re: [I] bug: Prometheus reports LLM metrics even when LLM plugin is not enabled [apisix] via GitHub
• (apisix) branch master updated (636100ec7 -> 490ee295a) baoyuan
• (apisix-dashboard) branch dependabot/npm_and_yarn/vite-6.4.2 created (now 58b167dfe) github-bot
• [PR] chore(deps-dev): bump vite from 6.4.1 to 6.4.2 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps-dev): bump vite from 6.4.1 to 6.4.2 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps-dev): bump vite from 6.4.1 to 6.4.2 [apisix-dashboard] via GitHub
• (apisix-website) branch release-3.16.0 updated (dc404d1c3a7 -> f04fed61b7c) traky
• (apisix-website) branch release-3.16.0 updated (f58f6aca9d2 -> dc404d1c3a7) traky
• (apisix) branch release/3.16 updated (64a50547e -> f9c4ee371) shreemaanabhishek
• (apisix) branch release/3.16 updated (6bb7532da -> 64a50547e) shreemaanabhishek
• (apisix) branch release/3.16 updated (e63edddb5 -> 6bb7532da) shreemaanabhishek
• Re: [PR] ci: support gitleaks to scan hardcoded password [apisix-dashboard] via GitHub
• Re: [PR] ci: support codeql-analysis [apisix-dashboard] via GitHub
• Re: [PR] fix: update seven module to 0.2.6 [apisix-ingress-controller] via GitHub
• Re: [PR] test: use ginkgo cmd to run e2e cases for more elegant output [apisix-ingress-controller] via GitHub
• Re: [PR] chore(deps): bump k8s.io/api from 0.24.3 to 0.24.4 in /test/e2e [apisix-ingress-controller] via GitHub
• Re: [PR] fix: minish resync_delay for e2e test [apisix-dashboard] via GitHub
• Re: [PR] feat: add referer-restriction plugin form [apisix-dashboard] via GitHub
• [PR] feat(plugin): add dpop plugin for RFC 9449 proof-of-possession [apisix] via GitHub
  • Re: [PR] feat(plugin): add dpop plugin for RFC 9449 proof-of-possession [apisix] via GitHub
  • Re: [PR] feat(plugin): add dpop plugin for RFC 9449 proof-of-possession [apisix] via GitHub
  • Re: [PR] feat(plugin): add dpop plugin for RFC 9449 proof-of-possession [apisix] via GitHub
• Re: [PR] fix: make field ID compatible with both string and int [apisix-dashboard] via GitHub
• [PR] fix(proxy-rewrite): correct header operation order to remove > set > add [apisix] via GitHub
  • Re: [PR] fix(proxy-rewrite): correct header operation order to remove > set > add [apisix] via GitHub
  • Re: [PR] fix(proxy-rewrite): correct header operation order to remove > set > add [apisix] via GitHub
  • Re: [PR] fix(proxy-rewrite): correct header operation order to remove > set > add [apisix] via GitHub
  • Re: [PR] fix(proxy-rewrite): correct header operation order to remove > set > add [apisix] via GitHub
• Re: [PR] chore: caching [apisix-ingress-controller] via GitHub
• (apisix-dashboard) branch dependabot/github_actions/apache/skywalking-eyes-6ac35584d6f923b6cb62f1ae8682c5bc60b537e4 created (now 41292e1fe) github-bot
• [PR] chore(deps): bump apache/skywalking-eyes from 55373684d1b70e5f8fd9fc8ec114a89ad11a56a3 to 6ac35584d6f923b6cb62f1ae8682c5bc60b537e4 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump apache/skywalking-eyes from 55373684d1b70e5f8fd9fc8ec114a89ad11a56a3 to 6ac35584d6f923b6cb62f1ae8682c5bc60b537e4 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump apache/skywalking-eyes from 55373684d1b70e5f8fd9fc8ec114a89ad11a56a3 to 6ac35584d6f923b6cb62f1ae8682c5bc60b537e4 [apisix-dashboard] via GitHub
• [I] bug: proxy-rewrite silently drops duplicate keys in headers.add due to JSON object limitation [apisix] via GitHub
  • Re: [I] bug: proxy-rewrite silently drops duplicate keys in headers.add due to JSON object limitation [apisix] via GitHub
• Re: [PR] fix: some apis bypassed authentication [apisix-dashboard] via GitHub
• (apisix) branch release/3.16 updated (2d3d0a40b -> e63edddb5) shreemaanabhishek
• [PR] fix(standalone): use credential id instead of conf key for schema selection [apisix] via GitHub
  • Re: [PR] feat: allow configuring credentials in standalone mode [apisix] via GitHub

• Earlier messages
• Later messages