From 759249b113f67debc667f8351e5655dfbe590916 Mon Sep 17 00:00:00 2001 From: Josh Van Leeuwen Date: Thu, 4 Feb 2021 13:48:49 +0000 Subject: [PATCH] Update design/20210203.certificate-request-identity.md Co-authored-by: Jake Sanders Signed-off-by: Jake Sanders --- design/20210203.certificate-request-identity.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/design/20210203.certificate-request-identity.md b/design/20210203.certificate-request-identity.md index d08e3a22b..d8b02b130 100644 --- a/design/20210203.certificate-request-identity.md +++ b/design/20210203.certificate-request-identity.md @@ -54,7 +54,7 @@ configuring auditing is available, it is often not preferable and an anti-pattern to make runtime decisions on historical audit logs. The upstream [Kubernetes certificates -`CertificateSigningRequest`](https://github.com/kubernetes/api/blob/master/certificates/v1/types.go#L41) +`CertificateSigningRequest`](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#certificatesigningrequest-v1-certificates-k8s-io) API has identity as part of the resource. As the project intends to align and likely make this resource compatible with cert-manager in some way, the `CertificateRequest` should expose identical identity details. This means