Install the CloudCenter Suite on an Existing Kubernetes Cluster

Overview

Once you access the Suite Installer Dashboard (see Prepare Infrastructure), you can choose to install the Suite Admin on an existing cluster

Restrictions

Before proceeding with section, adhere to the following restrictions:

  • AWS: The CloudCenter Suite does not currently support a Suite Admin installation on an existing AWS cluster.

  • Permission: Admin-level permissions for the cluster are mandatory for a user to install the Suite Admin in an existing cluster.

Prerequisites

Verify that the cluster adheres to the following requirements:

  • Kubernetes Version: The existing Kubernetes cluster must be of Version v1.14.x or and later.

  • Kubernetes Add Ons: Install Cert-manager version v0.7.0 (required) using the following command (refer to https://cert-manager.readthedocs.io/en/latest/ for details):

    kubectl apply -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.5/contrib/manifests/cert-manager/with-rbac.yaml


  • Instance Type: The instance type for GKE is should be n1-standard-8 or higher. Verify that it is large enough to accommodate the installation of Suite Admin and other CloudCenter Suite modules.

  • Basic Authentication: When creating the GKE cluster, go to Security and check the box to Enable Basic Authentication.

  • Storage Class: The default storageClass must be configured.

  • Kubeconfig: The kubeconfig user must have cluster-admin permission in the kubeconfig namespace. 

    • If the cluster does not support Load Balancer. 

    • GCP: You must remove auth provider and use the admin user password.

  • RBAC - Must be enabled.

  • Pod Priority: Define the PriorityClass for suite-high/suite-medium/suite-low. 

    • Refer to https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/ for details.

    • The commands to define PriorityClass are listed in the following code block.

      # create pod priority class: suite-high/suite-medium/suite-low
      
      ##################################### begin create pod priority
      
      cat <<EOF | kubectl apply -f -
      
      apiVersion: scheduling.k8s.io/v1beta1
      
      kind: PriorityClass
      
      metadata:
      
        name: suite-high
      
      value: 1000000
      
      globalDefault: false
      
      description: "High priority"
      
      ---
      
      apiVersion: scheduling.k8s.io/v1beta1
      
      kind: PriorityClass
      
      metadata:
      
        name: suite-medium
      
      value: 10000
      
      globalDefault: false
      
      description: "Medium priority"
      
      ---
      
      apiVersion: scheduling.k8s.io/v1beta1
      
      kind: PriorityClass
      
      metadata:
      
        name: suite-low
      
      value: 100
      
      globalDefault: false
      
      description: "Low priority"
      
      EOF
      
      ##################################### end create pod priority

Procedure

To install the CloudCenter Suite on an existing cluster, perform the following procedure. 

  1. Navigate to the Suite Installer Dashboard.

  2. Click Existing Cluster to get started as displayed in the following screenshot.

  3. Verify that you have met the items identified in the Prerequisites section. The following screenshot displays these items as well.

  4. Identify if you cluster supports load balancer as the service type – accordingly, turn this toggle 

    1. YES – Toggle ON if supported (public clouds generally support load balancers)

    2. NO – Toggle OFF if not supported (private clouds generally do not support load balancers)

  5. Upload the Kubeconfig file.

    Click Install. The installation progress is visible on screen. Once successful, you see the following message .

    CloudCenter Suite installation successful!


  6. 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 Another Cluster to start another installation on the same cluster.


You have now installed the Suite Admin on an existing cluster

  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks