Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Verify that you have prepared your environment as listed in the VMware Nuances section above.

  2. Navigate to the Suite Installer Dashboard.

  3. Click Upgrade in the New Kubernetes Cluster tile to create a new Kubernetes cluster and install the Suite Admin on it.

  4. Click the VMware vSphere tile.

  5. Enter your Suite Admin credentials and click Connect.

    vSphere DetailsDescription

    Suite Admin Endpoint for the Cluster to be Upgraded

    The DNS address or IP address of the vCenter server where you launch the Suite Admin.
    Email Address (Username) of the Suite AdminThe email address of Suite Admin (the Initial Administrator) who setup the Suite Admin.
    Password for the Suite AdminThe password for the Suite Admin (the Initial Administrator) who setup the Suite Admin.
    Tenant ID for the Suite Admin
    The Tenant ID for the Suite Admin (the Initial Administrator) who setup the Suite Admin.
    Is This an Amazon EKS ClusterToggle the switch (default is No). If it is, provide the Access Key and Secret Key details.

    The CloudCenter Suite validates the vSphere credentials to ensure that the cluster is available to this user.

  6. Once the connection is validated, click Next.

    Once Connected, you see the cloud type and other information on the left side off the screen

  7. Enter the information in the Upgrade settings fields.

    Upgrade Settings FieldDescription
    Current Kubernetes VersionThe current version for your Kubernetes setup is pre-populated in this field.
    New Kubernetes Version

    If an upgrade is available, it is listed in this dropdown list. Select the Desired K8s version for the upgrade.

    VM Template

    Different images will be used for the installer and the cluster launched by the installer as visible in the following screenshot.

    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.

    The CCS-version-Base-Image  image included in the installer is selected if you do not override the setting.

    To override the CCS-version-Base-Image image used by the Suite installer, be sure to add the applicable image in the vSphere console and selected the applicable OVA from the dropdown list in this field.

    If you use the OVA installer to launch the cluster in an OpenStack environment, be sure to override this field and select the applicable QCOW2 CS-version-Base-Image.


    If you install the CloudCenter Suite using any image other than CCS-version-Base-Image, the installation will fail.

    IP Allocation Mode

    This switch allows you to select the mode. Currently, only DHCP is supported.

    • DHCP: This strategy allows the IP to be allocated by the DHCP server to the instance on server boot up.

      • Master VIP: The IP address for the Take Me to Suite Admin link – Users can determine the IP address that should have the master primary role for the Take Me to Suite Admin link.


        This should be a unique IP and should not be assigned to any other resource. 

    • Static IP: This strategy allows the customer to provide the IP address. As this IP address may or may not be available to the server (based on the availability), you must perform adequate checks to ensure IP availability before using this strategy.

      • Static IP Pool Start IP: The first IP address of the static IP range. If you need to scale up nodes after setting up the Suite Admin, then you must ensure a wider range.
      • Static IP Pool End IPThe last IP address for the static IP range.
      • Subnet Mask: The netmask corresponding the the specified IP range.
      • DNS Server List: The comma separated list of DNS server IP addresses.
      • Gateway List: The comma separated list of Gateway server IP addresses.
  8. Click Upgrade to upgrade the Kubernetes cluster as well as the master primary and worker nodes once the upgrade is complete. A progress bar with relevant status messages is displayed as visible in the following screenshot.

  9. At this point, you can:

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

    2. Wait for cluster to finish upgrading.

  10. Once successful, you see the success message as visible in the following screenshot.

  11. You have the following options at this point:

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

    2. Click Install or Upgrade Another Cluster to start another installation and go back to the homepage (Installer Dashboard).

    3. Download KubeConfig file to connect to the launched cluster using the kubectl tool.

    4. After the installation is complete, use the following command to SSH into the workers/masters primary servers as cloud-user and use the private SSH key or the public key (provided when you configured the Placement Properties details above).

      Code Block
      #Sample command to SSH into a worker/masterprimary server
      • ssh -I <private key> cloud-user@<Masteruser@<primary server/Workerworker IP>
  12. Be sure to switch off the installer VM. You can reuse this VM for any other purpose, for example, as an Offline Repository.


Terms & Conditions Privacy Statement Cookies Trademarks