From 9a06c1bc95e446d62854372ad90608d03d535915 Mon Sep 17 00:00:00 2001 From: Chris Tomas Date: Tue, 15 Sep 2020 00:19:50 -0500 Subject: [PATCH 1/2] Updating apiVersion for Certificate Signing Request object #1 Issue detected: There are two references to old apiVersion for CertificateSigningRequest object Ref: CertificateSigningRequest API is promoted to certificates.k8s.io/v1 (https://kubernetes.io/docs/setup/release/notes/#api-change) Fix: Replaced "certificates.k8s.io/v1beta1" by "certificates.k8s.io/v1" --- .../access-authn-authz/certificate-signing-requests.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 4eb1705f4c..7c74cec092 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,7 @@ 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/v1beta1` API version. + 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 @@ -245,7 +245,7 @@ Create a CertificateSigningRequest and submit it to a Kubernetes Cluster via kub ``` cat < Date: Tue, 15 Sep 2020 09:14:52 -0500 Subject: [PATCH 2/2] 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