Semi-automatic update of generated content (#1390)

* Update from 'Create or Update Request' action

* Update from 'Create or Update Request' action

Co-authored-by: Create or Update Pull Request Action <[email protected]>

src/content/changes/documentation/docs/v2.2.391.md

@@ -0,0 +1,16 @@
+---
+# Generated by scripts/aggregate-changelogs. WARNING: Manual edits to this files will be overwritten.
+changes_categories:
+- Documentation
+changes_entry:
+  repository: giantswarm/docs
+  url: https://github.com/giantswarm/docs/releases/tag/v2.2.391
+  version: 2.2.391
+  version_tag: v2.2.391
+date: '2022-04-04T13:52:23'
+description: Changelog entry for giantswarm/docs version 2.2.391, published on 04
+  April 2022, 13:52
+title: docs release v2.2.391
+---
+
+

src/content/changes/workload-cluster-releases-aws/releases/aws-v17.0.0.md

@@ -55,6 +55,8 @@ This release provides support for Kubernetes 1.22, has Control Groups v2 enabled
 **Control Groups v1**
 To ensure a smooth transition, in case you need time to modify applications to make them compatible with Control Groups v2, we provide a mechanism that will allow using Control Groups v1 on specific node pools. More details are available in our [documentation](https://docs.giantswarm.io/advanced/forcing-cgroupsv1/).
 
+**Note when upgrading from v16 to v17:** Existing `Vertical Pod Autoscaler` app installations need to be removed from the workload cluster prior to upgrading to v17 because the `Vertical Pod Autscaler` is provided as a default application. The two applications have different names which leads to them fighting each other.
+
 
 ## Change details
 

src/content/changes/workload-cluster-releases-aws/releases/aws-v17.0.1.md

@@ -25,6 +25,8 @@ This release allows one replica of `coredns` to run on the control plane nodes f
 **Control Groups v1**
 To ensure a smooth transition, in case you need time to modify applications to make them compatible with Control Groups v2, we provide a mechanism that will allow using Control Groups v1 on specific node pools. More details are available in our [documentation](https://docs.giantswarm.io/advanced/forcing-cgroupsv1/).
 
+**Note when upgrading from v16 to v17:** Existing `Vertical Pod Autoscaler` app installations need to be removed from the workload cluster prior to upgrading to v17 because the `Vertical Pod Autscaler` is provided as a default application. The two applications have different names which leads to them fighting each other.
+
 ## Change details
 
 

src/content/changes/workload-cluster-releases-aws/releases/aws-v17.0.2.md

@@ -20,6 +20,8 @@ This release downgrades the version of the Flatcar AMI from `3033.2.2` to `3033.
 * [Giant Swarm roadmap issue](https://github.com/giantswarm/roadmap/issues/891)
 * [Upstream bug issue](https://github.com/flatcar-linux/Flatcar/issues/665)
 
+**Note when upgrading from v16 to v17:** Existing `Vertical Pod Autoscaler` app installations need to be removed from the workload cluster prior to upgrading to v17 because the `Vertical Pod Autscaler` is provided as a default application. The two applications have different names which leads to them fighting each other.
+
 ## Change details
 
 ### containerlinux [3033.2.0](https://www.flatcar-linux.org/releases/#release-3033.2.0)

src/content/changes/workload-cluster-releases-aws/releases/aws-v17.1.0.md

@@ -26,6 +26,9 @@ This release introduces IAM roles for service accounts (IRSA) as an alternative
 
 All the AWS prerequisites are available in the [giantswarm-aws-account-prerequisites repository](https://github.com/giantswarm/giantswarm-aws-account-prerequisites).
 
+**Note when upgrading from v16 to v17:** Existing `Vertical Pod Autoscaler` app installations need to be removed from the workload cluster prior to upgrading to v17 because the `Vertical Pod Autscaler` is provided as a default application. The two applications have different names which leads to them fighting each other.
+
+
 ## Change details
 
 

src/content/changes/workload-cluster-releases-aws/releases/aws-v17.2.0.md

@@ -30,6 +30,8 @@ This release improves the performance of `etcd` by using `gp3` volumes with prov
   * 1 openssl CVE;
   * 1 ignition
 
+**Note when upgrading from v16 to v17:** Existing `Vertical Pod Autoscaler` app installations need to be removed from the workload cluster prior to upgrading to v17 because the `Vertical Pod Autscaler` is provided as a default application. The two applications have different names which leads to them fighting each other.
+
 ## Change details