Adding GEP-3567: Gateway TLS Updates for HTTP/2 Connection Coalescing #3572
Conversation
k8s-ci-robot
added
release-note-none
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: robscott The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
approved
|
|
||
| ### C) Top Level Gateway TLS Config for Client Cert Validation | ||
|
|
||
| GEP-91 will be updated to move this configuration to a new top level Gateway TLS |
There was a problem hiding this comment.
How is this expected to interact with gateway merging/ListenerSets?
|
/cc |
|
|
||
| GEP-91 will be updated to move this configuration to a new top level Gateway TLS | ||
| config instead of per-listener. | ||
|
|
There was a problem hiding this comment.
do you mean move or copy the client cert validation field ? imo there's still value in per listener client validation for non intersecting hostnames
There was a problem hiding this comment.
I'd argue that it should be "move", but the only thing I'm trying to communicate here is that we'll need follow up changes in GEP-91. Will update the wording to be more open-ended here.
What type of PR is this?
/kind gep
What this PR does / why we need it:
This is a relatively small GEP that may not need to be a GEP, but creating one for the purpose of record keeping. Hoping to get at least A and B in v1.3. This is tracked by #3567.
Does this PR introduce a user-facing change?: