From 1425384888d6252b8b43dd8343fd835494f90415 Mon Sep 17 00:00:00 2001
From: Chris Tomas <chris.tomas20@gmail.com>
Date: Tue, 15 Sep 2020 09:14:52 -0500
Subject: [PATCH] fix description of signerName

Removed a line related to signerName because the feature is GA.
---
 .../reference/access-authn-authz/certificate-signing-requests.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/content/en/docs/reference/access-authn-authz/certificate-signing-requests.md b/content/en/docs/reference/access-authn-authz/certificate-signing-requests.md
index 7c74cec092..b255aec0d4 100644
--- a/content/en/docs/reference/access-authn-authz/certificate-signing-requests.md
+++ b/content/en/docs/reference/access-authn-authz/certificate-signing-requests.md
@@ -108,7 +108,6 @@ Kubernetes provides built-in signers that each have a well-known `signerName`:
 
 1. `kubernetes.io/legacy-unknown`:  has no guarantees for trust at all. Some distributions may honor these as client
   certs, but that behavior is not standard Kubernetes behavior.
-  This signerName can only be requested in CertificateSigningRequests created via the `certificates.k8s.io/v1` API version.
   Never auto-approved by {{< glossary_tooltip term_id="kube-controller-manager" >}}.
     1. Trust distribution: None.  There is no standard trust or distribution for this signer in a Kubernetes cluster.
     1. Permitted subjects - any