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

AuthorizationPolicy docs falsely imply that namespace can be set for spec.targetRef #1866

Open
netthier opened this issue Oct 30, 2024 · 0 comments

Comments

@netthier
Copy link

The docs at https://linkerd.io/2-edge/reference/authorization-policy/#authorizationpolicy currently claim the following:

An AuthorizationPolicy spec may contain the following top level fields:

  • targetRef: A TargetRef which references a resource to which the authorization policy applies
  • requiredAuthenticationRefs: A list of TargetRefs representing the required authentications. In the case of multiple entries, all authentications must match.

The docs for TargetRef here: https://linkerd.io/2-edge/reference/authorization-policy/#targetref then claim that it has a field called namespace:

namespace: The namespace of the target resource. When unspecified (or empty string), this refers to the local namespace of the policy.

This seems to imply that it's possible to set .spec.targetRef.namespace for AuthorizationPolicies. However, it is not, and the CRD only contains the namespace field for requiredAuthenticationRefs.
I'm not sure if this is a bug in the Linkerd CRDs or the docs, but this is a contradiction.

@netthier netthier changed the title AuthorizationPolicy docs falsely imply that namespace can be set for targetRef AuthorizationPolicy docs falsely imply that namespace can be set for spec.targetRef Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant