OCPBUGS-55694: Clarify vSphere static IP IPPool vs IPAddressClaim usage

[smunaval]

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

Issue:
https://issues.redhat.com/browse/OCPBUGS-55694

Link to docs preview:
Affected modules:

• modules/nodes-vsphere-machine-set-concept-static-ip.adoc
• modules/nodes-vsphere-machine-set-scaling-static-ip.adoc
  Published 4.22 page:
  https://docs.redhat.com/en/documentation/openshift_container_platform/4.22/html/postinstallation_configuration/post-install-node-tasks

QE review:

• QE has approved this change.

Additional information:
The vSphere static IP scaling docs mention IPAddressClaims without explaining that the installer-created IPPool is different from Whereabouts/Multus IPPool objects. The manual IPAddressClaim status patch is required for the default installer IPPool when no IPAM controller does the association, so that step is now marked Optional with that note.

Verified still present in OpenShift 4.22:

• Published 4.22 post-installation node tasks still omit the installer IPPool vs Whereabouts distinction and still present the status patch as a required step.

[openshift-ci-robot]

@smunaval: This pull request references Jira Issue OCPBUGS-55694, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

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/OCPBUGS-55694

Link to docs preview:
Preview is generated after an org member comments /ok-to-test.
Affected modules:

• modules/nodes-vsphere-machine-set-concept-static-ip.adoc
• modules/nodes-vsphere-machine-set-scaling-static-ip.adoc
  Published 4.22 page:
  https://docs.redhat.com/en/documentation/openshift_container_platform/4.22/html/postinstallation_configuration/post-install-node-tasks

QE review:

• QE has approved this change.

Additional information:
The vSphere static IP scaling docs mention IPAddressClaims without explaining that the installer-created IPPool is different from Whereabouts/Multus IPPool objects. The manual IPAddressClaim status patch is required for the default installer IPPool when no IPAM controller does the association, so that step is now marked Optional with that note.

Verified still present in OpenShift 4.22:

• Published 4.22 post-installation node tasks still omit the installer IPPool vs Whereabouts distinction and still present the status patch as a required step.

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]

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.

[openshift-ci-robot]

@smunaval: This pull request references Jira Issue OCPBUGS-55694, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

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/OCPBUGS-55694

Link to docs preview:
Affected modules:

• modules/nodes-vsphere-machine-set-concept-static-ip.adoc
• modules/nodes-vsphere-machine-set-scaling-static-ip.adoc
  Published 4.22 page:
  https://docs.redhat.com/en/documentation/openshift_container_platform/4.22/html/postinstallation_configuration/post-install-node-tasks

QE review:

• QE has approved this change.

Additional information:
The vSphere static IP scaling docs mention IPAddressClaims without explaining that the installer-created IPPool is different from Whereabouts/Multus IPPool objects. The manual IPAddressClaim status patch is required for the default installer IPPool when no IPAM controller does the association, so that step is now marked Optional with that note.

Verified still present in OpenShift 4.22:

• Published 4.22 post-installation node tasks still omit the installer IPPool vs Whereabouts distinction and still present the status patch as a required step.

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.