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

Support Gateway BackendTLS field #3153

Open
sjberman opened this issue Feb 20, 2025 · 1 comment
Open

Support Gateway BackendTLS field #3153

sjberman opened this issue Feb 20, 2025 · 1 comment
Labels
area/gateway/extended Relates to all extended features of Gateway enhancement New feature or request
Milestone

Comments

@sjberman
Copy link
Collaborator

As an NGF user,
I want to specify backend TLS settings at the Gateway level,
So that I can easily verify multiple backends by setting configuration in a single place.

I believe that the BackendTLS field gets overridden by a BackendTLSPolicy if one exists.

kubernetes-sigs/gateway-api#3563 has some information on this.

Acceptance

  • Support the BackendTLS field of the Gateway resource
  • ReferenceGrant allows ClientCertificateRef from another namespace to be attached, if specified
@sjberman sjberman added area/gateway/extended Relates to all extended features of Gateway enhancement New feature or request labels Feb 20, 2025
Copy link
Contributor

github-actions bot commented Mar 7, 2025

This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the stale Pull requests/issues with no activity label Mar 7, 2025
@sjberman sjberman removed the stale Pull requests/issues with no activity label Mar 11, 2025
@mpstefan mpstefan added this to the v2.1.0 milestone Mar 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/gateway/extended Relates to all extended features of Gateway enhancement New feature or request
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants