You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Chaoran Yu (Jira)" <ji...@apache.org> on 2021/10/26 04:25:00 UTC
[jira] [Resolved] (YUNIKORN-625) Use v1 for
CertificateSigningRequest instead of v1beta1
[ https://issues.apache.org/jira/browse/YUNIKORN-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chaoran Yu resolved YUNIKORN-625.
---------------------------------
Resolution: Done
> Use v1 for CertificateSigningRequest instead of v1beta1
> -------------------------------------------------------
>
> Key: YUNIKORN-625
> URL: https://issues.apache.org/jira/browse/YUNIKORN-625
> Project: Apache YuniKorn
> Issue Type: Improvement
> Reporter: Kinga Marton
> Assignee: Kinga Marton
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.0.0
>
>
> 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: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org