Skip to content

[enterprise-4.10] clarification about availability zones and tagging #45617

Open

Description

@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).

Activity

  1. openshift-bot commented on Aug 11, 2022

    @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

  2. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Aug 11, 2022
  3. yrro commented on Aug 11, 2022

    @yrro
    Author

    /remove-lifecycle stale

  4. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Aug 11, 2022
  5. openshift-bot commented on Nov 10, 2022

    @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

  6. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Nov 10, 2022
  7. yrro commented on Nov 10, 2022

    @yrro
    Author

    /remove-lifecycle stale
    /ilfecycle frozen

  8. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Nov 10, 2022
  9. openshift-bot commented on Feb 9, 2023

    @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

  10. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Feb 9, 2023
  11. yrro commented on Feb 9, 2023

    @yrro
    Author

    /remove-lifecycle stale

  12. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Feb 9, 2023
  13. yrro commented on Feb 9, 2023

    @yrro
    Author

    /lifecycle frozen

  14. added
    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
    on Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions