Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add possibility to remove AZs #404

Open
apjd opened this issue Aug 16, 2021 · 0 comments
Open

Add possibility to remove AZs #404

apjd opened this issue Aug 16, 2021 · 0 comments
Labels
area/control-plane Control plane related area/disaster-recovery Disaster recovery related area/networking Networking related kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage) priority/3 Priority (lower number equals higher priority)

Comments

@apjd
Copy link

apjd commented Aug 16, 2021

/area control-plane
/area disaster-recovery
/area networking
/kind enhancement
/priority 3

What would you like to be added:

Possibility to remove an Availability Zone (AZ) from a shoot cluster

Why is this needed:

Entering wrong AZ configuration by mistake while setting up a new cluster must be repairable, e.g. entering the same name for "zone2" and "zone3" in the infrastructureConfig. In productive environments, removing and creating a new cluster to correct the AZ configuration may not be possible.

Example of an infrastructureConfig in a shoot.yml:

infrastructureConfig:
      apiVersion: aws.provider.extensions.gardener.cloud/v1alpha1
      kind: InfrastructureConfig
      networks:
        vpc:
          cidr: 10.250.0.0/16
        zones:
          - internal: 10.250.250.0/26
            name: ap-northeast-1a
            public: 10.250.246.0/26
            workers: 10.250.0.0/22
          - internal: 10.250.250.64/26
            name: ap-northeast-1c
            public: 10.250.246.64/26
            workers: 10.250.4.0/22
          - internal: 10.250.250.128/26
            name: ap-northeast-1c 
            public: 10.250.246.128/26
            workers: 10.250.8.0/22

To correct this infrastructureConfig, ap-northeast-1c must be replaced with ap-northeast-1d in one of the last zones.

@rfranzke rfranzke transferred this issue from gardener/gardener Sep 1, 2021
@gardener-robot gardener-robot added area/control-plane Control plane related area/disaster-recovery Disaster recovery related area/networking Networking related kind/enhancement Enhancement, improvement, extension priority/3 Priority (lower number equals higher priority) labels Sep 1, 2021
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Mar 1, 2022
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Aug 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/control-plane Control plane related area/disaster-recovery Disaster recovery related area/networking Networking related kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage) priority/3 Priority (lower number equals higher priority)
Projects
None yet
Development

No branches or pull requests

2 participants