From b56390ab99507a7d46f35354d80ea8e496912107 Mon Sep 17 00:00:00 2001
From: Karl Cardenas <karl@spectrocloud.com>
Date: Tue, 6 Feb 2024 14:11:00 -0700
Subject: [PATCH] docs: added OpenStack steps

---
 .../clusters/data-center/openstack.md         |   6 +-
 .../clusters/pcg/deploy-pcg/maas.md           |  41 +++--
 .../clusters/pcg/deploy-pcg/openstack.md      | 164 +++++++++++++++++-
 .../clusters/pcg/deploy-pcg/vmware.md         |  25 ++-
 4 files changed, 200 insertions(+), 36 deletions(-)

diff --git a/docs/docs-content/clusters/data-center/openstack.md b/docs/docs-content/clusters/data-center/openstack.md
index 0da26e7bc0..e48a3aea58 100644
--- a/docs/docs-content/clusters/data-center/openstack.md
+++ b/docs/docs-content/clusters/data-center/openstack.md
@@ -563,7 +563,7 @@ following steps to resize a single-node PCG cluster to a three-node PCG cluster.
 4. The gateway upgrade begins shortly after the update. Two new nodes are created, and the gateway is upgraded to a
    3-node cluster.
 
-# Creating an OpenStack Cloud Account
+## Creating an OpenStack Cloud Account
 
 A default cloud account is automatically created when the private cloud gateway is configured. This cloud account can be
 used to create tenant clusters. Additional cloud accounts may be created if desired within the same gateway.
@@ -584,7 +584,7 @@ used to create tenant clusters. Additional cloud accounts may be created if desi
    | **Default Domain**        | Default OpenStack domain             |
    | **Default Project**       | Default OpenStack project            |
 
-# Deploying an OpenStack Cluster
+## Deploying an OpenStack Cluster
 
 <Video
   title="openstack-cluster-creation"
@@ -684,7 +684,7 @@ being provisioned, the 'Abort' action is available to stop provisioning and dele
 
 :::
 
-# Force Delete a Cluster
+## Force Delete a Cluster
 
 A cluster stuck in the **Deletion** state can be force deleted by the user through the User Interface. The user can go
 for a force deletion of the cluster, only if it is stuck in a deletion state for a minimum of **15 minutes**. Palette
diff --git a/docs/docs-content/clusters/pcg/deploy-pcg/maas.md b/docs/docs-content/clusters/pcg/deploy-pcg/maas.md
index d34a42cee8..18afda2d88 100644
--- a/docs/docs-content/clusters/pcg/deploy-pcg/maas.md
+++ b/docs/docs-content/clusters/pcg/deploy-pcg/maas.md
@@ -36,8 +36,8 @@ The following system requirements must be met to install a PCG in MAAS:
   - 1 IP address for the Kubernetes control-plane
   - DNS can resolve the domain `api.spectrocloud.com`.
 
-- A Linux environment with a Docker daemon installed and a connection to Palette and the MAAS endpoint. The Palette CLI
-  installation must be invoked on an up-to-date Linux system with an x86-64 architecture.
+- An x86 Linux environment with a Docker daemon installed and a connection to Palette and the MAAS endpoint. The Palette
+  CLI installation must be invoked on an up-to-date Linux system with an x86-64 architecture.
 
 - PCG IP address requirements:
 
