Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Pull request overview
Updates the Kubernetes operator guide to clarify that Redis-backed session-to-pod routing is conditional on Redis session storage being configured, avoiding the implication that Redis is always used whenever backendReplicas > 1.
Changes:
- Adds a new “Session routing for backend replicas” subsection under Horizontal scaling.
- Adjusts phrasing to distinguish Redis session storage behavior vs. client-IP affinity behavior.
- Adds an explanatory note about when
SessionStorageWarningfires.
When backendReplicas > 1, the proxy runner only uses Redis for session-to-pod routing when Redis session storage is actually configured. The previous wording implied Redis was always used, then contradicted itself in the next paragraph. Closes #727 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
| but `sessionAffinity: ClientIP` is unreliable behind NAT or shared egress IPs. | ||
| For stateful workloads or when per-session routing must remain consistent across | ||
| backend pods, Redis session storage is strongly recommended when | ||
| `backendReplicas > 1`. Stateless workloads can use `sessionAffinity: None`. |
There was a problem hiding this comment.
In this note you refer to spec.replicas > 1, but later switch to backendReplicas > 1 without the spec. prefix. For consistency with the rest of the doc’s field-path style (and the earlier spec.backendReplicas bullet), consider using spec.backendReplicas > 1 in both occurrences here.
| `backendReplicas > 1`. Stateless workloads can use `sessionAffinity: None`. | |
| `spec.backendReplicas > 1`. Stateless workloads can use `sessionAffinity: None`. |
|
Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
Summary
backendReplicas > 1Closes #727
Type of change
Test plan