Migration from v1.22

When upgrading to Kublr v1.23.2, it is recommended to first upgrade to v1.22.3. “Skip” upgrades (from 1.20, 1.19 etc, skipping 1.21) are not supported and may not work as expected.

It is recommended to use at least Kublr v1.23.2 as it includes a number of critical and important patches and fixes.

It is recomended to backup KCP data using instructions on the solution portal before upgrading:

Other useful links:

Important notes on migrating vSphere clusters to Kublr v1.23.0

For Kublr kubernetes clusters deployed in vSphere:

  • You will need to unmount CD/DVD drive 1 from each virtual machines directly from vCenter console

  • After migration it is recomended to modify the cluster specification for the master nodes location section from masterDataDisk proprty to dataDisks array. masterDataDisk is deprecated and may be removed in the future.

        - vSphere:
          - dataStoreName: ETCD-DISK-DATA-STORE-NAME
            sizeGb: ETCD-DISK-SIZE

Kublr feature Ingress

Ingress controller is upgraded to NGINX Ingress controller v1.3.0 (helm chart v4.2.3).

If Ingress objects are used in managed clusters (running Kubernetes older than v1.22), and the cluster upgrade to Kubernetess v1.22 is planned, refer to the following documentation and Kublr release notes:

CertManager is upgraded to v1.5 (helm chart v1.5.3).

To keep compatibility with older Kubernetes versions (down to 1.16), cert-manager 1.5 is now compatible with both Ingress v1 and v1beta1. Cert-manager will default to using v1 Ingress, and fall back to v1beta1 when v1 is not available.

Please refer to Cert Manager release notes for more information:

Simultaneous Update of Kublr Control Plane

When upgrading to Kublr Control Plane 1.23.2 use the following components versions.

Features versions for Kublr v1.23.2 are:

  • kublrOperator: 1.23.2
  • ControlPlane: 1.23.2

Features versions for Kublr v1.23.1 are:

  • kublrOperator: 1.23.1
  • ControlPlane: 1.23.1