Wiki Cloud Avenue
-
Overview
-
Practical sheets
-
-
-
-
-
-
-
- Backup : Agent-Level B&R via NSS for IAAS offer
- Backup : Create VCOD Backup
- Backup : Netbackup Agent Installation for Linux
- Backup : Netbackup Agent Installation for Windows
- Backup : Overall Design for VCOD Offer
- Backup : User's Guide for VCOD Offer
- NSX-T : Configuring a Distributed Firewall [FR]
- NSX-T : Create a VPN Ipsec
- NSX-T : Creation of T1
- NSX-T : DNAT configuration
- NSX-T : How to configure a Gateway Firewall
- NSX-T : SNAT configuration
- NSX-T: Create and Configure a Geneve Overlay Segment [FR]
- NSX-T: How to configure an IPSEC solution
- vCenter : Clone a VM [FR]
- VCenter : Create a new VM
- VCenter : Create a snapshot of a VM
- VCenter : Reset cloudadmin password
- VCenter : Storage Vmotion on a VM
- VCenter : Upgrade Vmware tools on a VM
- Show all articles (5) Collapse Articles
-
-
Q & A
-
Services
- Backup
- Bare metal server
- Block Storage
- BVPN access
- Certifications [FR]
- Cross Connect [FR]
- Dedicated Cluster
- DRaaS with VCDA
- Dual Site [FR]
- HA Dual-Room
- Internet access
- Kubernetes [FR]
- Licenses
- Loadbalancer As a Service
- Network
- Network Storage
- Object storage
- QoS Appliance
- Security
- Shared colocation switch option (Cross connect)
- Support and Coaching
- Tools [FR]
- VCenter On Demand
- VCenter On Demand
- VM Replication [FR]
- Show all articles (10) Collapse Articles
-
-
- Articles coming soon
-
- Articles coming soon
-
KaaS – upgrade workload cluster
Introduction
The upgrade of a Kubernetes cluster can only be done to the next incremental version, say from K8s 1.20 to K8s 1.21.
The update involves modifying the Cluster API objects created on the management cluster to select the target version of Kubernetes and the VM template to use.
Edit the -config.yml file
Modify the cluster1-config.yml file corresponding to the cluster to be updated and change the following parameters (cluster1 corresponds to your cluster to be updated):
| Paramètre | Où trouver cette valeur ? | Exemple |
|---|---|---|
| VCD_TEMPLATE_NAME | in vCloud Director console though Library menu then vApp templates, get the complete template name to use. | ubuntu-2004-kube-v1.20.8+vmware.1-tkg.1-17589475007677388652 or ubuntu-2004-kube-v1.21.2+vmware.1-tkg.1-7832907791984498322 …. |
| KUBERNETES_VERSION | from the template name extract the version to install. the format id v[number]+vmware.[number] | v1.21.2+vmware.1 |
Please note !
The update is performed automatically by adding new nodes with the new version and then removing the old nodes.
Apply the new configuration :
clusterctl generate cluster cluster1 --config cluster1-config.yaml -f v1.22.9-crs > cluster1.yaml
kubectl apply -f cluster1.yaml
Wait for the update to complete. You can track the deployment of the new nodes using the following command :
# watch kubectl get machinedeployment,kubeadmcontrolplane
NAME PHASE REPLICAS READY UPDATED UNAVAILABLE
machinedeployment.cluster.x-k8s.io/cluster1-md0 Running 2 2 2
NAME INITIALIZED API SERVER AVAILABLE VERSION REPLICAS READY UPDATED UNAVAILABLE
kubeadmcontrolplane.controlplane.cluster.x-k8s.io/cluster1-control-plane true true v1.22.9+vmware.1 1 1 1