Installing a cluster on Nutanix

If you do not have an existing SSH key pair on your local machine to use for authentication onto your cluster nodes, create one. For example, on a computer that uses a Linux operating system, run the following command:

$ ssh-keygen -t ed25519 -N '' -f <path>/<file_name> (1)

View the public SSH key:

$ cat <path>/<file_name>.pub

$ cat ~/.ssh/id_ed25519.pub

Add the SSH private key identity to the SSH agent for your local user, if it has not already been added. SSH agent management of the key is required for password-less SSH authentication onto your cluster nodes, or if you want to use the ./openshift-install gather command.

Add your SSH private key to the ssh-agent:

$ ssh-add <path>/<file_name> (1)

Identity added: /home/<you>/<path>/<file_name> (<computer_name>)

Download the installation program from https://github.com/openshift/okd/releases.

Extract the installation program. For example, on a computer that uses a Linux operating system, run the following command:

$ tar -xvf openshift-install-linux.tar.gz

Download your installation pull secret from Red Hat OpenShift Cluster Manager. This pull secret allows you to authenticate with the services that are provided by the included authorities, including Quay.io, which serves the container images for OKD components.

From the Prism Central web console, download the Nutanix root CA certificates.

Extract the compressed file that contains the Nutanix root CA certificates.

Add the files for your operating system to the system trust. For example, on a Fedora operating system, run the following command:

# cp certs/lin/* /etc/pki/ca-trust/source/anchors

Update your system trust. For example, on a Fedora operating system, run the following command:

# update-ca-trust extract

Create the install-config.yaml file.

Optional: Update one or more of the default configuration parameters in the install.config.yaml file to customize the installation.

Back up the install-config.yaml file so that you can use it to install multiple clusters.

Navigate to https://mirror.openshift.com/pub/openshift-v4/clients/oc/latest/ and choose the folder for your operating system and architecture.

Download oc.tar.gz.

Unpack the archive:

$ tar xvf <file>

Place the oc binary in a directory that is on your PATH.

$ echo $PATH

Navigate to https://mirror.openshift.com/pub/openshift-v4/clients/oc/latest/ and choose the folder for your operating system and architecture.

Download oc.zip.

Unzip the archive with a ZIP program.

Move the oc binary to a directory that is on your PATH.

C:\> path

Navigate to https://mirror.openshift.com/pub/openshift-v4/clients/oc/latest/ and choose the folder for your operating system and architecture.

Download oc.tar.gz.

Unpack and unzip the archive.

Move the oc binary to a directory on your PATH.

$ echo $PATH

Create a YAML file that contains the credentials data in the following format:

credentials:
- type: basic_auth (1)
  data:
    prismCentral: (2)
      username: <username_for_prism_central>
      password: <password_for_prism_central>
    prismElements: (3)
    - name: <name_of_prism_element>
      username: <username_for_prism_element>
      password: <password_for_prism_element>

Set a $RELEASE_IMAGE variable with the release image from your installation file by running the following command:

$ RELEASE_IMAGE=$(./openshift-install version | awk '/release image/ {print $3}')

Extract the list of CredentialsRequest custom resources (CRs) from the OKD release image by running the following command:

$ oc adm release extract \
  --from=$RELEASE_IMAGE \
  --credentials-requests \
  --included \(1)
  --install-config=<path_to_directory_with_installation_configuration>/install-config.yaml \(2)
  --to=<path_to_directory_for_credentials_requests> (3)

  apiVersion: cloudcredential.openshift.io/v1
  kind: CredentialsRequest
  metadata:
    annotations:
      include.release.openshift.io/self-managed-high-availability: "true"
    labels:
      controller-tools.k8s.io: "1.0"
    name: openshift-machine-api-nutanix
    namespace: openshift-cloud-credential-operator
  spec:
    providerSpec:
      apiVersion: cloudcredential.openshift.io/v1
      kind: NutanixProviderSpec
    secretRef:
      name: nutanix-credentials
      namespace: openshift-machine-api

Use the ccoctl tool to process all CredentialsRequest objects by running the following command:

$ ccoctl nutanix create-shared-secrets \
  --credentials-requests-dir=<path_to_credentials_requests_directory> \(1)
  --output-dir=<ccoctl_output_dir> \(2)
  --credentials-source-filepath=<path_to_credentials_file> (3)

Edit the install-config.yaml configuration file so that the credentialsMode parameter is set to Manual.

apiVersion: v1
baseDomain: cluster1.example.com
credentialsMode: Manual (1)
...

Create the installation manifests by running the following command:

$ openshift-install create manifests --dir <installation_directory> (1)

Copy the generated credential files to the target manifests directory by running the following command:

$ cp <ccoctl_output_dir>/manifests/*credentials.yaml ./<installation_directory>/manifests

Navigate to the manifests directory:

$ cd <path_to_installation_directory>/manifests

Create the cloud-conf configmap file with the name openshift-cloud-controller-manager-cloud-config.yaml and add the following information:

apiVersion: v1
kind: configmap
metadata:
  name: cloud-conf
  namespace: openshift-cloud-controller-manager
data:
  cloud.conf: "{
      \"prismCentral\": {
          \"address\": \"<prism_central_FQDN/IP>\", (1)
          \"port\": 9440,
            \"credentialRef\": {
                \"kind\": \"Secret\",
                \"name\": \"nutanix-credentials\",
                \"namespace\": \"openshift-cloud-controller-manager\"
            }
       },
       \"topologyDiscovery\": {
           \"type\": \"Prism\",
           \"topologyCategories\": null
       },
       \"enableCustomLabeling\": true
     }"

Verify that the file cluster-infrastructure-02-config.yml exists and has the following information:

spec:
  cloudConfig:
    key: config
    name: cloud-provider-config