[enterprise-4.10] clarification about availability zones and tagging

[yrro]

Which section(s) is the issue in?

https://docs.openshift.com/container-platform/4.10/installing/installing_azure/installing-azure-vnet.html#installation-configuration-parameters-additional-azure_installing-azure-vnet

What needs fixing?

There is a prominent note,

You cannot customize Azure Availability Zones or Use tags to organize your Azure resources with an Azure cluster.

I don't understand what it means.

• You can specify .platform.azure.zone in install-config.yaml to say which zones you want your machines in.
• You can tag the resource group after it's been created (or can you? will the cluster revert any added tags? if so this should be stated explicitly in the note).

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[yrro]

/remove-lifecycle stale

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[yrro]

/remove-lifecycle stale
/ilfecycle frozen

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[yrro]

/remove-lifecycle stale

[yrro]

/lifecycle frozen