@@ -130,14 +130,14 @@ is not required for the DNS records to be accessible from the internet.
     palette pcg install
     ```
 
-    | **Parameter**                                        | **Description**                                                                                                                                                                                                                                |
-    | :--------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-    | **Management Plane Type**                            | Select Palette or VerteX.                                                                                                                                                                                                                      |
-    | **Enable Ubuntu Pro (required for production)**      | Choose `y` if you want to to use Ubuntu Pro, otherwise press `n`. If you select `y`, you will be be asked to provide an Ubuntu Pro token.                                                                                                      |
-    | **Select an image registry type**                    | Choose Default to pull images from public iamge registries. This requires an internet connection. Airgap customers, select `Custom` so you can point to our airgap support VM or a custom internal registry that contains the required images. |
-    | **Cloud Type**                                       | Select MAAS.                                                                                                                                                                                                                                   |
-    | **Private Cloud Gateway Name**                       | Enter a custom name for the PCG. Example: `maas-pcg-1`.                                                                                                                                                                                        |
-    | **Share PCG Cloud Account across platform Projects** | Enter `y` if you want the Cloud Account associated with the PCG to be available from all projects within your organization. Enter `n` if you want the Cloud Account to only be available at the tenant admin scope.                            |
+    | **Parameter**                                        | **Description**                                                                                                                                                                                                                                  |
+    | :--------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+    | **Management Plane Type**                            | Select Palette or VerteX.                                                                                                                                                                                                                        |
+    | **Enable Ubuntu Pro (required for production)**      | Choose `y` if you want to to use Ubuntu Pro, otherwise press `n`. If you select `y`, you will be be asked to provide an Ubuntu Pro token.                                                                                                        |
+    | **Select an image registry type**                    | Choose `Default` to pull images from public image registries. This requires an internet connection. Airgap customers, select `Custom` so you can point to our airgap support VM or a custom internal registry that contains the required images. |
+    | **Cloud Type**                                       | Select MAAS.                                                                                                                                                                                                                                     |
+    | **Private Cloud Gateway Name**                       | Enter a custom name for the PCG. Example: `maas-pcg-1`.                                                                                                                                                                                          |
+    | **Share PCG Cloud Account across platform Projects** | Enter `y` if you want the Cloud Account associated with the PCG to be available from all projects within your organization. Enter `n` if you want the Cloud Account to only be available at the tenant admin scope.                              |
 
 4.  Next, provide environment configurations for the cluster. Refer to the following table for information about each
     option.
@@ -151,14 +151,27 @@ is not required for the DNS records to be accessible from the internet.
     | **Pod CIDR**                      | Enter the CIDR pool that will be used to assign IP addresses to pods in the PCG cluster. The pod IP addresses should be unique and not overlap with any machine IPs in the environment.                                                                                                                        |
     | **Service IP Range**              | Enter the IP address range that will be used to assign IP addresses to services in the PCG cluster. The service IP addresses should be unique and not overlap with any machine IPs in the environment.                                                                                                         |
 
-5.  Provide the MAAS API key and the MAAS server URL. Refer to the table below for information about each parameter.
+5.  If you selected `Custom` for the image registry type, you will be prompted to provide the following information.
+
+    | **Parameter**                                            | **Description**                                                                                                                                                                                                                                                    |
+    | -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+    | **Registry Name**                                        | Assign a name to the custom registry.                                                                                                                                                                                                                              |
+    | **Registry Endpoint**                                    | The endpoint or IP address for the custom registry. Example: `https://palette.example.com` or `https://10.10.1.0`.                                                                                                                                                 |
+    | **Registry Base Content Path**                           | The base content path for the custom registry. Example: `spectro-images`.                                                                                                                                                                                          |
+    | **Configure Registry Mirror**                            | Your system default text editor, such as Vi, will open up and allow you customize the default mirror registry settings. Add any additional registry mirrors you want to add. Otherwise, press `Esc` and then `:wq` to save and exit the file.                      |
+    | **Allow Insecure Connection (Bypass x509 Verification)** | Enabling this option bypasses x509 CA verification. Enter `n` if using a custom registry with self-signed SSL certificates. Otherwise, enter `y`. If you enter `y`, you will receive a follow up prompt asking you to provide the file path to the CA certificate. |
+    | **Registry CA certificate Filepath**                     | The CA certificate for the custom registry. This is optional. Provide the file path of the CA certificate on the installer host. Example: `/usr/local/share/ca-certificates/ca.crt`.                                                                               |
+    | **Registry Username**                                    | The username for the custom registry.                                                                                                                                                                                                                              |
+    | **Password**                                             | The password for the custom registry.                                                                                                                                                                                                                              |
+
+6.  Provide the MAAS API key and the MAAS server URL. Refer to the table below for information about each parameter.
 
     | **Parameter**       | **Description**                                                  |
     | :------------------ | ---------------------------------------------------------------- |
     | **MAAS API Key**    | Enter the MAAS API key.                                          |
     | **MAAS Server URL** | Enter the MAAS server URL. Example: `http://10.1.1.1:5240/MAAS`. |
 
