Skip to content

Commit a55b105

Browse files
committed
Add links to CertificateSigningRequest API
Signed-off-by: Craig Rodrigues <[email protected]>
1 parent 19f3ec2 commit a55b105

File tree

1 file changed

+9
-4
lines changed

1 file changed

+9
-4
lines changed

content/en/docs/reference/access-authn-authz/certificate-signing-requests.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -31,14 +31,16 @@ There is also experimental (alpha) support for distributing [trust bundles](#clu
3131
{{< feature-state for_k8s_version="v1.19" state="stable" >}}
3232

3333

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
3536
by a denoted signer, after which the request may be approved or denied before
3637
finally being signed.
3738

3839

3940
### Request signing process
4041

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
4244
be issued, based on a signing request.
4345
The CertificateSigningRequest object includes a PEM-encoded PKCS#10 signing request in
4446
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
285287
to allow for explanatory text as described in [section 5.2 of RFC7468](https://www.rfc-editor.org/rfc/rfc7468#section-5.2).
286288

287289
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:
289292

290293
```yaml
291294
apiVersion: certificates.k8s.io/v1
@@ -505,7 +508,9 @@ openssl req -new -key myuser.key -out myuser.csr -subj "/CN=myuser"
505508

506509
### Create a CertificateSigningRequest {#create-certificatessigningrequest}
507510

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/).
509514

510515
```shell
511516
cat <<EOF | kubectl apply -f -

0 commit comments

Comments
 (0)