Upgrade Managed Clusters
If you have managed clusters, follow these steps to upgrade each cluster similar to the management cluster process order:
Using the kubeconfig of your management cluster, find your cluster name and be sure to copy the information for all of your clusters:
CODE
kubectl get clusters -A
Set your cluster variable:
CODE
export CLUSTER_NAME=<your-managed-cluster-name>
Set your cluster's workspace variable:
CODE
export CLUSTER_WORKSPACE=<your-workspace-namespace>
Then, upgrade the core addons (replacing aws
with whatever infrastructure provider you would be using):
CODE
dkp upgrade addons aws --cluster-name=${CLUSTER_NAME} -n ${CLUSTER_WORKSPACE}
Upgrade Kubernetes Version on a Managed Cluster After you complete the previous steps for all managed clusters and you update your core addons, begin upgrading the Kubernetes version.
You should first complete the upgrade of your Kommander Management Cluster before upgrading any managed clusters.
Use this command to begin upgrading the Kubernetes version:
CODE
dkp update controlplane aws --cluster-name=${CLUSTER_NAME} --kubernetes-version=v1.28.7 -n ${CLUSTER_WORKSPACE}
For EKS
CODE
dkp update controlplane eks --cluster-name=${CLUSTER_NAME} --kubernetes-version=v1.26.12 -n ${CLUSTER_WORKSPACE}
For Azure
CODE
dkp update controlplane azure --cluster-name=${CLUSTER_NAME} --kubernetes-version=v1.28.7 --compute-gallery-id <Azure Compute Gallery built by KIB for Kubernetes v1.28.7> -n ${CLUSTER_WORKSPACE}
For vSphere
CODE
dkp update controlplane vsphere --cluster-name=${CLUSTER_NAME} --kubernetes-version=v1.28.7 --vm-template <vSphere template built by KIB for Kubernetes v1.28.7> -n ${CLUSTER_WORKSPACE}
For VCD
CODE
dkp update controlplane vcd --cluster-name=${CLUSTER_NAME} --kubernetes-version=v1.28.7 --catalog <tenant catalog image> --vapp-template <vApp template built in vSphere KIB for Kubernetes v1.28.7> -n ${CLUSTER_WORKSPACE}
For GCP
CODE
dkp update controlplane gcp --cluster-name=${CLUSTER_NAME} --kubernetes-version=v1.28.7 --image=projects/${GCP_PROJECT}/global/images/<GCP image built by KIB for Kubernetes v1.28.7> -n ${CLUSTER_WORKSPACE}
For Pre-provisioned
CODE
dkp update controlplane preprovisioned --cluster-name=${CLUSTER_NAME} --kubernetes-version=v1.28.7 -n ${CLUSTER_WORKSPACE}
Get a list of all node pools available in your cluster by running the following command:
CODE
dkp get nodepools -c ${CLUSTER_NAME} -n ${CLUSTER_WORKSPACE}
export NODEPOOL_NAME=<my-nodepool>
Use this command to upgrade the node pools:
CODE
dkp update nodepool aws ${NODEPOOL_NAME} --cluster-name=${CLUSTER_NAME} --kubernetes-version=v1.28.7 -n ${CLUSTER_WORKSPACE}
For EKS
CODE
dkp update nodepool eks ${NODEPOOL_NAME} --cluster-name=${CLUSTER_NAME} --kubernetes-version=v1.26.12 -n ${CLUSTER_WORKSPACE}
For Azure
CODE
dkp update nodepool azure ${NODEPOOL_NAME} --cluster-name=${CLUSTER_NAME} --kubernetes-version=v1.28.7 --compute-gallery-id <Azure Compute Gallery built by KIB for Kubernetes v1.28.7> -n ${CLUSTER_WORKSPACE}
For vSphere
CODE
dkp update nodepool vsphere ${NODEPOOL_NAME} --cluster-name=${CLUSTER_NAME} --kubernetes-version=v1.28.7 --vm-template <vSphere template built by KIB for Kubernetes v1.28.7> -n ${CLUSTER_WORKSPACE}
For VCD
CODE
dkp update nodepool vcd ${NODEPOOL_NAME} --cluster-name=${CLUSTER_NAME} --kubernetes-version=v1.28.7 --catalog <tenant catalog image> --vapp-template <vApp template built in vSphere KIB for Kubernetes v1.28.7> -n ${CLUSTER_WORKSPACE}
For GCP
CODE
dkp update nodepool gcp ${NODEPOOL_NAME} --cluster-name=${CLUSTER_NAME} --kubernetes-version=v1.28.7 --image=projects/${GCP_PROJECT}/global/images/<GCP image built by KIB for Kubernetes v1.28.7> -n ${CLUSTER_WORKSPACE}
For Pre-provisioned
CODE
dkp update nodepool preprovisioned ${NODEPOOL_NAME} --cluster-name=${CLUSTER_NAME} --kubernetes-version=v1.28.7 -n ${CLUSTER_WORKSPACE}
Upgrade Attached Cluster Since any attached clusters you have are managed by their corresponding cloud provider, none of the components would be upgraded using the DKP process. The tool used to create the cluster is used to upgrade it. Ensure that it has the Kubernetes version that is compatible with the versions we support.