Is there an existing issue for this?
Does this enhancement require public documentation?
Problem Statement
To ensure consistency across the Kong ecosystem, we need to update how KongRoute protocols are determined.
Set the respective protocol based on configured listeners, examples:
- If an HTTPRoute belongs to a Gateway with an HTTP listener, the route protocol must be set to http.
- If an HTTPRoute specifies a sectionName in its parentRef, the protocol must match the specific listener defined in that section
Ingress support - Since the standard Ingress resource doesn't define protocols, these should now follow the Gateway default (HTTPS) to maintain a secure posture.
Target with this change
Proposed Solution
No response
Additional information
No response
Acceptance Criteria
Is there an existing issue for this?
Does this enhancement require public documentation?
Problem Statement
To ensure consistency across the Kong ecosystem, we need to update how KongRoute protocols are determined.
Set the respective protocol based on configured listeners, examples:
Ingress support - Since the standard Ingress resource doesn't define protocols, these should now follow the Gateway default (HTTPS) to maintain a secure posture.
Target with this change
main3.5.x3.4.xProposed Solution
No response
Additional information
No response
Acceptance Criteria