Skip to content

RFE-7972: Azure data disk IOPS/throughput configuration#2017

Open
chdeshpa-hue wants to merge 1 commit into
openshift:masterfrom
chdeshpa-hue:rfe-7972-azure-data-disk-iops-throughput
Open

RFE-7972: Azure data disk IOPS/throughput configuration#2017
chdeshpa-hue wants to merge 1 commit into
openshift:masterfrom
chdeshpa-hue:rfe-7972-azure-data-disk-iops-throughput

Conversation

@chdeshpa-hue
Copy link
Copy Markdown

Summary

Enhancement proposal for configuring provisioned IOPS (diskIOPSReadWrite) and throughput (diskMBpsReadWrite) on Azure PremiumV2_LRS and UltraSSD_LRS data disks during OpenShift cluster installation and day-2 machine scaling.

This extends the existing data disk support (SPLAT-2133/PR #1779) to allow fine-grained performance tuning and cost optimization — Azure PremiumV2 bills IOPS and throughput independently of disk capacity.

Key Points

  • Extends DataDiskManagedDiskParameters in openshift/api with two new optional fields
  • Adds PremiumV2_LRS to the existing StorageAccountType enum
  • Full-stack propagation: install-config → CAPZ → Machine API → MAPO → Azure ARM API
  • Validated on live Azure environment (OpenShift 4.22-rc.3) with custom builds
  • No new CRDs or webhooks — extends existing MAO webhook validation

Implementation PRs (ready, pending this enhancement approval)

  1. openshift/api — Add PremiumV2_LRS + IOPS/MBps to DataDiskManagedDiskParameters
  2. openshift/installer — Support IOPS/MBps in install-config + CAPZ wiring
  3. machine-api-provider-azure — Wire IOPS/MBps to Azure ARM API
  4. machine-api-operator — Webhook validation for IOPS/MBps

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

Made with Cursor

Enhancement proposal for configuring provisioned IOPS and throughput
on Azure PremiumV2_LRS and UltraSSD_LRS data disks during OpenShift
cluster installation and day-2 machine scaling.

Tracking: https://issues.redhat.com/browse/RFE-7972
Co-authored-by: Cursor <cursoragent@cursor.com>
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 20, 2026

@chdeshpa-hue: This pull request references RFE-7972 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 for configuring provisioned IOPS (diskIOPSReadWrite) and throughput (diskMBpsReadWrite) on Azure PremiumV2_LRS and UltraSSD_LRS data disks during OpenShift cluster installation and day-2 machine scaling.

This extends the existing data disk support (SPLAT-2133/PR #1779) to allow fine-grained performance tuning and cost optimization — Azure PremiumV2 bills IOPS and throughput independently of disk capacity.

Key Points

  • Extends DataDiskManagedDiskParameters in openshift/api with two new optional fields
  • Adds PremiumV2_LRS to the existing StorageAccountType enum
  • Full-stack propagation: install-config → CAPZ → Machine API → MAPO → Azure ARM API
  • Validated on live Azure environment (OpenShift 4.22-rc.3) with custom builds
  • No new CRDs or webhooks — extends existing MAO webhook validation

Implementation PRs (ready, pending this enhancement approval)

  1. openshift/api — Add PremiumV2_LRS + IOPS/MBps to DataDiskManagedDiskParameters
  2. openshift/installer — Support IOPS/MBps in install-config + CAPZ wiring
  3. machine-api-provider-azure — Wire IOPS/MBps to Azure ARM API
  4. machine-api-operator — Webhook validation for IOPS/MBps

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

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 20, 2026
@openshift-ci openshift-ci Bot requested review from dougbtv and ingvagabund May 20, 2026 05:57
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 20, 2026

[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 dougbtv 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:

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

@openshift-ci openshift-ci Bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label May 20, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 20, 2026

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.

@chdeshpa-hue
Copy link
Copy Markdown
Author

cc @jcpowermac @lnguyen1401

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants