You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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.targetRefOct 30, 2024
The docs at https://linkerd.io/2-edge/reference/authorization-policy/#authorizationpolicy currently claim the following:
The docs for
TargetRef
here: https://linkerd.io/2-edge/reference/authorization-policy/#targetref then claim that it has a field callednamespace
:This seems to imply that it's possible to set
.spec.targetRef.namespace
forAuthorizationPolicies
. However, it is not, and the CRD only contains thenamespace
field forrequiredAuthenticationRefs
.I'm not sure if this is a bug in the Linkerd CRDs or the docs, but this is a contradiction.
The text was updated successfully, but these errors were encountered: