Fix AuthorizationPolicy docs to indicate that targetRef cannot include a namespace #1928
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e a namespace Signed-off-by: Alex Leong <[email protected]>
kflynn
approved these changes
Feb 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
An AuthorizationPolicy cannot target a resource in another namespace, as this would allow one namespace to grant access to another's resources. This is codified in the CRD as the
targetRefdoes not have anamespacefield. However, our docs incorrect claim that it does have anamespacefield.We correct this error by removing references to the non-existent field and clarifying that only the namespace which can be targeted is the local one.