RFE-9321: Nutanix configurable storage container for principal OS disk

[chdeshpa-hue]

Summary

Enhancement proposal to expose an explicit osDisk.storageConfig.storageContainer field in install-config and Machine API for Nutanix IPI clusters. This allows administrators to control which Nutanix storage container is used for VM principal OS/system disks during installation and MachineSet scale-out.

Tracking: https://issues.redhat.com/browse/RFE-9321

Motivation

Today, OS disk storage container placement on Nutanix is implicit — determined by where the RHCOS preloaded image resides. This is undocumented, not guaranteed across Prism versions, and provides no day-2 control via MachineSets.

Data disks already have storageConfig.storageContainer support. This EP extends the same pattern to the system disk.

Key Design Decisions

• Reuses existing StorageConfig / StorageResourceReference types from data disks
• Supports UUID, name, and failure-domain referenceName references
• Explicit container overrides implicit image-based placement (Option A)
• Feature gate: NutanixOSDiskStorageContainer (DevPreview → TechPreview → GA)
• Backward compatible: field is optional, omission preserves current behavior

Components Affected

Component	Change
openshift/installer	Types, validation, asset generation
openshift/api	NutanixMachineProviderConfig.SystemDiskStorageConfig
cluster-api-provider-nutanix	CreateSystemDiskSpec storage container ref
machine-api-operator	Webhook validation (if required)
Documentation	Install guide update

/cc @yanhua121 @patrickdillon @JoelSpeed

Made with Cursor

[openshift-ci-robot]

@chdeshpa-hue: This pull request references RFE-9321 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 feature request to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

Enhancement proposal to expose an explicit osDisk.storageConfig.storageContainer field in install-config and Machine API for Nutanix IPI clusters. This allows administrators to control which Nutanix storage container is used for VM principal OS/system disks during installation and MachineSet scale-out.

Tracking: https://issues.redhat.com/browse/RFE-9321

Motivation

Today, OS disk storage container placement on Nutanix is implicit — determined by where the RHCOS preloaded image resides. This is undocumented, not guaranteed across Prism versions, and provides no day-2 control via MachineSets.

Data disks already have storageConfig.storageContainer support. This EP extends the same pattern to the system disk.

Key Design Decisions

• Reuses existing StorageConfig / StorageResourceReference types from data disks
• Supports UUID, name, and failure-domain referenceName references
• Explicit container overrides implicit image-based placement (Option A)
• Feature gate: NutanixOSDiskStorageContainer (DevPreview → TechPreview → GA)
• Backward compatible: field is optional, omission preserves current behavior

Components Affected

Component	Change
openshift/installer	Types, validation, asset generation
openshift/api	NutanixMachineProviderConfig.SystemDiskStorageConfig
cluster-api-provider-nutanix	CreateSystemDiskSpec storage container ref
machine-api-operator	Webhook validation (if required)
Documentation	Install guide update

/cc @yanhua121 @patrickdillon @JoelSpeed

Made with Cursor

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]

@chdeshpa-hue: GitHub didn't allow me to request PR reviews from the following users: yanhua121.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

Summary

Enhancement proposal to expose an explicit osDisk.storageConfig.storageContainer field in install-config and Machine API for Nutanix IPI clusters. This allows administrators to control which Nutanix storage container is used for VM principal OS/system disks during installation and MachineSet scale-out.

Tracking: https://issues.redhat.com/browse/RFE-9321

Motivation

Today, OS disk storage container placement on Nutanix is implicit — determined by where the RHCOS preloaded image resides. This is undocumented, not guaranteed across Prism versions, and provides no day-2 control via MachineSets.

Data disks already have storageConfig.storageContainer support. This EP extends the same pattern to the system disk.

Key Design Decisions

• Reuses existing StorageConfig / StorageResourceReference types from data disks
• Supports UUID, name, and failure-domain referenceName references
• Explicit container overrides implicit image-based placement (Option A)
• Feature gate: NutanixOSDiskStorageContainer (DevPreview → TechPreview → GA)
• Backward compatible: field is optional, omission preserves current behavior

Components Affected

Component	Change
openshift/installer	Types, validation, asset generation
openshift/api	NutanixMachineProviderConfig.SystemDiskStorageConfig
cluster-api-provider-nutanix	CreateSystemDiskSpec storage container ref
machine-api-operator	Webhook validation (if required)
Documentation	Install guide update

/cc @yanhua121 @patrickdillon @JoelSpeed

Made with Cursor

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign joelanford for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @chdeshpa-hue. 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.