1733109 – Cert validity increases from 1 year to 10 years during rotation

Bug 1733109 - Cert validity increases from 1 year to 10 years during rotation

Summary: Cert validity increases from 1 year to 10 years during rotation

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	kube-apiserver
Sub Component:
Version:	4.2.0
Hardware:	All
OS:	Linux
Priority:	high
Severity:	high
Target Milestone:	---
Target Release:	4.2.0
Assignee:	Tomáš Nožička
QA Contact:	Xingxing Xia
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:	1721586 1733232
TreeView+	depends on / blocked

Reported:	2019-07-25 08:44 UTC by Sunil Choudhary
Modified:	2019-10-16 06:33 UTC (History)
CC List:	3 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Clones:	1733232 (view as bug list)
Environment:
Last Closed:	2019-10-16 06:33:28 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Github	openshift cluster-kube-apiserver-operator pull 533	0	'None'	closed	Bug 1733109: Fix kube-apiserver-to-kubelet-signer validity	2020-08-13 17:49:54 UTC
Red Hat Product Errata	RHBA-2019:2922	0	None	None	None	2019-10-16 06:33:43 UTC

Description Sunil Choudhary 2019-07-25 08:44:17 UTC

Description of problem:

Cert validity increases from 1 year to 10 years during rotation. In this instance manually forced rotation by deleting annotations.

$ oc get secret kube-apiserver-to-kubelet-signer -o yaml 
apiVersion: v1
data:
[...]
kind: Secret
metadata:
  annotations:
    auth.openshift.io/certificate-issuer: kube-apiserver-to-kubelet-signer
    auth.openshift.io/certificate-not-after: "2020-07-23T09:09:05Z"
    auth.openshift.io/certificate-not-before: "2019-07-24T09:09:05Z"
  creationTimestamp: "2019-07-24T09:22:14Z"
  name: kube-apiserver-to-kubelet-signer
  namespace: openshift-kube-apiserver-operator
  resourceVersion: "254"
  selfLink: /api/v1/namespaces/openshift-kube-apiserver-operator/secrets/kube-apiserver-to-kubelet-signer
  uid: 85e31801-adf4-11e9-a73a-0282cb83bab0
type: SecretTypeTLS

After deleting annotations:

$ oc get secret kube-apiserver-to-kubelet-signer -o yaml 
apiVersion: v1
data:
[...]
kind: Secret
metadata:
  annotations:
    auth.openshift.io/certificate-issuer: openshift-kube-apiserver-operator_kube-apiserver-to-kubelet-signer@1563964343
    auth.openshift.io/certificate-not-after: "2029-07-21T10:32:23Z"
    auth.openshift.io/certificate-not-before: "2019-07-24T10:32:22Z"
  creationTimestamp: "2019-07-24T09:22:14Z"
  labels:
    auth.openshift.io/managed-certificate-type: signer
  name: kube-apiserver-to-kubelet-signer
  namespace: openshift-kube-apiserver-operator
  resourceVersion: "29119"
  selfLink: /api/v1/namespaces/openshift-kube-apiserver-operator/secrets/kube-apiserver-to-kubelet-signer
  uid: 85e31801-adf4-11e9-a73a-0282cb83bab0
type: SecretTypeTLS

Version-Release number of selected component (if applicable):

4.2.0-0.nightly-2019-07-24-000310

Comment 2 zhou ying 2019-07-30 01:53:26 UTC

Confirmed with Payload: 4.2.0-0.nightly-2019-07-28-222114, the issue has fixed:
[root@dhcp-140-138 ~]# oc get secret kube-apiserver-to-kubelet-signer -o yaml 
apiVersion: v1
data:
  [...]
kind: Secret
metadata:
  annotations:
    auth.openshift.io/certificate-issuer: openshift-kube-apiserver-operator_kube-apiserver-to-kubelet-signer@1564451491
    auth.openshift.io/certificate-not-after: "2020-07-29T01:51:32Z"
    auth.openshift.io/certificate-not-before: "2019-07-30T01:51:31Z"
  creationTimestamp: "2019-07-29T01:22:10Z"
  labels:
    auth.openshift.io/managed-certificate-type: signer
  name: kube-apiserver-to-kubelet-signer
  namespace: openshift-kube-apiserver-operator
  resourceVersion: "394495"
  selfLink: /api/v1/namespaces/openshift-kube-apiserver-operator/secrets/kube-apiserver-to-kubelet-signer
  uid: 49825ae1-b19f-11e9-86af-0293dfa65d10
type: SecretTypeTLS

Comment 3 errata-xmlrpc 2019-10-16 06:33:28 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2922

Note You need to log in before you can comment on or make changes to this bug.