-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.14.z, 4.15.z, 4.17.z, 4.16.z, 4.18.z, 4.19.0
Description of problem:
In order to avoid self-signed loopback certificate in every apiserver from expiring we should cherrypick https://github.com/kubernetes/kubernetes/pull/130047 and backport it to 4.16.z
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- blocks
-
OCPBUGS-56082 [release-4.19]Backport UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver
-
- Closed
-
-
OCPBUGS-56083 Backport https://github.com/kubernetes/kubernetes/pull/130047 to 4.16
-
- Closed
-
- is cloned by
-
OCPBUGS-56082 [release-4.19]Backport UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver
-
- Closed
-
-
OCPBUGS-56083 Backport https://github.com/kubernetes/kubernetes/pull/130047 to 4.16
-
- Closed
-
- relates to
-
OCPBUGS-50505 Identify in-memory certificates and ensure they are stored in secrets/on disk
-
- Closed
-
- links to