-6.  Configure the PCG Cluster. The values provided will determine what machines should be selected in MAAS for
+7.  Configure the PCG Cluster. The values provided will determine what machines should be selected in MAAS for
     deployment as a PCG. Refer to the table below for information about each parameter.
 
     | **Parameter**                             | **Description**                                                                                       |
@@ -177,7 +190,7 @@ is not required for the DNS records to be accessible from the internet.
 
     :::
 
-7.  A new PCG configuration file is generated and its location is displayed on the console. You will receive an output
+8.  A new PCG configuration file is generated and its location is displayed on the console. You will receive an output
     similar to the following.
 
     ```bash hideClipboard
@@ -205,7 +218,7 @@ is not required for the DNS records to be accessible from the internet.
 
     :::
 
-## Validation
+## Validate
 
 Once installed, the PCG registers itself with Palette. To verify the PCG is registered, use the following steps.
 
diff --git a/docs/docs-content/clusters/pcg/deploy-pcg/openstack.md b/docs/docs-content/clusters/pcg/deploy-pcg/openstack.md
index fc7e670e27..5c798e73c3 100644
--- a/docs/docs-content/clusters/pcg/deploy-pcg/openstack.md
+++ b/docs/docs-content/clusters/pcg/deploy-pcg/openstack.md
@@ -36,11 +36,8 @@ The following system requirements must be met to install a PCG in OpenStack:
   - 1 IP address for the Kubernetes control-plane
   - DNS can resolve the domain `api.spectrocloud.com`.
 
-- A Linux environment with a Docker daemon installed and a connection to Palette and the MAAS endpoint. The Palette CLI
-  installation must be invoked on an up-to-date Linux system with an x86-64 architecture.
-
-- One additional Kubernetes control plane IP address for rolling upgrades.
-- A Linux x86-64 host with the Docker daemon installed.
+- An x86 Linux environment with a Docker daemon installed and a connection to Palette and the Openstack endpoint. The
+  Palette CLI installation must be invoked on an up-to-date Linux system with an x86-64 architecture
 
 - An Open Stack SSH Key Pair. Refer to the
   [Configure access and security for instances](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html)
@@ -318,3 +315,160 @@ The following permissions are required to deploy a PCG to OpenStack and for Pale
 </Tabs>
 
 ## Deploy PCG
+
+1.  In an x86 Linux host with the Palette CLI installed, open up a terminal session.
+
+2.  Issue the following command to authenticate with Palette. When prompted, enter the required information. Refer to
+    the table below for information about each parameter.
+
+    ```shell
+    palette login
+    ```
+
+    | **Parameter**                  | **Description**                                                                                                                                                                                                                                                   |
+    | :----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+    | **Spectro Cloud Console**      | Enter the Palette endpoint URL. When using the Palette SaaS service, enter `https://console.spectrocloud.com`. When using a self-hosted instance of Palette, enter the URL for that instance.                                                                     |
+    | **Allow Insecure Connection**  | Enabling this option bypasses x509 server Certificate Authority (CA) verification. Enter `y` if you are using a self-hosted Palette, or VerteX instance with self-signed TLS certificates and need to provide the file path to instance CA. Otherwise, enter `n`. |
+    | **Spectro Cloud API Key**      | Enter your Palette API Key. Refer to the [Create API Key](../../../user-management/authentication/api-key/create-api-key.md) for guidance on creating an API key.                                                                                                 |
+    | **Spectro Cloud Organization** | Select your Palette Organization name.                                                                                                                                                                                                                            |
+    | **Spectro Cloud Project**      | Select the project name you want to register the VMware vSphere account in.                                                                                                                                                                                       |
+    | **Acknowledge**                | Accept the login banner message. Login banner messages are only displayed if the tenant admin enabled a login banner.                                                                                                                                             |
+
+    :::info
+
+    The `CloudAccount.apiKey` and `Mgmt.apiKey` values in the **pcg.yaml** are encrypted and cannot be manually updated.
+    To change these values, use the `palette pcg install --update-passwords` command. Refer to the
+    [PCG command](../../../palette-cli/commands/pcg.md#update-passwords) reference page for more information.
+
+    :::
+
+3.  Once you have authenticated successfully, start the PCG installer by issuing the following command. Refer to the
+    table below for information about each parameter.
+
+    ```bash
+    palette pcg install
+    ```
+
+    | **Parameter**                                        | **Description**                                                                                                                                                                                                                                  |
+    | :--------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+    | **Management Plane Type**                            | Select Palette or VerteX.                                                                                                                                                                                                                        |
+    | **Enable Ubuntu Pro (required for production)**      | Choose `y` if you want to to use Ubuntu Pro, otherwise press `n`. If you select `y`, you will be be asked to provide an Ubuntu Pro token.                                                                                                        |
+    | **Select an image registry type**                    | Choose `Default` to pull images from public image registries. This requires an internet connection. Airgap customers, select `Custom` so you can point to our airgap support VM or a custom internal registry that contains the required images. |
+    | **Share PCG Cloud Account across platform Projects** | Enter `y` if you want the Cloud Account associated with the PCG to be available from all projects within your organization. Enter `n` if you want the Cloud Account to only be available at the tenant admin scope.                              |
+    | **Cloud Type**                                       | Select OpenStack.                                                                                                                                                                                                                                |
+    | **Private Cloud Gateway Name**                       | Enter a custom name for the PCG. Example: `openstack-pcg-1`.                                                                                                                                                                                     |
+    | **Share PCG Cloud Account across platform Projects** | Enter `y` if you want the Cloud account associated with the PCG to be available from all projects within your organization. Enter `n` if you want the Cloud Account to only be available at the tenant admin scope.                              |
+
+4.  Next, provide environment configurations for the cluster. Refer to the following table for information about each
+    option.
+
+    | **Parameter**                     | **Description**                                                                                                                                                                                                                                                                                                |
+    | :-------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+    | **HTTPS Proxy**                   | Leave this blank unless you are using an HTTPS Proxy. This setting will be propagated to all PCG nodes and all of its cluster nodes. Example: `https://USERNAME:PASSWORD@PROXYIP:PROXYPORT`.                                                                                                                   |
+    | **HTTP Proxy**                    | Leave this blank unless you are using an HTTP Proxy. This setting will be propagated to all PCG nodes and all of its cluster nodes. Example: `http://USERNAME:PASSWORD@PROXYIP:PROXYPORT`.                                                                                                                     |
+    | **No Proxy**                      | You will be prompted to provide a list of local network CIDR addresses, hostnames, and domain names that should be excluded from being a proxy. This setting will be propagated to all the nodes to bypass the proxy server. Example if you have a self-hosted environment: `my.company.com,10.10.0.0/16`.     |
+    | **Proxy CA Certificate Filepath** | The default is blank. You can provide the file path of a CA certificate on the installer host. If provided, this CA certificate will be copied to each host in the PCG cluster during deployment. The provided path will be used on the PCG cluster hosts. Example: `/usr/local/share/ca-certificates/ca.crt`. |
+    | **Pod CIDR**                      | Enter the CIDR pool that will be used to assign IP addresses to pods in the PCG cluster. The pod IP addresses should be unique and not overlap with any machine IPs in the environment.                                                                                                                        |
+    | **Service IP Range**              | Enter the IP address range that will be used to assign IP addresses to services in the PCG cluster. The service IP addresses should be unique and not overlap with any machine IPs in the environment.                                                                                                         |
+
+5.  If you selected `Custom` for the image registry type, you will be prompted to provide the following information.
+
+    | **Parameter**                                            | **Description**                                                                                                                                                                                                                                                    |
+    | -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+    | **Registry Name**                                        | Assign a name to the custom registry.                                                                                                                                                                                                                              |
+    | **Registry Endpoint**                                    | The endpoint or IP address for the custom registry. Example: `https://palette.example.com` or `https://10.10.1.0`.                                                                                                                                                 |
+    | **Registry Base Content Path**                           | The base content path for the custom registry. Example: `spectro-images`.                                                                                                                                                                                          |
+    | **Configure Registry Mirror**                            | Your system default text editor, such as Vi, will open up and allow you customize the default mirror registry settings. Add any additional registry mirrors you want to add. Otherwise, press `Esc` and then `:wq` to save and exit the file.                      |
+    | **Allow Insecure Connection (Bypass x509 Verification)** | Enabling this option bypasses x509 CA verification. Enter `n` if using a custom registry with self-signed SSL certificates. Otherwise, enter `y`. If you enter `y`, you will receive a follow up prompt asking you to provide the file path to the CA certificate. |
+    | **Registry CA certificate Filepath**                     | The CA certificate for the custom registry. This is optional. Provide the file path of the CA certificate on the installer host. Example: `/usr/local/share/ca-certificates/ca.crt`.                                                                               |
+    | **Registry Username**                                    | The username for the custom registry.                                                                                                                                                                                                                              |
+    | **Password**                                             | The password for the custom registry.                                                                                                                                                                                                                              |
+
+6.  Next, provide the OpenStack environment configurations. Refer to the following table for information about each
+    option.
+
+    | **Parameter**                   | **Description**                                                                                                                                                                            |
+    | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+    | **OpenStack Identity Endpoint** | OpenStack Identity endpoint. Domain or IP address. Example: `https://openstack.mycompany.com/identity`.                                                                                    |
+    | **OpenStack Account Username**  | OpenStack account username.                                                                                                                                                                |
+    | **OpenStack Account Password**  | OpenStack account password.                                                                                                                                                                |
+    | **Allow Insecure Connection**   | Enabling this option bypasses x509 verification. Enter `y` if you are using an OpenStack instance with self-signed TLS certificates. Otherwise, enter `n`.                                 |
+    | **CA certificate Filepath**     | The CA certificate for the OpenStack environment. This is optional. Provide the file path of the CA certificate on the installer host. Example: `/usr/local/share/ca-certificates/ca.crt`. |
+    | **Default Domain**              | The default domain for the OpenStack environment.                                                                                                                                          |
+    | **Default Region**              | The default region for the OpenStack environment.                                                                                                                                          |
+    | **Default Project**             | The default project for the OpenStack environment.                                                                                                                                         |
+
+    After providing the OpenStack environment configurations and credentials, the Palette CLI will query the OpenStack
+    environment to validate the provided credentials. If the credentials are valid, the installation process will
+    continue. If the credentials are invalid, you will be prompted to re-enter the credentials.
+
+7.  After the OpenStack environment configurations are validated, you will be prompted for additional OpenStack
+    configuration values. Use the following table to learn more about each options.
+
+    | **Parameter**                             | **Description**                                                                                                                                                                                                                                                               |
+    | ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+    | **Domain**                                | Select the domain you want to target for the PCG deployment. Example: `Default`.                                                                                                                                                                                              |
+    | **Region**                                | Select the region for the PCG deployment.                                                                                                                                                                                                                                     |
+    | **Project**                               | Specify the OpenStack project to place the PCG cluster in.                                                                                                                                                                                                                    |
+    | **Placement Type**                        | Placement can be static or dynamic. For static placement, cluster nodes are placed into existing networks. For dynamic placement, a new network is created.                                                                                                                   |
+    | **Network**                               | Select an existing network. This is only required for static placement.                                                                                                                                                                                                       |
+    | **Subnet**                                | Select an existing subnet. This is only required for static placement.                                                                                                                                                                                                        |
+    | **DNS Server(s)**                         | Enter a comma-separated list of DNS server IPs . This is only required for dynamic placement.                                                                                                                                                                                 |
+    | **Node CIDR**                             | Enter a node CIDR. This is only required for dynamic placement. Example: `10.55.0.0/24`.                                                                                                                                                                                      |
+    | **SSH Public Key**                        | Provide the public OpenSSH key for the PCG cluster. Use this key when establishing an SSH connection with the PCG cluster. This prompt will result in the default text editor for the Operating System to open. Vi is the more common text editor used in Linux environments. |
+    | **Patch OS on boot**                      | This parameter indicates whether or not to patch the OS of the PCG hosts on the first boot.                                                                                                                                                                                   |
+    | **Reboot nodes once OS patch is applied** | This parameter indicates whether or not to reboot PCG nodes after OS patches are complete. This only applies if the **Patch OS on boot** parameter is enabled.                                                                                                                |
+    | **AZs**                                   | Select the availability zones for the PCG cluster.                                                                                                                                                                                                                            |
+    | **Flavor**                                | Specify the OpenStack Flavor for the PCG nodes.                                                                                                                                                                                                                               |
+    | **Number of Nodes**                       | Specify the number of nodes for the PCG cluster. We recommend three node clusters for production workloads.                                                                                                                                                                   |
+    | **Node Affinity**                         | Enter `y` to schedule all Palette pods on the control plane node                                                                                                                                                                                                              |
+
+8.  A new PCG configuration file is generated and its location is displayed on the console. You will receive an output
+    similar to the following.
+
+    ```bash hideClipboard
+    ==== PCG config saved ====
+    Location: :/home/demo/.palette/pcg/pcg-20230706150945/pcg.yaml
+    ```
+
+    The Palette CLI will now provision a PCG cluster in your OpenStack environment. You can monitor the progress of the
+    PCG cluster by navigating to Palette and selecting **Tenant Settings** from the left **Main Menu**. Next, click on
+    **Private Cloud Gateways** from the left **Tenant Settings Menu** and select the PCG cluster you just deployed to
+    access its details page. From the details page, select the **Events** tab to view the progress of the PCG cluster
+
+    If you encounter issues during the installation, refer to the [PCG Troubleshooting](../../../troubleshooting/pcg.md)
+    guide for debugging assistance. If you need additional help, reach out to our
+    [Customer Support](https://spectrocloud.atlassian.net/servicedesk/customer/portals) team.
+
+    :::warning
+
+    You cannot modify a deployed PCG cluster. If you need to make changes to the PCG cluster, you must first delete the
+    cluster and redeploy it. We recommend you save your PCG configuration file for future use. Use the `--config-only`
+    flag to save the configuration file without deploying the PCG cluster. Refer to the
+    [Generate a Configuration File](../../../palette-cli/commands/pcg.md#generate-a-configuration-file) section to learn
+    more. For additional assistance, visit our
+    [Customer Support](https://spectrocloud.atlassian.net/servicedesk/customer/portals) portal.
+
+    :::
+
+## Validate
+
+Once installed, the PCG registers itself with Palette. To verify the PCG is registered, use the following steps.
+
+1. Log in to [Palette](https://console.spectrocloud.com) as a tenant admin.
+
+2. Navigate to the left **Main Menu** and select **Tenant Settings**
+
+3. From the **Tenant Settings Menu** click on **Private Cloud Gateways**. Verify your PCG cluster is available from the
+   list of PCG clusters displayed and that its **Status** is healthy.
+
+4. Navigate to left **Tenant Settings Menu** and select **Cloud Accounts**.
+
+5. Verify a new OpenStack cloud account is available from the list of cloud accounts displayed.
+
+## Next Steps
+
+After you have successfully deployed the PCG into your OpenStack environment, you can now deploy Kubernetes clusters in
+your MAAS environment through Palette. Check out the
+[Deploying an OpenStack Cluster](../../data-center/openstack.md#deploying-an-openstack-cluster) guide to learn how to
+deploy a Kubernetes cluster in MAAS that is managed by Palette.
diff --git a/docs/docs-content/clusters/pcg/deploy-pcg/vmware.md b/docs/docs-content/clusters/pcg/deploy-pcg/vmware.md
index 82a8c68439..17e758d7b6 100644
--- a/docs/docs-content/clusters/pcg/deploy-pcg/vmware.md
+++ b/docs/docs-content/clusters/pcg/deploy-pcg/vmware.md
@@ -55,11 +55,8 @@ The following system requirements must be met to install a PCG in VMware vSphere
   Nodes can exhaust the 60 GiB storage with prolonged use. If you initially set up the gateway with one node, you can
   resize it at a later time.
 
-- A Linux environment with a Docker daemon installed and a connection to Palette and the MAAS endpoint. The Palette CLI
-  installation must be invoked on an up-to-date Linux system with an x86-64 architecture.
-
-- One additional Kubernetes control plane IP address for rolling upgrades.
-- A Linux x86-64 host with the Docker daemon installed.
+- An x86 Linux environment with a Docker daemon installed and a connection to Palette and the VMware vSphere endpoint.
+  The Palette CLI installation must be invoked on an up-to-date Linux system with an x86-64 architecture.
 
 Before installing PCG on VMware, review the following system requirements and permissions. The vSphere user account used
 to deploy the PCG must have the required permissions to access the proper roles and objects in vSphere.
@@ -387,14 +384,14 @@ The following requirements apply to tags:
     palette pcg install
     ```
 
-    | **Parameter**                                        | **Description**                                                                                                                                                                                                                                |
-    | :--------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-    | **Management Plane Type**                            | Select Palette or VerteX.                                                                                                                                                                                                                      |
-    | **Enable Ubuntu Pro (required for production)**      | Choose `y` if you want to to use Ubuntu Pro, otherwise press `n`. If you select `y`, you will be be asked to provide an Ubuntu Pro token.                                                                                                      |
-    | **Select an image registry type**                    | Choose Default to pull images from public iamge registries. This requires an internet connection. Airgap customers, select `Custom` so you can point to our airgap support VM or a custom internal registry that contains the required images. |
-    | **Cloud Type**                                       | Choose VMware vSphere.                                                                                                                                                                                                                         |
-    | **Private Cloud Gateway Name**                       | Enter a custom name for the PCG. Example: `vmware-pcg-1`.                                                                                                                                                                                      |
-    | **Share PCG Cloud Account across platform Projects** | Enter `y` if you want the Cloud Account associated with the PCG to be available from all projects within your organization. Enter `n` if you want the Cloud Account to only be available at the tenant admin scope.                            |
+    | **Parameter**                                        | **Description**                                                                                                                                                                                                                                  |
+    | :--------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+    | **Management Plane Type**                            | Select Palette or VerteX.                                                                                                                                                                                                                        |
+    | **Enable Ubuntu Pro (required for production)**      | Choose `y` if you want to to use Ubuntu Pro, otherwise press `n`. If you select `y`, you will be be asked to provide an Ubuntu Pro token.                                                                                                        |
+    | **Select an image registry type**                    | Choose `Default` to pull images from public image registries. This requires an internet connection. Airgap customers, select `Custom` so you can point to our airgap support VM or a custom internal registry that contains the required images. |
+    | **Cloud Type**                                       | Choose VMware vSphere.                                                                                                                                                                                                                           |
+    | **Private Cloud Gateway Name**                       | Enter a custom name for the PCG. Example: `vmware-pcg-1`.                                                                                                                                                                                        |
+    | **Share PCG Cloud Account across platform Projects** | Enter `y` if you want the Cloud Account associated with the PCG to be available from all projects within your organization. Enter `n` if you want the Cloud Account to only be available at the tenant admin scope.                              |
 
 4.  Next, provide environment configurations for the cluster. Refer to the following table for information about each
     option.
@@ -417,9 +414,9 @@ The following requirements apply to tags:
     | **Registry Base Content Path**                           | The base content path for the custom registry. Example: `spectro-images`.                                                                                                                                                                                          |
     | **Configure Registry Mirror**                            | Your system default text editor, such as Vi, will open up and allow you customize the default mirror registry settings. Add any additional registry mirrors you want to add. Otherwise, press `Esc` and then `:wq` to save and exit the file.                      |
     | **Allow Insecure Connection (Bypass x509 Verification)** | Enabling this option bypasses x509 CA verification. Enter `n` if using a custom registry with self-signed SSL certificates. Otherwise, enter `y`. If you enter `y`, you will receive a follow up prompt asking you to provide the file path to the CA certificate. |
+    | **Registry CA certificate Filepath**                     | The CA certificate for the custom registry. This is optional. Provide the file path of the CA certificate on the installer host. Example: `/usr/local/share/ca-certificates/ca.crt`.                                                                               |
     | **Registry Username**                                    | The username for the custom registry.                                                                                                                                                                                                                              |
     | **Password**                                             | The password for the custom registry.                                                                                                                                                                                                                              |
-    | **CA Cert**                                              | The CA certificate for the custom registry. This is optional. Provide the file path of the CA certificate on the installer host. Example: `/usr/local/share/ca-certificates/ca.crt`.                                                                               |
 
 6.  The next set of prompts is for configuring connection details for the vSphere environment. The CLI will use this
     information to establish a network connection to the vSphere environment and query the vSphere API to retrieve