Skip to content

Align Route Protocol Selection with Gateway API Listeners #7900

@programmer04

Description

@programmer04

Is there an existing issue for this?

  • I have searched the existing issues

Does this enhancement require public documentation?

  • I have added an Acceptance Criteria item for adding and/or adjusting public documentation (if applicable)

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

  • main
  • 3.5.x
  • 3.4.x

Proposed Solution

No response

Additional information

No response

Acceptance Criteria

  • clearly documented in CHANGELOG.md
  • each case covered with a test

Metadata

Metadata

Assignees

Labels

area/maintenanceCleanup, refactoring, and other maintenance improvements that don't change functionality.

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions