From a2b19e1dded81f80a5b7ffcca0e56c6d075b91bd Mon Sep 17 00:00:00 2001 From: Eliza Weisman Date: Fri, 18 Aug 2023 15:58:39 -0700 Subject: [PATCH] s/CRDs/CRs --- linkerd.io/content/2-edge/features/server-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/linkerd.io/content/2-edge/features/server-policy.md b/linkerd.io/content/2-edge/features/server-policy.md index 99bc42cc46..ac5af89ee1 100644 --- a/linkerd.io/content/2-edge/features/server-policy.md +++ b/linkerd.io/content/2-edge/features/server-policy.md @@ -91,7 +91,7 @@ authentication rules to targets. The general pattern for Linkerd's dynamic, fine-grained policy is to define the traffic target that must be protected (via a combination of `Server` and -[`HTTPRoute`] CRDs); define the types of authentication that are required before +[`HTTPRoute`] CRs); define the types of authentication that are required before access to that traffic is permitted (via `MeshTLSAuthentication` and `NetworkAuthentication`); and then define the policy that maps authentication to target (via an `AuthorizationPolicy`).