You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[enterprise-4.10] clarification about availability zones and tagging #45617
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).
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.
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.
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.
Activity
openshift-bot commentedon Aug 11, 2022
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 commentedon Aug 11, 2022
/remove-lifecycle stale
openshift-bot commentedon Nov 10, 2022
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 commentedon Nov 10, 2022
/remove-lifecycle stale
/ilfecycle frozen
openshift-bot commentedon Feb 9, 2023
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 commentedon Feb 9, 2023
/remove-lifecycle stale
yrro commentedon Feb 9, 2023
/lifecycle frozen