Skip to content

WIP: CORS-4288: docs(azure): Restructure tested VM families with Series-based organization#10314

Open
gpei wants to merge 1 commit intoopenshift:mainfrom
gpei:CORS-4288
Open

WIP: CORS-4288: docs(azure): Restructure tested VM families with Series-based organization#10314
gpei wants to merge 1 commit intoopenshift:mainfrom
gpei:CORS-4288

Conversation

@gpei
Copy link
Contributor

@gpei gpei commented Feb 14, 2026

Transform the Tested Azure instance type documentation from simple bullet lists to structured tables organized by Azure VM Series categories. This improves clarity by aligning with Azure's official VM documentation structure[1].

Changes for x86_64 (106 families):

  • Organize families by category: General Purpose, Memory Optimized, Compute Optimized, Storage Optimized, GPU Accelerated and HPC
  • Add table format showing: Azure VM Series → Family Name

Changes for ARM64 (13 families):

  • Apply same table structure with ARM64-specific categories

The documentation now provides clear guidance on selecting appropriate VM sizes for OpenShift clusters on Azure, with examples organized by workload type and Azure's official Series naming.

[1] https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/overview?tabs=breakdownseries%2Cgeneralsizelist%2Ccomputesizelist%2Cmemorysizelist%2Cstoragesizelist%2Cgpusizelist%2Cfpgasizelist%2Chpcsizelist#list-of-vm-size-families-by-type

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 14, 2026

@gpei: This pull request references CORS-4288 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 epic to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Transform the Tested Azure instance type documentation from simple bullet lists to structured tables organized by Azure VM Series categories. This improves clarity by aligning with Azure's official VM documentation structure[1].

Changes for x86_64 (106 families):

  • Organize families by category: General Purpose, Memory Optimized, Compute Optimized, Storage Optimized, GPU Accelerated and HPC
  • Add table format showing: Azure VM Series → Family Name

Changes for ARM64 (13 families):

  • Apply same table structure with ARM64-specific categories

The documentation now provides clear guidance on selecting appropriate VM sizes for OpenShift clusters on Azure, with examples organized by workload type and Azure's official Series naming.

[1] https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/overview?tabs=breakdownseries%2Cgeneralsizelist%2Ccomputesizelist%2Cmemorysizelist%2Cstoragesizelist%2Cgpusizelist%2Cfpgasizelist%2Chpcsizelist#list-of-vm-size-families-by-type

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 Feb 14, 2026
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 14, 2026
@openshift-ci openshift-ci bot requested review from rna-afk and sadasu February 14, 2026 07:43
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 14, 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 sadasu 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
Copy link
Contributor

openshift-ci bot commented Feb 14, 2026

@gpei: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/azure-ovn-marketplace-images 4e573ac link false /test azure-ovn-marketplace-images
ci/prow/e2e-azurestack 4e573ac link false /test e2e-azurestack
ci/prow/azure-private 4e573ac link false /test azure-private

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

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

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants