diff --git a/docs/admin/kof/kof-install.md b/docs/admin/kof/kof-install.md index d05f7ba0b..5e5a111ca 100644 --- a/docs/admin/kof/kof-install.md +++ b/docs/admin/kof/kof-install.md @@ -417,6 +417,7 @@ apply this example for AWS, or use it as a reference: namespace: kcm-system labels: k0rdent.mirantis.com/kof-cluster-role: regional + k0rdent.mirantis.com/kof-version: {{{ extra.docsVersionInfo.kofVersions.kofDotVersion }}} spec: template: $TEMPLATE credential: aws-cluster-identity-cred @@ -455,6 +456,7 @@ apply this example for AWS, or use it as a reference: namespace: kcm-system labels: k0rdent.mirantis.com/kof-cluster-role: regional + k0rdent.mirantis.com/kof-version: {{{ extra.docsVersionInfo.kofVersions.kofDotVersion }}} spec: template: $TEMPLATE credential: azure-cluster-identity-cred @@ -494,6 +496,7 @@ apply this example for AWS, or use it as a reference: namespace: kcm-system labels: k0rdent.mirantis.com/kof-cluster-role: regional + k0rdent.mirantis.com/kof-version: {{{ extra.docsVersionInfo.kofVersions.kofDotVersion }}} spec: template: $TEMPLATE credential: openstack-cluster-identity-cred @@ -523,6 +526,9 @@ apply this example for AWS, or use it as a reference: EOF ``` + * For on-demand upgrade: set `k0rdent.mirantis.com/kof-version` label here. + * For auto-upgrade: set `autoUpgrade: true` in `kof-values.yaml`. + 4. If you've applied the [DNS auto-config](#dns-auto-config) section, add it to the `.metadata.labels` in the `regional-cluster.yaml` file. Examples by cloud provider: @@ -750,6 +756,7 @@ apply this example for AWS, or use it as a reference: namespace: kcm-system labels: k0rdent.mirantis.com/kof-cluster-role: child + k0rdent.mirantis.com/kof-version: {{{ extra.docsVersionInfo.kofVersions.kofDotVersion }}} spec: template: $TEMPLATE credential: aws-cluster-identity-cred @@ -782,6 +789,7 @@ apply this example for AWS, or use it as a reference: namespace: kcm-system labels: k0rdent.mirantis.com/kof-cluster-role: child + k0rdent.mirantis.com/kof-version: {{{ extra.docsVersionInfo.kofVersions.kofDotVersion }}} spec: template: $TEMPLATE credential: azure-cluster-identity-cred @@ -815,6 +823,7 @@ apply this example for AWS, or use it as a reference: namespace: kcm-system labels: k0rdent.mirantis.com/kof-cluster-role: child + k0rdent.mirantis.com/kof-version: {{{ extra.docsVersionInfo.kofVersions.kofDotVersion }}} spec: template: $TEMPLATE credential: openstack-cluster-identity-cred @@ -838,6 +847,9 @@ apply this example for AWS, or use it as a reference: EOF ``` + * For on-demand upgrade: set `k0rdent.mirantis.com/kof-version` label here. + * For auto-upgrade: set `autoUpgrade: true` in `kof-values.yaml`. + 4. If you've applied the [Istio](#istio) section, update the `child-cluster.yaml` file: ??? note "Istio" diff --git a/includes/kof-install-includes.md b/includes/kof-install-includes.md index 736fe5f91..1f3e015fc 100644 --- a/includes/kof-install-includes.md +++ b/includes/kof-install-includes.md @@ -6,7 +6,8 @@ ```bash - helm upgrade -i --reset-values --wait --create-namespace -n istio-system k0rdent-istio \ + helm upgrade -i --reset-values --wait \ + --create-namespace -n istio-system k0rdent-istio \ {{{ extra.docsVersionInfo.kofVersions.kofOciRegistryBaseIstio }}}/charts/k0rdent-istio \ --version 0.6.0 \ --set cert-manager-service-template.enabled=false \ diff --git a/includes/kof-upgrade-includes.md b/includes/kof-upgrade-includes.md index 39854d915..18babb7d4 100644 --- a/includes/kof-upgrade-includes.md +++ b/includes/kof-upgrade-includes.md @@ -1,6 +1,27 @@ +## Upgrade to v1.11.0 + +### On-demand upgrade by default + +Earlier, upgrade of `kof` umbrella chart in the management cluster +lead to instant upgrade of **all** regional and child clusters at the same time, +which may be not the best strategy. + +For more fine-grained control, starting from KOF 1.11.0 +you can upgrade each regional and child cluster on-demand +by labeling it with a new `k0rdent.mirantis.com/kof-version` like this: + +```bash +kubectl label --overwrite cld -n kcm-system $CLUSTER_NAME \ + k0rdent.mirantis.com/kof-version=1.11.0 +``` + +If you want to keep old behavior, +set `autoUpgrade: true` in your `kof-values.yaml` file +and apply it on upgrade of the management cluster. + ## Upgrade to v1.10.0 > WARNING: