Skip to content

Enable TLSRoutes to route to another namespace #2139

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

Closed
mpstefan opened this issue Jun 13, 2024 · 0 comments · Fixed by #2379
Closed

Enable TLSRoutes to route to another namespace #2139

mpstefan opened this issue Jun 13, 2024 · 0 comments · Fixed by #2379
Assignees
Labels
enhancement New feature or request refined Requirements are refined and the issue is ready to be implemented.
Milestone

Comments

@mpstefan
Copy link
Member

mpstefan commented Jun 13, 2024

As a user of NGF utilizing TLS passthrough
I want to enable my TLSRoute to route to a service in another namespace
So that my single Gateway object can route my TLS traffic to my applications in other namespaces.

Acceptance

Given that NGF is installed in namespace A
And given a TLSRoute is created referencing a service in namespace B
When a referenceGrant is created allowing the TLSRoute to access namespace B
Then incoming traffic to the Gateway in namespace A that matches the TLSRoute criteria will be forwarded to the service in namespace B

Dev Notes

As part of this issue, add tests to change_processor_test.go to cover TLSRoute CRUD events including ReferenceGrants.

@mpstefan mpstefan added this to the v1.4.0 milestone Jun 13, 2024
@mpstefan mpstefan added refined Requirements are refined and the issue is ready to be implemented. enhancement New feature or request labels Jun 13, 2024
@mpstefan mpstefan modified the milestones: v1.4.0, v2.1.0 Jul 24, 2024
@kate-osborn kate-osborn self-assigned this Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request refined Requirements are refined and the issue is ready to be implemented.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants