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

BackendTLSPolicy ancestor should include section name #1888

Closed
kate-osborn opened this issue Apr 26, 2024 · 2 comments
Closed

BackendTLSPolicy ancestor should include section name #1888

kate-osborn opened this issue Apr 26, 2024 · 2 comments

Comments

@kate-osborn
Copy link
Contributor

Currently, the BackendTLSPolicy status ancestor object is the entire Gateway object.

However, the BackendTLSPolicy status may differ from listener to listener on a Gateway. The policy status ancestor object should include the section name for the Gateway to differentiate between Gateway listeners.

Copy link
Contributor

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 May 11, 2024
@sjberman sjberman removed the stale Pull requests/issues with no activity label May 14, 2024
@mpstefan
Copy link
Collaborator

We should be able to determine any issues with status by examining the Gateway object status if needed.

@mpstefan mpstefan closed this as not planned Won't fix, can't repro, duplicate, stale May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

3 participants