You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@yunikorn.apache.org by "Kinga Marton (Jira)" <ji...@apache.org> on 2021/03/31 16:42:00 UTC

[jira] [Created] (YUNIKORN-625) Use v1 for CertificateSigningRequest instead of v1beta1

Kinga Marton created YUNIKORN-625:
-------------------------------------

             Summary: Use v1 for CertificateSigningRequest instead of v1beta1
                 Key: YUNIKORN-625
                 URL: https://issues.apache.org/jira/browse/YUNIKORN-625
             Project: Apache YuniKorn
          Issue Type: Sub-task
            Reporter: Kinga Marton


Starting from Kubernetes v. 1.19 the CertificateSigningRequest API is promoted to certificates.k8s.io/v1 with the following changes:
 * spec.signerName is now required, and requests for kubernetes.io/legacy-unknown are not allowed to be created via the certificates.k8s.io/v1 API
 * spec.usages is now required, may not contain duplicate values, and must only contain known usages
 * status.conditions may not contain duplicate types
 * status.conditions[*].status is now required
 * status.certificate must be PEM-encoded, and contain only CERTIFICATE blocks (#91685, @liggitt) [SIG API Machinery, Architecture, Auth, CLI and Testing]

See more details at:  https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.19.md



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org