Upgrading Mirantis k0rdent Enterprise#
Note
If upgrading from versions of Mirantis k0rdent Enterprise
prior to v1.0.0, upgrade to v1.0.0 first to facilitate the change
from alpha to beta APIs.
Upgrading Mirantis k0rdent Enterprise involves making upgrades to the
Management object. To do that, you must have the Global Admin role. (For
detailed information about Mirantis k0rdent Enterprise RBAC roles and
permissions, refer to the RBAC documentation.) Follow
these steps to upgrade Mirantis k0rdent Enterprise:
-
Create a new
ReleaseobjectStart by creating a
Releaseobject in the management cluster that points to the desired version. You can getReleaseobject for the current version from the following URL:https://get.mirantis.com/k0rdent-enterprise/1.1.0/release.yamlOnce you've chosen a release, you can go ahead and create the release object by referencing the YAML file online, as in:
kubectl create -f https://get.mirantis.com/k0rdent-enterprise/1.1.0/release.yamlrelease.k0rdent.mirantis.com/k0rdent-enterprise-1-1-0 created -
List Available
ReleasesOnce you've created the new
Releaseyou need to update theManagementobject to use it. Start by viewing all availableReleases:kubectl get releasesNAME AGE kcm-0-0-6 71m kcm-0-0-7 65m kcm-0-1-0 6d9h k0rdent-enterprise-1-1-0 12m -
Patch the
Managementobject with the newReleaseUpdate the
spec.releasefield in theManagementobject to point to the new release. Replace<release-name>with the name of your desired release:RELEASE_NAME=k0rdent-enterprise-1-1-0 kubectl patch managements.k0rdent.mirantis.com kcm --patch "{\"spec\":{\"release\":\"${RELEASE_NAME}\"}}" --type=merge -
Verify the Upgrade
Although the change will be made immediately, it will take some time for Mirantis k0rdent Enterprise to update the components it should be using. Monitor the readiness of the
Managementobject to ensure the upgrade was successful. For example:kubectl get managements.k0rdent.mirantis.com kcmNAME READY RELEASE AGE kcm True k0rdent-enterprise-1-1-0 4m34s