Loading...

XML

Word

Printable

Type: Bug
Resolution: Not a Bug
Priority: Undefined
Fix Version/s: None
Affects Version/s: 4.20
Component/s: Image Registry
Labels:
None

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

Hide

None

Show
None
Story Points:
None
Severity:
Low
Regression:
None
Architecture:

All

Target Backport Versions:
None
Target Version:
None
Release Blocker:
None
Sprint:
None

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

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:

As a part of KPI effort for Telco use case, we're tracking number of pods in the SNO cluster as each pod comes with a slight overhead. If a new pod is added and it's optional, we're looking for a way to not use this extra functionality if it's not required.

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

    4.20

How reproducible:

    100%

Steps to Reproduce:

    1. Deploy 4.20 SNO cluster
    2. Check pods in openshift-image-registry namespace

Actual results:

    New pod node-ca is present

Expected results:

    No new pods or a parameter to disable new pod creation

Additional info:

Assignee:: Flavian Missi

Reporter:: Alexander Gurenko

Need Info From:: None

Contributors:: None

QA Contact:: XiuJuan Wang

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2025/09/09 10:33 AM

Updated:: 2025/09/09 4:27 PM

Resolved:: 2025/09/09 4:27 PM