Upgrade Approach

Overview

This section provides details on restrictions, prerequisites, and the process to upgrade the Kubernetes cluster. During this upgrade, the software upgrades the cluster and migrates the pods to new worker instances.

If you restart any worker node, be sure to wait for approximately 10 minutes before logging into the CloudCenter Suite – this timeline is determined by the pods taking about 10 minutes to startup. 

Restrictions

Before proceeding with an upgrade, adhere to the following restrictions:

  • Usage: To upgrade the Kubernetes cluster to a new version, you can do so from CloudCenter Suite 5.1.0 and later releases.

    • You cannot use the CloudCenter Suite 5.1 upgrader to upgrade a CloudCenter Suite 5.0 cluster. You can only use the CloudCenter Suite 5.1 upgrader effective CloudCenter Suite 5.1.1 to upgrade to a later release.

    • As an upgrader is not available to upgrade from CloudCenter Suite 5.0 to CloudCenter Suite 5.1, you must use the Backup and Restore procedure to upgrade to a CloudCenter Suite 5.1 cluster.

    • Even if you update the Suite Admin to Suite Admin 5.1, the underlying cluster will not have the capability to be upgraded as it is still using CloudCenter Suite 5.0.

    • Public Clouds:

      • By upgrading the cluster, you upgrade to the applicable Kubernetes version.

    • Private Clouds:

      • By upgrading the cluster, you are performing a rolling upgrade on each base image in the cluster.

      • A rolling upgrade may or may not include a change in the Kubernetes version – it may merely apply an OS patch or address vulnerabilities depending on the image version that you use.

      • The installer includes a default Kubernetes cluster image (called, CCS-version-Base-Image). The VM Template contains a list of tenant images with a CCS-version-Base-Image name format. If you want to upgrade to a version other than the default version provided by the installer, then upload that CCS-version-Base-Image under the root folder, so that it will display in this dropdown list. You can use this option to upgrade the cluster across private clouds.

  • Suite Admin-level Permissions: The Suite Admin-level permissions are mandatory for a user to upgrade the cluster.

  • New Clusters Only: You can upgrade a cluster that is created (from the Suite Installer) using the New cluster option.

    If you created your cluster by clicking the Existing cluster option (using the KubeConfig file), then you cannot upgrade this cluster using the process provided in this section.

Prerequisites

Verify that the cluster adheres to the following requirements:

  • Backup Environment: Back up your environment before initiating the upgrade. See Backup for additional details.

  • Schedule Downtime: Schedule a suitable downtime during off-peak hours to minimize the impact to your users and or customers. Communicate the downtime as the CloudCenter Suite will not be accessible during the upgrade.

  • Verify Kubernetes Version: Verify that the existing Kubernetes cluster is Version v1.11.0 and above.

Process

This is the generic process to upgrade a Kubernetes cluster for a cloud that is supported by the CloudCenter Suite.

  1. Navigate to the Suite Installer Dashboard (see Prepare Infrastructure).

  2. Click Upgrade in the Upgrade Kubernetes Cluster section to specify the credentials for your cluster as displayed in the following screenshot.

  3. Enter the Suite Admin URL (or DNS), username, password, and Tenant ID for the admin account.

  4. Identify if this is An Amazon EKS Cluster by toggling the switch (default is No). If it is, provide the Access Key and Secret Key details.

    See the individual cloud upgrade pages for additional notes and nuances.

  5. Click Connect to validate your credentials.

  6. At this point, you have multiple scenarios:

    • You will be able to click Next and select the desired Kubernetes version from the dropdown list for this upgrade. Proceed to Step 8.

    • If an upgrade is not available for your cluster as displayed in the following screenshot, some possible reasons are:

      • An upgrade is not currently available as the cluster is already at the latest available version of Kubernetes.

      • You may have provided the wrong cluster credentials (in this case, you will not see the Connected status update when you try to connect). If so, enter the right credentials and try again.

  7. Once Connected, you see the cloud type and other information on the left side off the screen as visible in the following screenshot (sample of a GKE environment):

  8. If an upgrade is available, select the Desired K8s version for the upgrade.

  9. Click Upgrade to upgrade the Kubernetes cluster as well as the master and worker nodes once the upgrade is complete. A progress bar with relevant status messages is displayed.

    An upgrade operation can take more than one hour depending on the number of nodes to be upgraded and cloud response time.

  10. At this point, you can:

    1. Download the latest logs to track the upgrade process.

    2. Wait for cluster to finish upgrading.

  11. The installation progress and success is visible on the screen.

    See the individual cloud upgrade pages for which of these options are available and for additional notes and nuances.

  12. You have the following options at this point – depending on your cloud environment:

    1. Click Take Me To Suite Admin to launch and set up the Suite Admin.

    2. Click Install Another Cluster to start another installation on the same cluster.

    3. Download the Kubeconfig file.

    4. Download the SSH private key.

    5. Re-purpose the installer server.

  13. Login to CloudCenter Suite using valid credentials and verify that your information is preserved and that the cluster was upgraded.


  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks