Messages by Thread
-
[I] feat: As a Kubernetes user, I want to leverage Gateway API Inference Extension, so that I can use the Gateway API to optimize self-hosting Generative Models on Kubernetes [apisix-ingress-controller]
via GitHub
-
Re: [I] feat: As a Kubernetes user, I want to leverage Gateway API Inference Extension, so that I can use the Gateway API to optimize self-hosting Generative Models on Kubernetes [apisix-ingress-controller]
via GitHub
-
Re: [I] feat: As a Kubernetes user, I want to leverage Gateway API Inference Extension, so that I can use the Gateway API to optimize self-hosting Generative Models on Kubernetes [apisix-ingress-controller]
via GitHub
-
Re: [I] feat: As a Kubernetes user, I want to leverage Gateway API Inference Extension, so that I can use the Gateway API to optimize self-hosting Generative Models on Kubernetes [apisix-ingress-controller]
via GitHub
-
Re: [I] feat: As a Kubernetes user, I want to leverage Gateway API Inference Extension, so that I can use the Gateway API to optimize self-hosting Generative Models on Kubernetes [apisix-ingress-controller]
via GitHub
-
Re: [I] feat: As a Kubernetes user, I want to leverage Gateway API Inference Extension, so that I can use the Gateway API to optimize self-hosting Generative Models on Kubernetes [apisix-ingress-controller]
via GitHub
-
Re: [I] feat: As a Kubernetes user, I want to leverage Gateway API Inference Extension, so that I can use the Gateway API to optimize self-hosting Generative Models on Kubernetes [apisix-ingress-controller]
via GitHub
-
Re: [I] feat: As a Kubernetes user, I want to leverage Gateway API Inference Extension, so that I can use the Gateway API to optimize self-hosting Generative Models on Kubernetes [apisix-ingress-controller]
via GitHub
-
(apisix) branch master updated: fix(forward-auth): extra_headers not resolving variable on $post_arg. (#12435)
ashishtiwari
-
[PR] chore: add websocket e2e test [apisix-ingress-controller]
via GitHub
-
[I] bug: mTLS stream data to external server, APISIX not sending client certificate [apisix]
via GitHub
-
[I] bug: ApisixRoute `spec.http.backends` associated with ApisixUpstream needs to be handled correctly [apisix-ingress-controller]
via GitHub
-
[I] help request: Socket-related errors occur if you build with Custom Plugin as a docker image and run Gateway in a K8s environment [apisix]
via GitHub
-
[I] request help: Socket-related errors occur if you build with Custom Plugin as a docker image and run Gateway in a K8s environment [apisix-java-plugin-runner]
via GitHub
-
[PR] fix: traffic-split weight distribution and add e2e tests [apisix-ingress-controller]
via GitHub
-
Re: [I] Running Apisix with securityContext does not work [apisix-helm-chart]
via GitHub
-
[I] help request: ApisixTLS applies SSL certificate not populated even it says Accepted [apisix]
via GitHub
-
[PR] feat(apisix): service support http3 [apisix-helm-chart]
via GitHub
-
[I] help request: apisix 如何监控websocket的连接情况？ [apisix]
via GitHub
-
(apisix-helm-chart) branch chore/helm-chart-repo updated (a43af84 -> 2ac6c65)
juzhiyuan
-
(apisix-helm-chart) branch chore/helm-chart-repo created (now a43af84)
juzhiyuan
-
[PR] chore: update helm repo url [apisix-helm-chart]
via GitHub
-
[I] help request: Abnormal startup of arm environment apisix [apisix]
via GitHub
-
[I] 当挂载apisix时，如何在同一机器启动多POD？ [apisix]
via GitHub
-
Re: [I] How to specify the size of this parameter value in lua_shared_dict prometheus-metrics? [apisix]
via GitHub
-
[PR] eat: release apisix-ingress-controller 2.0.0-rc3 [apisix-helm-chart]
via GitHub
-
Re: [I] bug: APISIX rewrites yaml configuration file to cause restarting errors [apisix]
via GitHub
-
(apisix-ingress-controller) tag 2.0.0-rc3 created (now 486cc652)
alinsran
-
(apisix) branch master updated: feat(datadog): Improve Datadog plugin tag support (#11943)
baoyuan
-
[I] help request: cpu too high for 3 mins when routes update, we have 40k+routes and 20k+ ups [apisix]
via GitHub
-
(apisix-dashboard) branch dependabot/npm_and_yarn/eslint-9.31.0 deleted (was 15880fdbe)
github-bot
-
Re: [PR] chore(deps-dev): bump eslint from 9.25.1 to 9.31.0 [apisix-dashboard]
via GitHub
-
(apisix-dashboard) branch dependabot/npm_and_yarn/eslint-9.32.0 created (now 38c28e8a6)
github-bot
-
[PR] chore(deps-dev): bump eslint from 9.25.1 to 9.32.0 [apisix-dashboard]
via GitHub
-
[PR] Refactor loop to use range over integer in test [apisix-ingress-controller]
via GitHub
-
Re: [PR] feat: allow to use environment variables for openid-connect plugin [apisix]
via GitHub
-
Re: [PR] fix(discovery): when `endpoint_slices` updated, old endpoints all flush_all/flush_expired [apisix]
via GitHub
-
Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix]
via GitHub
-
Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix]
via GitHub
-
Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix]
via GitHub
-
Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix]
via GitHub
-
Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix]
via GitHub
-
Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix]
via GitHub
-
Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix]
via GitHub
-
Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix]
via GitHub
-
Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix]
via GitHub
-
Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix]
via GitHub
-
Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix]
via GitHub
-
Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix]
via GitHub
-
Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix]
via GitHub
-
Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix]
via GitHub
-
Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix]
via GitHub
-
Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix]
via GitHub
-
Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix]
via GitHub
-
Re: [PR] feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents [apisix]
via GitHub
-
Re: [PR] feat: use custom auth header name [apisix]
via GitHub
-
Re: [PR] fix: PoC fix for #11781, "connect to apisix failed: missing the port number" [apisix]
via GitHub
-
Re: [PR] fix: Updated route name length το 3 times the default, to cope with Ingress Controller problems [apisix]
via GitHub
-
Re: [PR] perf(etcd): refactor some code to improve performance [apisix]
via GitHub
-
Re: [PR] fix: Update apisix-grafana-dashboard.json [apisix]
via GitHub
-
Re: [PR] feat: Add proxy-chain plugin to chain multiple upstream service calls [apisix]
via GitHub
-
Re: [PR] fix: The events array after splitting may contain empty strings, w… [apisix]
via GitHub
-
Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix]
via GitHub
-
(apisix-dashboard) branch master updated: fix: support edit and show vars (#3152)
young
-
Re: [I] bug: route vars cannot be displayed or edited using new admin ui / dashboard [apisix-dashboard]
via GitHub
-
Re: [PR] fix: can not get hostname in redhat [apisix]
via GitHub
-
(apisix-ingress-controller) branch v2.0.0 updated (66c2b0ac -> 486cc652)
alinsran
-
(apisix-ingress-controller) branch master updated: chore: v2.0.0-rc3 release (#2493)
alinsran
-
(apisix-ingress-controller) branch chore/realse-200rc3 deleted (was f766b9c6)
alinsran