Upgrading to k0rdent 0.2.0#
In k0rdent 0.2.0, the k0smotron
management component has been renamed to
cluster-api-provider-k0sproject-k0smotron
. To safely upgrade from 0.1.0
to 0.2.0
, follow the upgrade guide
and perform the additional manual steps outlined below:
-
Follow the upgrading guide and create a new
Release
object (steps 1-2). -
Verify the new
Release
statusWait for the new
Release
to havestatus.ready: true
:kubectl wait --for=jsonpath='{.status.ready}=true' release/kcm-0-2-0
-
Manually delete the
k0smotron
providers (replacekcm-system
with your system namespace):kubectl -n kcm-system delete infrastructureproviders.operator.cluster.x-k8s.io k0sproject-k0smotron kubectl -n kcm-system delete controlplaneproviders.operator.cluster.x-k8s.io k0sproject-k0smotron kubectl -n kcm-system delete bootstrapproviders.operator.cluster.x-k8s.io k0sproject-k0smotron
-
Instead of the step 3 from Upgrading guide you need to edit the
Management
object. Run:kubectl edit managements.k0rdent.mirantis.com kcm
And do the following:
- Set
spec.release
tokcm-0-2-0
- In
spec.providers
rename thek0smotron
provider tocluster-api-provider-k0sproject-k0smotron
:
providers: - name: cluster-api-provider-k0sproject-k0smotron
The full example of the new Management spec:
apiVersion: k0rdent.mirantis.com/v1alpha1 kind: Management metadata: labels: k0rdent.mirantis.com/component: kcm name: kcm spec: core: capi: {} kcm: {} providers: - name: cluster-api-provider-k0sproject-k0smotron - name: projectsveltos - name: cluster-api-provider-aws - name: cluster-api-provider-azure - name: cluster-api-provider-docker - name: cluster-api-provider-gcp - name: cluster-api-provider-openstack - name: cluster-api-provider-vsphere release: kcm-0-2-0
- Set
-
Follow the Upgrading guide and verify the upgrade (step 4).