You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(interceptor): clean up direct-pod routing TLS and defaults
- Default DirectPodRouting to true (matching Knative behavior)
- Remove dead forwardingTLSCfg/TLSClientConfig code superseded by
DialTLSContext
- Soften newTLSDialer to fall back to dial-address hostname when
context has no server name, instead of hard-failing
- Fix notifyCh comment to reflect actual broadcast semantics
(ready-state transitions only, not every change)
- Document dual-stack limitation in collectServiceState
Signed-off-by: Mikhail Fedosin <mfedosin@redhat.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ This changelog keeps track of work items that have been completed and are ready
35
35
36
36
-**General**: Add `staticRoutes` to InterceptorRoute for defining routes that should not trigger autoscaling, such as health checks, redirects, and maintenance pages. Supports `responseMode: WhenUnavailable` (forward to backend when ready, static response otherwise) and `responseMode: Always` (always serve static response) ([#1622](https://github.com/kedacore/http-add-on/issues/1622))
37
37
-**General**: TODO ([#TODO](https://github.com/kedacore/http-add-on/issues/TODO))
38
-
-**Interceptor**: Add `KEDA_HTTP_DIRECT_POD_ROUTING` environment variable (`true` | `false`, default `false`). When enabled, the interceptor routes requests directly to a ready pod IP instead of through the Service ClusterIP, bypassing kube-proxy and other Service-layer features (Service-level NetworkPolicy, session affinity, topology-aware routing). ([#1473](https://github.com/kedacore/http-add-on/issues/1473))
38
+
-**Interceptor**: Add `KEDA_HTTP_DIRECT_POD_ROUTING` environment variable (`true` | `false`, default `true`). When enabled, the interceptor routes requests directly to a ready pod IP instead of through the Service ClusterIP, bypassing kube-proxy and other Service-layer features (Service-level NetworkPolicy, session affinity, topology-aware routing). ([#1473](https://github.com/kedacore/http-add-on/issues/1473))
0 commit comments