Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

GEP: Allow Multiple Certificate Refs per Gateway Listener #851

Closed
robscott opened this issue Sep 3, 2021 · 5 comments · Fixed by #852
Closed

GEP: Allow Multiple Certificate Refs per Gateway Listener #851

robscott opened this issue Sep 3, 2021 · 5 comments · Fixed by #852
Labels
area/conformance kind/gep PRs related to Gateway Enhancement Proposal(GEP) lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@robscott
Copy link
Member

robscott commented Sep 3, 2021 •
edited
Loading

What would you like to be added:
The CertificateRef field in Listener TLSConfig should be replaced with a CertificateRefs field.

Why this is needed:
This would help with a number of use cases, including:

  • When hostname is empty on the Listener, and Routes attach multiple unique Hostnames
  • Providing RSA and EC certs
  • Temporarily including new and old certs during an upgrade

Relevant Slack thread: https://kubernetes.slack.com/archives/CR0H13KGA/p1629912749150800
@robscott robscott added the kind/gep PRs related to Gateway Enhancement Proposal(GEP) label Sep 3, 2021
@tokers
Copy link
Contributor

tokers commented Sep 4, 2021

Hi, there, what's the status of this GEP? I'd like to implement it :)

@tokers
Copy link
Contributor

tokers commented Sep 7, 2021

/assign

@tokers tokers mentioned this issue Sep 7, 2021
Merged
@robscott robscott mentioned this issue Sep 8, 2021
Merged
@robscott
Copy link
Member Author

robscott commented Aug 1, 2022

Reopening because we need conformance test coverage for this.

@robscott robscott reopened this Aug 1, 2022
@shaneutt shaneutt added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. area/conformance labels Aug 16, 2022
@mikemorris mikemorris mentioned this issue Oct 4, 2022
Closed
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 14, 2022
@shaneutt shaneutt added this to the v0.7.0 milestone Mar 8, 2023
@shaneutt shaneutt added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Mar 14, 2023
@shaneutt shaneutt modified the milestones: v0.7.0, v0.8.0 Apr 6, 2023
@shaneutt shaneutt added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels May 18, 2023
@shaneutt shaneutt removed this from the v0.8.0 milestone May 18, 2023
@robscott
Copy link
Member Author

The only thing left here is conformance tests (and spec clarification) which has more recently been covered by #1330 and #1526, going to close this one out.

@github-project-automation github-project-automation bot moved this from Standard to Implementable in Gateway API Enhancement Proposals (GEPs) May 18, 2023
@shaneutt shaneutt moved this from Implementable to Complete in Gateway API Enhancement Proposals (GEPs) Aug 22, 2023
@robscott robscott moved this from Complete to 5) Standard in Gateway API Enhancement Proposals (GEPs) Dec 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/conformance kind/gep PRs related to Gateway Enhancement Proposal(GEP) lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
Gateway API Enhancement Proposals (GEPs)
Status: Standard
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: support to configure multiple certificates on GatewayTLSConfig tokers/gateway-api
5 participants
@robscott @shaneutt @tokers @k8s-ci-robot @k8s-triage-robot