generated from kubernetes/kubernetes-template-project
-
Notifications
You must be signed in to change notification settings - Fork 588
Closed
Labels
help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Milestone
Description
What happened:
The Gateway spec states
gateway-api/apis/v1beta1/gateway_types.go
Lines 72 to 77 in c2d863b
// Each listener in a Gateway must have a unique combination of Hostname, | |
// Port, and Protocol. Below combinations are considered Core and MUST be | |
// supported: | |
// | |
// 1. Port: 80, Protocol: HTTP | |
// 2. Port: 443, Protocol: HTTPS |
However, one of the base conformance Gateways includes a listener on port 8080 --
port: 8080 |
Since base Gateways always get deployed as part of running the conformance tests, that Gateway with port 8080 listener becomes a blocker for running conformance tests for implementations that do not support port 8080.
What you expected to happen:
Conformance tests only use ports 80 and 443 in base manifests.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
robscott, kate-osborn and vepatel
Metadata
Metadata
Assignees
Labels
help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.