Skip to content

[OCPBUGS#56411]: Document creating an IPPool for static IP machine scaling - #115964

Open
harsh-thakare wants to merge 1 commit into
openshift:mainfrom
harsh-thakare:OCPBUGS-56411-document-ippool-creation
Open

[OCPBUGS#56411]: Document creating an IPPool for static IP machine scaling#115964
harsh-thakare wants to merge 1 commit into
openshift:mainfrom
harsh-thakare:OCPBUGS-56411-document-ippool-creation

Conversation

@harsh-thakare

Copy link
Copy Markdown

Summary

  • Adds a procedure for creating an IPPool resource used when scaling machine sets with static IP addresses.
  • Clarifies that the Whereabouts IPPool API (whereabouts.cni.cncf.io/v1alpha1) is for pod secondary-network IPAM and is not used for Machine API static IP allocation.
  • Notes that DHCP-backed and static-IP machine sets can be scaled independently.

Test plan

  • Confirm the new module renders under Machine scaling with static IP addresses in the Netlify PR preview.
  • Verify callouts and example YAML for IPPool creation are clear and consistent with the existing machine set examples (ipamcontroller.example.io).
  • Confirm the Whereabouts distinction note is accurate for QE/docs review.
  • QE review for OCP 4.16+.

Version(s):
4.16+

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

Link to docs preview:

QE review:

  • QE has approved this change.

Made with Cursor

Add procedure steps for creating an IPPool resource used by machine sets
that scale with static IP addresses, and clarify that the Whereabouts
IPPool API is not used for Machine API static IP allocation.

Signed-off-by: Harshal Thakare <hthakare@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@openshift-ci openshift-ci Bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jul 21, 2026
@openshift-ci

openshift-ci Bot commented Jul 21, 2026

Copy link
Copy Markdown

Hi @harsh-thakare. 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

needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant