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
- More robust validation for `HTTPRoute`, when an unsupported feature is used, and the route refers to existing and non-existing `Gateway`, it will be rejected.
-**Changed (potentially breaking):** As part of our secure-by-default initiative, everything out of the box relies on
302
+
defaults from Kong Gateway. It may break existing configurations that relied on previous implicit protocol behavior
303
+
(access via http will result `426` status code.), when version of Kong Gateway will change.
304
+
- For `HTTPRoute`, protocol now matches the attached Gateway listener protocol (and when `parentRef.sectionName` is set, it must match that specific listener). When `parentRef.sectionName` is not specified it binds to all `Gateway`s listeners.
305
+
- For `Ingress`, default protocol relies on Kong Gateway, can be set explicitly via `konghq.com/protocols: "http"` (or `https`)
306
+
annotation on particular `Ingress`.
307
+
- Sanitize the plugin configuration when `--dump-sensitive-config` isn't set.
- More robust validation for `HTTPRoute`, when an unsupported feature is used, and the route refers to existing and non-existing `Gateway`, it will be rejected.
0 commit comments