Skip to content

OSDOCS-17437: Document nodeStatusMaxImages for KubeVirt hosted workers - #119576

Open
smunaval wants to merge 1 commit into
openshift:mainfrom
smunaval:OSDOCS-17437-hcp-kubelet-max-images
Open

OSDOCS-17437: Document nodeStatusMaxImages for KubeVirt hosted workers#119576
smunaval wants to merge 1 commit into
openshift:mainfrom
smunaval:OSDOCS-17437-hcp-kubelet-max-images

Conversation

@smunaval

@smunaval smunaval commented Sep 9, 2026

Copy link
Copy Markdown

Version(s):
main (in-development OpenShift 5.1). Still present in published 4.18-4.22 docs.

Issue:
https://issues.redhat.com/browse/OSDOCS-17437

Link to docs preview:
Affected module: modules/hcp-kubeconf-nodepool.adoc
Published 4.22 page:
https://docs.redhat.com/en/documentation/openshift_container_platform/4.22/html/hosted_control_planes/hcp-machine-config

QE review:

  • QE has approved this change.

Additional information:
Hosted clusters on OpenShift Virtualization default kubelet nodeStatusMaxImages to 50. When a worker has more than 50 images, the truncated image list can break imageLocality scoring. Docs now note this and show nodeStatusMaxImages: -1 in the kubelet ConfigMap example.

Verified still present in OpenShift 4.22:

  • Published 4.22 hosted control planes kubelet configuration topic does not mention nodeStatusMaxImages.

Recommend disabling the kubelet 50-image reporting limit to keep imageLocality scheduling balanced.

Co-authored-by: Cursor <cursoragent@cursor.com>
@openshift-ci-robot

openshift-ci-robot commented Sep 9, 2026

Copy link
Copy Markdown

@smunaval: This pull request references OSDOCS-17437 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "5.1.0" version, but no target version was set.

Details

In response to this:

Version(s):
main (in-development OpenShift 5.1). Still present in published 4.18-4.22 docs.

Issue:
https://issues.redhat.com/browse/OSDOCS-17437

Link to docs preview:
Preview is generated after an org member comments /ok-to-test.
Affected module: modules/hcp-kubeconf-nodepool.adoc
Published 4.22 page:
https://docs.redhat.com/en/documentation/openshift_container_platform/4.22/html/hosted_control_planes/hcp-machine-config

QE review:

  • QE has approved this change.

Additional information:
Hosted clusters on OpenShift Virtualization default kubelet nodeStatusMaxImages to 50. When a worker has more than 50 images, the truncated image list can break imageLocality scoring. Docs now note this and show nodeStatusMaxImages: -1 in the kubelet ConfigMap example.

Verified still present in OpenShift 4.22:

  • Published 4.22 hosted control planes kubelet configuration topic does not mention nodeStatusMaxImages.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 9, 2026
@openshift-ci openshift-ci Bot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Sep 9, 2026
@openshift-ci

openshift-ci Bot commented Sep 9, 2026

Copy link
Copy Markdown

Hi @smunaval. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants