Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Undefined
Fix Version/s: 4.19.z
Affects Version/s: 4.19.z, 4.20.0
Component/s: kube-apiserver
Labels:
- pre-merge-tested

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:

4.19.z
Release Blocker:
None
Sprint:
None

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

PX Impact Score:

Release Note Status:
Done
Release Note Type:
Release Note Not Required
Release Note Text:
N/A

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

This is a clone of issue OCPBUGS-60628. The following is the description of the original issue:
—
Description of problem:

Some resources don't have RefreshOnlyWhenExpired set, so when their metadata is updated sidecar controllers are reverting back the changes. They should work on the resource only when it has expired

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

How reproducible:

Steps to Reproduce:

    1.
    2.
    3.

Actual results:

Expected results:

Additional info:

clones

OCPBUGS-60628 Ensure that RefreshOnlyWhenExpired is set for every controlled resource

Verified

is blocked by

OCPBUGS-60628 Ensure that RefreshOnlyWhenExpired is set for every controlled resource

Verified

links to

openshift/cluster-kube-apiserver-operator#1901: [release-4.19] OCPBUGS-60677: certrotation: ensure that all rotated secrets/configmaps have RefreshOnlyWhenExpired set

Assignee:: Vadim Rutkovsky

Reporter:: Vadim Rutkovsky

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/08/20 9:34 AM

Updated:: 2025/09/02 3:31 PM

Resolved:: 2025/09/02 3:31 PM