Loading...

XML

Word

Printable

Type: Bug
Resolution: Can't Do
Priority: Undefined
Fix Version/s: None
Affects Version/s: 4.14.z, 4.15.z, 4.17.z, 4.16.z, 4.18.z, 4.19.0
Component/s: kube-apiserver
Labels:
- feature-team-cert
- rits-work

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
None
Regression:
None

Target Backport Versions:

4.14.z, 4.15.z, 4.17.z, 4.16.z, 4.18.z
Target Version:

4.18.z
Release Blocker:
None
Sprint:
None

RH Private Keywords:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

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:

clones

OCPBUGS-54208 Backport UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver

Verified

is blocked by

OCPBUGS-54208 Backport UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver

Verified

Assignee:: Vadim Rutkovsky

Reporter:: OpenShift Prow Bot

Need Info From:: None

Contributors:: None

QA Contact:: Ke Wang

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2025/05/13 2:28 AM

Updated:: 2025/09/13 5:50 PM

Resolved:: 2025/05/13 7:00 AM