@@ -31,14 +31,16 @@ There is also experimental (alpha) support for distributing [trust bundles](#clu
31
31
{{< feature-state for_k8s_version="v1.19" state="stable" >}}
32
32
33
33
34
- A CertificateSigningRequest (CSR) resource is used to request that a certificate be signed
34
+ A [ CertificateSigningRequest] ( /docs/reference/kubernetes-api/authentication-resources/certificate-signing-request-v1/ )
35
+ (CSR) resource is used to request that a certificate be signed
35
36
by a denoted signer, after which the request may be approved or denied before
36
37
finally being signed.
37
38
38
39
39
40
### Request signing process
40
41
41
- The CertificateSigningRequest resource type allows a client to ask for an X.509 certificate
42
+ The [ CertificateSigningRequest] ( /docs/reference/kubernetes-api/authentication-resources/certificate-signing-request-v1/ )
43
+ resource type allows a client to ask for an X.509 certificate
42
44
be issued, based on a signing request.
43
45
The CertificateSigningRequest object includes a PEM-encoded PKCS #10 signing request in
44
46
the ` spec.request ` field. The CertificateSigningRequest denotes the signer (the
@@ -285,7 +287,8 @@ Non-PEM content may appear before or after the CERTIFICATE PEM blocks and is unv
285
287
to allow for explanatory text as described in [ section 5.2 of RFC7468] ( https://www.rfc-editor.org/rfc/rfc7468#section-5.2 ) .
286
288
287
289
When encoded in JSON or YAML, this field is base-64 encoded.
288
- A CertificateSigningRequest containing the example certificate above would look like this:
290
+ A [ CertificateSigningRequest] ( /docs/reference/kubernetes-api/authentication-resources/certificate-signing-request-v1/ )
291
+ containing the example certificate above would look like this:
289
292
290
293
``` yaml
291
294
apiVersion : certificates.k8s.io/v1
@@ -505,7 +508,9 @@ openssl req -new -key myuser.key -out myuser.csr -subj "/CN=myuser"
505
508
506
509
# ## Create a CertificateSigningRequest {#create-certificatessigningrequest}
507
510
508
- Create a CertificateSigningRequest and submit it to a Kubernetes Cluster via kubectl. Below is a script to generate the CertificateSigningRequest.
511
+ Create a [CertificateSigningRequest](/docs/reference/kubernetes-api/authentication-resources/certificate-signing-request-v1/)
512
+ and submit it to a Kubernetes Cluster via kubectl. Below is a script to generate the
513
+ [CertificateSigningRequest](/docs/reference/kubernetes-api/authentication-resources/certificate-signing-request-v1/).
509
514
510
515
` ` ` shell
511
516
cat <<EOF | kubectl apply -f -
0 commit comments