Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: None
Affects Version/s: 4.19.0
Component/s: oauth-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:
None
Target Version:
None
Release Blocker:
Rejected
Sprint:
None

RH Private Keywords:

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

PX Review Complete:
PX Impact Score:

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

Description of problem:

    https://issues.redhat.com/browse/OCPBUGS-48557 and https://issues.redhat.com/browse/OCPBUGS-46024 were about in-memory certificate which is not stored in secret or on disk.
We should find a way to identify such secrets and ensure that they are generated by the operator and saved in the secrets, so that they would appear on TLS registry and we could rotate them effortlessly

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

How reproducible:

Steps to Reproduce:

    1.
    2.
    3.

Actual results:

Expected results:

Additional info:

is related to

OCPBUGS-55335 LoopbackClientConfig is required when creating apiserver

New

OCPBUGS-61759 In-memory certificate expiration date in openshift-apiserver namespace is too short for ELS term 2

New

OCPBUGS-61760 In-memory certificate expiration date in oauth-apiserver namespace is too short for ELS term 2

New

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

Verified

links to

Upstream Commit: Certificate expiration - Reboot/upgrade expected

Assignee:: Vadim Rutkovsky

Reporter:: Vadim Rutkovsky

Need Info From:: None

Contributors:: None

QA Contact:: Xingxing Xia

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 10 Start watching this issue

Created:: 2025/02/10 2:23 PM

Updated:: 2025/10/01 12:29 PM

Resolved:: 2025/04/24 11:36 AM