-
Bug
-
Resolution: Done-Errata
-
Undefined
-
4.14.z, 4.15.z, 4.17.z, 4.16.z, 4.18.z, 4.19.0
This is a clone of issue OCPBUGS-58054. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-57196. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-56835. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-56082. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-54208. The following is the description of the original issue:
—
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-59473 [release-4.14]Backport UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver
-
- New
-
-
OCPBUGS-59474 [release-4.15]Backport UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver
-
- POST
-
- clones
-
OCPBUGS-58054 [release-4.16]Backport UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver
-
- Closed
-
- is blocked by
-
OCPBUGS-58054 [release-4.16]Backport UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver
-
- Closed
-
- is cloned by
-
OCPBUGS-59473 [release-4.14]Backport UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver
-
- New
-
-
OCPBUGS-59474 [release-4.15]Backport UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver
-
- POST
-
- links to
-
RHBA-2025:12370 OpenShift Container Platform 4.15.56 bug fix update