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.

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

GEP: Complete Backend mTLS Configuration #3155

Open
robscott opened this issue Jun 13, 2024 · 3 comments
Open

GEP: Complete Backend mTLS Configuration #3155

robscott opened this issue Jun 13, 2024 · 3 comments
Labels
kind/gep PRs related to Gateway Enhancement Proposal(GEP)
Milestone

Comments

@robscott
Copy link
Member

What would you like to be added:
I'd like to bundle three related changes together as part of a broader effort to enable Backend mTLS configuration:

  1. Configuration for the client certificate Gateways should use when connecting to Backends
  2. Ability to specify SANs on BackendTLSPolicy
  3. Add TLS options to BackendTLSPolicy to mirror TLS config on Gateways

Of those, 2 may not seem quite as obvious as the rest. The rationale is that SPIFFE is very commonly used as part of mTLS, and is not compatible with our current requirement that the cert served by the backend must match the SNI used to connect to the backend. Adding the option to separately specify SANs would also enable the use of SPIFFE IDs with BackendTLSPolicy.

All of Envoy, HAProxy, and NGINX should be able to support these capabilities, but there will be some nuance in terms of where the configuration lives.

Why this is needed:
One of the core goals for Gateway API is to provide more secure capabilities than Ingress. This feature would finally allow backend mTLS to be configured natively within Kubernetes APIs, and would likely provide opportunities for closer integration between ingress-focused implementations of this API and mesh-focused implementations.

@robscott robscott added the kind/gep PRs related to Gateway Enhancement Proposal(GEP) label Jun 13, 2024
@robscott robscott added this to the v1.2.0 milestone Jun 13, 2024
@robscott robscott changed the title Complete Backend mTLS Configuration GEP: Complete Backend mTLS Configuration Jun 13, 2024
@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue 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 Sep 11, 2024
@youngnick
Copy link
Contributor

/remove-lifecycle stale

The changes described here are heading in to Experimental in v1.2.

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 11, 2024
@youngnick
Copy link
Contributor

See #3180 and #3304 for more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/gep PRs related to Gateway Enhancement Proposal(GEP)
Projects
None yet
Development

No branches or pull requests

4 participants