OSDOCS-4486: add Azure AZ warning in MAPI compute spec

[jeana-redhat]

Version(s):
4.12+

Issue:
OSDOCS-4486

Link to docs preview:
Sample YAML for a compute machine set custom resource on Azure

• standard
• infrastructure

QE review:

• QE has approved this change.

Additional information:

[openshift-ci-robot]

@jeana-redhat: This pull request references OSDOCS-4486 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 bug to target the "4.19.0" version, but no target version was set.

Details

In response to this:

Version(s):
4.12+

Issue:
OSDOCS-4486

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

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]

@jeana-redhat: This pull request references OSDOCS-4486 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 bug to target the "4.19.0" version, but no target version was set.

Details

In response to this:

Version(s):
4.12+

Issue:
OSDOCS-4486

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

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]

@jeana-redhat: This pull request references OSDOCS-4486 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 bug to target the "4.19.0" version, but no target version was set.

Details

In response to this:

Version(s):
4.12+

Issue:
OSDOCS-4486

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

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.

[ocpdocs-previewbot]

🤖 Wed Mar 05 17:16:06 - Prow CI generated the docs preview:

https://89658--ocpdocs-pr.netlify.app/openshift-enterprise/latest/machine_management/creating-infrastructure-machinesets.html
https://89658--ocpdocs-pr.netlify.app/openshift-enterprise/latest/machine_management/creating_machinesets/creating-machineset-azure.html

[openshift-ci-robot]

@jeana-redhat: This pull request references OSDOCS-4486 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 bug to target the "4.19.0" version, but no target version was set.

Details

In response to this:

Version(s):
4.12+

Issue:
OSDOCS-4486

Link to docs preview:
Sample YAML for a compute machine set custom resource on Azure

• standard
• infrastructure

QE review:

• QE has approved this change.

Additional information:

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]

@jeana-redhat: all tests passed!

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.

[openshift-ci-robot]

@jeana-redhat: This pull request references OSDOCS-4486 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 bug to target the "4.19.0" version, but no target version was set.

Details

In response to this:

Version(s):
4.12+

Issue:
OSDOCS-4486

Link to docs preview:
Sample YAML for a compute machine set custom resource on Azure

• standard
• infrastructure

QE review:

• QE has approved this change.

Additional information:

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.

[shellyyang1989]

cc @sunzhaohua2

[JoelSpeed]

LGTM

[sunzhaohua2]

/lgtm
I tested on 4.19, create machine without defining zone, create pvc and pod, though the zone between node labels and pv affinity are not match, pod can be deployed succeed. But I think this warning is valid, before we had a similar bug about region's mistmatch between node labels and pv affinity. https://bugzilla.redhat.com/show_bug.cgi?id=1860128

$ oc get machine                                                          
NAME                                         PHASE     TYPE              REGION   ZONE   AGE
kataci06123718-fqb9h-master-0                Running   Standard_D8s_v3   eastus   2      6h
kataci06123718-fqb9h-master-1                Running   Standard_D8s_v3   eastus   3      6h
kataci06123718-fqb9h-master-2                Running   Standard_D8s_v3   eastus   1      6h
kataci06123718-fqb9h-worker-eastus2-7psgt    Running   Standard_D4s_v3   eastus   2      5h54m
kataci06123718-fqb9h-worker-eastus3-j7jlz    Running   Standard_D4s_v3   eastus   3      5h54m
kataci06123718-fqb9h-worker-eastus33-gdshv   Running   Standard_D4s_v3   eastus          171m
$ oc get po                                                       
task-pv-pod                                           1/1     Running   0          7m35s
$ oc get node kataci06123718-fqb9h-worker-eastus33-gdshv -o yaml
    topology.kubernetes.io/region: eastus
    topology.kubernetes.io/zone: "0"
 $ oc get pv pvc-60eeb887-1391-40e6-986d-aafb88093512 -o yaml
  nodeAffinity:
    required:
      nodeSelectorTerms:
      - matchExpressions:
        - key: topology.disk.csi.azure.com/zone
          operator: In
          values:
          - ""

[openshift-ci-robot]

@jeana-redhat: This pull request references OSDOCS-4486 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 bug to target the "4.19.0" version, but no target version was set.

Details

In response to this:

Version(s):
4.12+

Issue:
OSDOCS-4486

Link to docs preview:
Sample YAML for a compute machine set custom resource on Azure

• standard
• infrastructure

QE review:

• QE has approved this change.

Additional information:

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.

[lpettyjo]

LGTM!

[jeana-redhat]

/cherrypick enterprise-4.19

[jeana-redhat]

/cherrypick enterprise-4.18

[jeana-redhat]

/cherrypick enterprise-4.17

[jeana-redhat]

/cherrypick enterprise-4.16

[jeana-redhat]

/cherrypick enterprise-4.15

[jeana-redhat]

/cherrypick enterprise-4.14

[jeana-redhat]

/cherrypick enterprise-4.13

[jeana-redhat]

/cherrypick enterprise-4.12

[openshift-cherrypick-robot]

@jeana-redhat: new pull request created: #89766

Details

In response to this:

/cherrypick enterprise-4.19

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-cherrypick-robot]

@jeana-redhat: new pull request created: #89767

Details

In response to this:

/cherrypick enterprise-4.18

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-cherrypick-robot]

@jeana-redhat: new pull request created: #89768

Details

In response to this:

/cherrypick enterprise-4.17

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-cherrypick-robot]

@jeana-redhat: new pull request created: #89769

Details

In response to this:

/cherrypick enterprise-4.16

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-cherrypick-robot]

@jeana-redhat: new pull request created: #89770

Details

In response to this:

/cherrypick enterprise-4.15

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-cherrypick-robot]

@jeana-redhat: new pull request created: #89771

Details

In response to this:

/cherrypick enterprise-4.14

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-cherrypick-robot]

@jeana-redhat: new pull request created: #89772

Details

In response to this:

/cherrypick enterprise-4.13

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-cherrypick-robot]

@jeana-redhat: new pull request created: #89773

Details

In response to this:

/cherrypick enterprise-4.12

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.