Changed
- In order to facilitate the migration from aws-cni to cilium we need to keep the standard network policies in place so that VPA can communicate with the k8s API while the clusters are being upgraded
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
topologySpreadConstraints
for all 3 VPA components (updater, recommender and admission controller)/metrics
rule in the updater cilium network policy because it can cause delays in the application availability when switching from a different CNI over to CiliumtopologySpreadConstraints
for all 3 VPA components (updater, recommender and admission controller)/metrics
rule in the updater cilium network policy because it can cause delays in the application availability when switching from a different CNI over to Ciliumlogin
works on CAPA and gcp
to use our DNS record for the k8s API when using these providers, rather than the value found in the CAPI CRs.This part of our documentation refers to our vintage product. The content may be not valid anymore for our current product. Please check our new documentation hub for the latest state of our docs.