Fix link to moved HA guide in gardener repo

docs/alicloud/readme.md

@@ -20,7 +20,7 @@ You can run the above in parallel, even of the same type, as long as the targete
 
 ### Why?
 
-Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal [here](https://github.com/gardener/gardener/blob/master/docs/usage/shoot_high_availability_best_practices.md). To put your solution to the test, this module will help you.
+Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal [here](https://github.com/gardener/gardener/blob/master/docs/usage/high-availability/shoot_high_availability_best_practices.md). To put your solution to the test, this module will help you.
 
 ## Usage
 

docs/aws/readme.md

@@ -20,7 +20,7 @@ You can run the above in parallel, even of the same type, as long as the targete
 
 ### Why?
 
-Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal [here](https://github.com/gardener/gardener/blob/master/docs/usage/shoot_high_availability_best_practices.md). To put your solution to the test, this module will help you.
+Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal [here](https://github.com/gardener/gardener/blob/master/docs/usage/high-availability/shoot_high_availability_best_practices.md). To put your solution to the test, this module will help you.
 
 ## Usage
 

docs/azure/readme.md

@@ -20,7 +20,7 @@ You can run the above in parallel, even of the same type, as long as the targete
 
 ### Why?
 
-Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal [here](https://github.com/gardener/gardener/blob/master/docs/usage/shoot_high_availability_best_practices.md). To put your solution to the test, this module will help you.
+Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal [here](https://github.com/gardener/gardener/blob/master/docs/usage/high-availability/shoot_high_availability_best_practices.md). To put your solution to the test, this module will help you.
 
 ## Usage
 

docs/garden/readme.md

@@ -26,7 +26,7 @@ This module also provides [`chaostoolkit`](https://chaostoolkit.org) probes:
 
 ### Why?
 
-Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal [here](https://github.com/gardener/gardener/blob/master/docs/usage/shoot_high_availability_best_practices.md). To put your solution to the test, this module will help you.
+Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal [here](https://github.com/gardener/gardener/blob/master/docs/usage/high-availability/shoot_high_availability_best_practices.md). To put your solution to the test, this module will help you.
 
 The probe on the other hand is targeting Gardener developers and output-qualification and puts Gardener HA as such to the test, which requires automation as Gardener-managed clusters perform many functions in parallel.
 

docs/gcp/readme.md

@@ -22,7 +22,7 @@ You can run the above in parallel, even of the same type, as long as the targete
 
 ### Why?
 
-Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal [here](https://github.com/gardener/gardener/blob/master/docs/usage/shoot_high_availability_best_practices.md). To put your solution to the test, this module will help you.
+Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal [here](https://github.com/gardener/gardener/blob/master/docs/usage/high-availability/shoot_high_availability_best_practices.md). To put your solution to the test, this module will help you.
 
 ## Usage
 

docs/k8s/readme.md

@@ -29,7 +29,7 @@ This module also provides [`chaostoolkit`](https://chaostoolkit.org) probes:
 
 ### Why?
 
-Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal [here](https://github.com/gardener/gardener/blob/master/docs/usage/shoot_high_availability_best_practices.md). To put your solution to the test, this module will help you.
+Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal [here](https://github.com/gardener/gardener/blob/master/docs/usage/high-availability/shoot_high_availability_best_practices.md). To put your solution to the test, this module will help you.
 
 The probe on the other hand is targeting Kubernetes provider developers and output-qualification and puts cluster HA as such to the test, which requires automation as Kubernetes clusters may perform many functions in parallel.
 

docs/openstack/readme.md

@@ -20,7 +20,7 @@ You can run the above in parallel, even of the same type, as long as the targete
 
 ### Why?
 
-Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal [here](https://github.com/gardener/gardener/blob/master/docs/usage/shoot_high_availability_best_practices.md). To put your solution to the test, this module will help you.
+Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal [here](https://github.com/gardener/gardener/blob/master/docs/usage/high-availability/shoot_high_availability_best_practices.md). To put your solution to the test, this module will help you.
 
 ## Usage
 

docs/tutorials/getting_started.md

@@ -113,7 +113,7 @@ Now let's break 🪓 your cluster. Be advised that this experiment will be destr
 
 Being unreachable will trigger service endpoint and load balancer de-registration (when the node's grace period lapses) as well as eventually pod eviction and machine replacement (which will continue to fail under test). We won't run the experiment long enough for all of these effects to materialize, but the longer you run it, the more will happen, up to temporarily giving up/going into "back-off" for the affected worker pool in that zone. You will also see that the Kubernetes cluster autoscaler will try to create a new machine almost immediately, if pods are pending for the affected zone (which will initially fail under test, but may succeed later, which again depends on the runtime of the experiment and whether or not the cluster autoscaler goes into "back-off" or not).
 
-But for now, all of this doesn't matter as we want to start "small". You can later read up more on the various settings and effects in our [best practices guide on high availability](https://github.com/gardener/gardener/blob/master/docs/usage/shoot_high_availability_best_practices.md).
+But for now, all of this doesn't matter as we want to start "small". You can later read up more on the various settings and effects in our [best practices guide on high availability](https://github.com/gardener/gardener/blob/master/docs/usage/high-availability/shoot_high_availability_best_practices.md).
 
 Please create a new experiment file, this time with this content:
 
@@ -188,7 +188,7 @@ Normally, you would not only run [actions](https://chaostoolkit.org/reference/co
 <!-- BEGIN of section that must be kept in sync with sibling tutorial -->
 ## High Availability
 
-Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal in our [best practices guide on high availability](https://github.com/gardener/gardener/blob/master/docs/usage/shoot_high_availability_best_practices.md).
+Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal in our [best practices guide on high availability](https://github.com/gardener/gardener/blob/master/docs/usage/high-availability/shoot_high_availability_best_practices.md).
 
 Thank you for your interest in Gardener chaos engineering and making your workload more resilient.
 

docs/tutorials/python_scripting.md

@@ -122,7 +122,7 @@ You can see how both failure simulations were launched in parallel and how one f
 <!-- BEGIN of section that must be kept in sync with sibling tutorial -->
 ## High Availability
 
-Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal in our [best practices guide on high availability](https://github.com/gardener/gardener/blob/master/docs/usage/shoot_high_availability_best_practices.md).
+Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal in our [best practices guide on high availability](https://github.com/gardener/gardener/blob/master/docs/usage/high-availability/shoot_high_availability_best_practices.md).
 
 Thank you for your interest in Gardener chaos engineering and making your workload more resilient.
 

docs/vsphere/readme.md

@@ -20,7 +20,7 @@ You can run the above in parallel, even of the same type, as long as the targete
 
 ### Why?
 
-Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal [here](https://github.com/gardener/gardener/blob/master/docs/usage/shoot_high_availability_best_practices.md). To put your solution to the test, this module will help you.
+Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal [here](https://github.com/gardener/gardener/blob/master/docs/usage/high-availability/shoot_high_availability_best_practices.md). To put your solution to the test, this module will help you.
 
 ## Usage
 

readme.md

@@ -79,6 +79,6 @@ In some cases, we extended the original upstream open source incubator extension
 
 ## Implementing High Availability and Tolerating Zone Outages
 
-Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal [here](https://github.com/gardener/gardener/blob/master/docs/usage/shoot_high_availability_best_practices.md). While many recommendations are general enough, the examples are specific in how to achieve this in a Gardener-managed cluster and where/how to tweak the different control plane components. If you do not use Gardener, it may be still a worthwhile read.
+Developing highly available workload that can tolerate a zone outage is no trivial task. You can find more information on how to achieve this goal [here](https://github.com/gardener/gardener/blob/master/docs/usage/high-availability/shoot_high_availability_best_practices.md). While many recommendations are general enough, the examples are specific in how to achieve this in a Gardener-managed cluster and where/how to tweak the different control plane components. If you do not use Gardener, it may be still a worthwhile read.
 
 Thank you for your interest in Gardener chaos engineering and making your workload more resilient.