OSDOCS-17043_2_a: CQA Azure machine set assembly and core modules#114616
Conversation
27684ad to
130ec70
Compare
242b2be to
8bfdd95
Compare
|
/label merge-review-needed |
jeana-redhat
left a comment
There was a problem hiding this comment.
A couple small items to address here, overall good!
/remove-label merge-review-in-progress
/remove-label merge-review-needed
| .Additional resources | ||
|
|
||
| * link:https://docs.microsoft.com/en-us/azure/virtual-machines/ephemeral-os-disks[Ephemeral OS disks for {azure-short} VMs ({azure-full} documentation)] | ||
| * link:https://docs.microsoft.com/en-us/azure/virtual-machines/ephemeral-os-disks[Ephemeral OS disks for {azure-first} VMs ({azure-short} documentation)] |
There was a problem hiding this comment.
This should be reverted (the linked article is "Ephemeral OS disks for Azure VMs" so {azure-short} is correct)
| * link:https://docs.microsoft.com/en-us/azure/virtual-machines/ephemeral-os-disks[Ephemeral OS disks for {azure-first} VMs ({azure-short} documentation)] | |
| * link:https://docs.microsoft.com/en-us/azure/virtual-machines/ephemeral-os-disks[Ephemeral OS disks for {azure-short} VMs ({azure-full} documentation)] |
| * link:https://docs.microsoft.com/en-us/azure/aks/azure-disk-customer-managed-keys#create-an-azure-key-vault-instance[Create an {azure-short} Key Vault instance ({azure-short} documentation)] | ||
| * link:https://docs.microsoft.com/en-us/azure/aks/azure-disk-customer-managed-keys#create-an-instance-of-a-diskencryptionset[Create an instance of a disk encryption set ({azure-short} documentation)] | ||
| * link:https://docs.microsoft.com/en-us/azure/aks/azure-disk-customer-managed-keys#grant-the-diskencryptionset-access-to-key-vault[Grant the disk encryption set access to key vault ({azure-short} documentation)] |
There was a problem hiding this comment.
Revert these. SSG states:
Write prerequisites as checks that are true or that the user must have completed before they begin a procedure. They can be actions that the user, another person, or piece of technology has completed. Prerequisites can also include items that the user must have ready before beginning the procedure.
and
Avoid using imperative formations.
| * link:https://docs.microsoft.com/en-us/azure/aks/azure-disk-customer-managed-keys#create-an-azure-key-vault-instance[Create an {azure-short} Key Vault instance ({azure-short} documentation)] | |
| * link:https://docs.microsoft.com/en-us/azure/aks/azure-disk-customer-managed-keys#create-an-instance-of-a-diskencryptionset[Create an instance of a disk encryption set ({azure-short} documentation)] | |
| * link:https://docs.microsoft.com/en-us/azure/aks/azure-disk-customer-managed-keys#grant-the-diskencryptionset-access-to-key-vault[Grant the disk encryption set access to key vault ({azure-short} documentation)] | |
| * link:https://docs.microsoft.com/en-us/azure/aks/azure-disk-customer-managed-keys#create-an-azure-key-vault-instance[You created an {azure-short} Key Vault instance ({azure-short} documentation)] | |
| * link:https://docs.microsoft.com/en-us/azure/aks/azure-disk-customer-managed-keys#create-an-instance-of-a-diskencryptionset[You created an instance of a disk encryption set ({azure-short} documentation)] | |
| * link:https://docs.microsoft.com/en-us/azure/aks/azure-disk-customer-managed-keys#grant-the-diskencryptionset-access-to-key-vault[You granted the disk encryption set access to key vault ({azure-short} documentation)] |
| where: | ||
|
|
||
| `<infrastructure_id>`:: Specifies the infrastructure ID that is based on the cluster ID that you set when you provisioned the cluster. If you have the OpenShift CLI installed, you can obtain the infrastructure ID by running the following command: | ||
| `<infrastructure_id>`:: Specifies the infrastructure ID that is based on the cluster ID that you set when you provisioned the cluster. If you have the {product-title} CLI installed, you can obtain the infrastructure ID by running the following command: |
There was a problem hiding this comment.
It is actually "the OpenShift CLI" - if you want to avoid the name in text you can use the oc attribute here
| `<infrastructure_id>`:: Specifies the infrastructure ID that is based on the cluster ID that you set when you provisioned the cluster. If you have the {product-title} CLI installed, you can obtain the infrastructure ID by running the following command: | |
| `<infrastructure_id>`:: Specifies the infrastructure ID that is based on the cluster ID that you set when you provisioned the cluster. If you have the {oc-first} installed, you can obtain the infrastructure ID by running the following command: |
| [NOTE] | ||
| ==== | ||
| The value of the `spec.template.spec.providerSpec.value.zone` parameter specifies the zone within your region to place machines on. Ensure that your region supports the zone that you specify. If your region supports availability zones, you must specify the zone. Specifying the zone avoids volume node affinity failure when a pod requires a persistent volume attachment. To do this, you can create a compute machine set for each zone in the same region. | ||
| The value of the `spec.template.spec.providerSpec.value.zone` parameter specifies the zone within your region to place machines on. If your region supports availability zones, you must specify the zone. |
There was a problem hiding this comment.
Why remove the statement "Ensure that your region supports the zone that you specify."?
|
@jeana-redhat: Those labels are not set on the issue: DetailsIn response to this:
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. |
8bfdd95 to
95081f0
Compare
95081f0 to
e8b2c36
Compare
|
@brendan-daly-red-hat: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/cherrypick enterprise-4.20 |
|
/cherrypick enterprise-4.21 |
|
/cherrypick enterprise-4.22 |
|
@brendan-daly-red-hat: new pull request created: #115937 DetailsIn response to this:
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. |
|
@brendan-daly-red-hat: new pull request created: #115938 DetailsIn response to this:
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. |
|
@brendan-daly-red-hat: new pull request created: #115939 DetailsIn response to this:
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. |
|
/cherry-pick enterprise-5.0 |
|
@brendan-daly-red-hat: new pull request created: #115942 DetailsIn response to this:
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. |
Versions:
4.20+
Issue:
https://redhat.atlassian.net/browse/OSDOCS-17043
Link to docs preview:
QE review:
Additional information: