Setting up the AppViewX Cloud Connector using a Packaged Installer

Note: The installation occurs with the privileges of the user who begins the installation.
Note: The steps for installing the AppViewX Cloud Connector via the native OS assume that you have gone through the system requirements across the following categories: hardware, operating system, Docker, and server and network.

If the host machine does not/cannot fulfill the installation prerequisites, you can set up the AppViewX Cloud Connector via the AppViewX SaaS OVA. To know more about the OVA and for instructions on setting up the AppViewX Cloud Connector using the AppViewX SaaS OVA, click here.

Note: If this AppViewX Cloud Connector installation requires configuring a proxy server, click here for instructions.
  1. Configure the native OS for the cloud connector installation.
    Note: Before executing the following instructions, ensure that you have root user permissions.
    1. Create the appviewx user and directory.
      useradd appviewx && mkdir /home/appviewx/ && chown appviewx:appviewx /home/appviewx && chmod 700 /home/appviewx
    2. Uninstall the previous version of Docker.
      • For RHEL, CentOS, and Amazon Linux 2:
        sudo yum remove docker \
          docker-client \
          docker-client-latest \
          docker-common \
          docker-latest \
          docker-latest-logrotate \
          docker-logrotate \
          Docker-engine
        
      • For Ubuntu
        for pkg in docker.io docker-doc docker-compose podman-docker containerd runc; do sudo apt-get remove $pkg; done
    3. Configure the hostname and the nameserver.
      1. Configure the hostname: sudo hostnamectl set-hostname "hostname"
      2. Add the host IP address at the end of the hosts file.
        sudo vi /etc/hosts
        <ip> <hostname>
      3. Replace the default nameserver IP address.
        sudo systemctl stop systemd-resolved.service 
        sudo systemctl disable systemd-resolved.service 
        sudo rm /etc/resolv.conf 
        sudo vi /etc/hosts/ 
        <ip> <hostname>
        
      4. To configure nameserver, add the IP address of the nameserver to beginning of the resolv.conf
        sudo vi /etc/resolv.conf 
        nameserver <nameserver ip>
        
    4. Add Docker repo and install Docker.
      • For RHEL and CentOS
        sudo yum install -y yum-utils && sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo sudo yum install -y docker-ce docker-ce-cli containerd.io 
        sudo systemctl start docker 
        sudo systemctl enable docker 
        sudo systemctl status docker
        
      • For Amazon Linux 2
        sudo yum install -y docker containerd 
        sudo systemctl start docker 
        sudo systemctl enable docker 
        sudo systemctl status docker
        
      • For Ubuntu
        sudo apt-get update 
        sudo apt-get install ca-certificates curl gnupg 
        #Add Docker’s official GPG key for Ubuntu: 
        sudo install -m 0755 -d /etc/apt/keyrings 
        curl -fsSL https://download.docker.com/linux/debian/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg 
        sudo chmod a+r /etc/apt/keyrings/docker.gpg 
        #Use the following command to set up the repository: 
        echo \ 
         "deb [arch="$(dpkg --print-architecture)" signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \  "$(. /etc/os-release && echo "$VERSION_CODENAME")" stable" | \ 
         sudo tee /etc/apt/sources.list.d/docker.list > /dev/null 
        sudo apt-get update
        
        To install Docker for Ubuntu
        sudo apt-get update && sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin sudo systemctl start docker 
        sudo systemctl enable docker 
        sudo systemctl status docker
        
    5. Add the appviewx user in the Docker group.
      sudo groupadd docker 
      sudo usermod -aG docker appviewx
      
    6. Install NTP.
      • For RHEL and CentOS
        sudo yum update -y 
        sudo yum install ntp -y 
        sudo systemctl restart ntpd 
        sudo systemctl enable ntpd 
        ntpq -np
        
      • For Amazon Linux 2
        sudo yum install -y chrony 
        sudo systemctl enable chronyd 
        sudo systemctl start chronyd 
        sudo systemctl status chronyd
        
      • For Ubuntu
        sudo apt update -y 
        sudo apt install ntp -y 
        sudo systemctl restart ntp 
        sudo systemctl enable ntp 
        ntpq -np
        
    7. Install the additional packages required for the AppViewX Cloud Connector to run.
      • For RHEL, CentOS, and Amazon Linux 2
        sudo yum install bind-utils net-tools telnet tcpdump curl -y
      • For Ubuntu
        sudo apt install bind9-utils net-tools telnet tcpdump curl -y
    8. Limit the maximum number of processes that the appviewx user can create.
      sudo vi /etc/security/limit.conf 
      appviewx soft nproc 65536 
      appviewx hard nproc 65536 
      appviewx soft nofile 65536 
      appviewx hard nofile 65536
      
    9. Allow the appviewx user to run sudo root.
      sudo vi /etc/sudoers 
      appviewx ALL=(ALL) ALL
      
    10. To download the required packages, enable the AppViewX repository.
      Important: This step is not applicable for Amazon Linux 2.
    11. If access to the internet is restricted, whitelist the AppViewX repository to perform OS patching.
      • For RHEL and CentOS
        mv /etc/yum.repos.d /etc/yum.repos.d_backup 
        mkdir -p /etc/yum.repos.d 
        mv appviewx.repo /etc/yum.repos.d/appviewx.repo 
        yum clean all 
        yum update
        
      • For Ubuntu
        1. Create a file, appviewx_repo.list, and open it for editing.
          vi /etc/apt/sources.list.d/appviewx_repo.list
        2. Add the following to the appviewx_repo.list file:
          #appviewx apt repo 
          deb https://repos.appviewx.com/repository/ubuntu focal universe 
          deb https://repos.appviewx.com/repository/ubuntu focal-updates universe 
          deb https://repos.appviewx.com/repository/ubuntu focal multiverse 
          deb https://repos.appviewx.com/repository/ubuntu focal-updates multiverse 
          deb https://repos.appviewx.com/repository/ubuntu focal-backports main restricted universe multiverse 
          deb https://repos.appviewx.com/repository/ubuntu focal-security main restricted 
          deb https://repos.appviewx.com/repository/ubuntu focal-security universe 
          deb https://repos.appviewx.com/repository/ubuntu focal-security multiverse
        3. Create a file, auth.conf and open it for editing.
          vi /etc/apt/auth.conf
        4. Add the following to the auth.conf file:
          machine repos.appviewx.com 
          login xxxxx 
          password xxxxx
          
          Note: Contact the AppViewX TAC/CSM team for the login and password.
    12. Create a new directory at the location /home/appviewx and name it cc-installer.
    13. Ensure that the AppViewX Cloud Connector can establish connectivity with the AppViewX SaaS server endpoints over HTTPS (port 443).
    14. To verify connectivity with the AppViewX SaaS servers, use the cURL utility.
      curl -k --max-time 20 --connect-timeout 20 -s -o /dev/null -w "%{http_code}" "<<https://AppViewX SaaS server  
       URL>>/socket.io/?EIO=3&transport=polling&t=O11wka_"
      
      If connectivity has been established successfully, the command will return the HTTP code 200. If the command returns any other code, it indicates that connectivity is not established.
  2. Access the AppViewX user interface.
    In order to set up the AppViewX Cloud Connector instance, you will need to login to the connectivity service’s user interface. The following steps will outline the navigation and steps required to access the AppViewX Cloud Connector's setup interface.

    As an additional layer of security, AppViewX issues client certificates to access the AppViewX GUI. The client certificate will be made available as part of the onboarding process. Upload this client certificate to the browser to start accessing the product.

    1. Enter your account URL (for example, https://tenant-name.appvx.com/appviewx/login) in the address bar of your browser.
      The AppViewX login page is displayed.
    2. Login to AppViewX.
    3. Navigate to the cloud connector's setup interface.
      There are three ways you can access the interface for setting up the AppViewX Cloud Connector:
      • From the product landing page (that you will see as soon as you have logged in)
        • Expand the Connectivity section and click .You will be redirected to the Settings :: Cloud Connector page.
      • From the new navigation menu (displayed by default starting product version 2022.1.0 FP3 onwards):
        1. From the menu in the top-right corner of the page, select Platform.
        2. From the Platform menu, under Connectivity, click Cloud Connector.
          The Settings :: Cloud Connector page is displayed.
      • From the old navigation menu:
        Note: For instructions on switching between the new and the old navigation menus, click here.
        1. From the top right corner of the landing page, click the menu icon.
        2. From the menu displayed, navigate to Settings > Cloud Connector.

          The Settings :: Cloud Connector page is displayed.

  3. On the Setting :: Cloud Connector page, click Add Cloud Connector.
    The Cloud Connector Setup screen is displayed.

    The landing page gives you a quick introduction to the AppViewX Cloud Connector, with a graphical representation of how the infrastructure is deployed and works.

  4. To start with the process of adding the cloud connector, from the bottom-right corner of the screen, click Get Started.
    You will be redirected to the Basic Information page.
  5. On the Basic Information page, configure the basic cloud connector settings.
    1. From Installation Type, select Native OS.
    2. In the Cloud Connector Name (FQDN) field, enter the hostname of the machine on which the AppViewX Cloud Connector will be installed.
      Tip: To retrieve the hostname, from the command line terminal of the host machine, execute the following command: hostname -f
      Note: The hostname entered here is added to the license file that will be generated and downloaded as part of the installer. Therefore, the license file can be used to install the cloud connector only on the machine with the entered hostname and no other.
      Tip: The Setup Cloud Connector section to the right of the Basic Information screen lists hyperlinks to the prerequisites required for setting up the AppViewX Cloud Connector. To read more about what the AppViewX Cloud Connector offers, click Learn More.
    3. Click Next.
  6. [Optional] Execute a prerequisite check script.
    To simplify compliance to the AppViewX Cloud Connector installation prerequisites, you can execute a script to identify and rule out any deviations from the prerequisites.
    Note: This is an optional step. The prerequisite check script is executed automatically at the time of installing the AppViewX Cloud Connector and the results are shown as a part of the installation logs.
    1. On the Basic Information screen, under Setup Cloud Connector, you will see a list of the installation prerequisites.
      From this list, for Executing the Prerequisites Check Script, to download the script, click .
      The pre-requisite-check.sh script file is downloaded.
    2. Securely copy the pre-requisite-check.sh via SCP/SFTP to the host machine where the AppViewX Cloud Connector is to be installed
    3. Convert the downloaded script file into an executable file using the chmod command, as shown below:chmod 755 pre-requisite-check.sh
    4. Execute the .sh prerequisite check script file: ./pre-requisite-check.sh
      If the node does not meet the prerequisites for the AppViewX Cloud Connector installation, the output of the command returns an error code and the corresponding error message, causes, and fixes, if any.

      For example, as seen in the sample output in the image below, the prerequisite check for the memory requirement has failed.

      Note: For resolutions to the prerequisite check failure scenarios, click here.
  7. Click Next.
    You will be navigated to the AssignData Center screen, where, for deploying the AppViewX Cloud Connector, you can either select an existing data center or add a new one.
  8. To use an existing data center, select one from the options displayed on the Assign Data Center screen.
    Tip: Alternatively, you can use the Search… field on this screen to search for an existing data center.
    To add a new data center:
    1. Click Add Data Center.
    2. In the Add Data Center dialog box, enter a name for the new data center.
    3. Click Save.
      The new data center will now be displayed on the Assign Data Center screen along with the other existing data centers.
    4. Select the required data center.
      Tip: The Data Center based routing section to the right of the Assign Data Center screen explains the concept of data center-based routing and how you can achieve high availability. To read more on this, click Learn More from the top-right corner of this screen.
  9. Click Next.
    The Advanced Configuration screen is displayed.
  10. On the Advanced Configuration page, to configure the TLS authentication and proxy server settings for your cloud connector:
    1. Enter/Select the advanced configuration settings for the AppViewX Cloud Connector.
      Note: The Data center field is auto-populated based on your selection on the Assigning a Data Center screen.
      Field Description
      TLS Authentication
      Tip: The section on the right of the screen gives you a brief context of what is TLS Authentication. To read more, click Learn More (next to the TLS Authentication heading).
      • To auto-generate a TLS certificate, select Auto-generate (default selection).

        By default, the certificate is generated using the AppViewX CA.

        Note: The created certificate is available in the certificate inventory. You can:
        • Assign this certificate to a certificate group
        • Configure a certificate expiry alert for this certificate group from the Server Certificate dashboard, using the Certificate Summary Report widget settings
      • To enter details of a custom TLS certificate, select Custom.

        The TLS Certificate Password and Custom TLS Certificate fields are displayed. The instructions for filling these fields are given below.

      TLS Certificate Password*
      Note: This field is displayed only if you have selected to enter details of a Custom TLS certificate in the TLS Authentication field.
      Password of the TLS certificate (that will be uploaded in the next step)
      Note: This is a mandatory field if a Custom TLS certificate is uploaded. AppViewX supports only password-protected Custom TLS certificates.
      TLS Certificate
      Note: This field is displayed only if you have selected to enter details of a Custom TLS certificate in the TLS Authentication field.
      To upload a custom TLS certificate:
      1. To navigate to the location of the custom TLS certificate, click within the field.
      2. Select the certificate file.
      3. Click Open.
      4. To upload the custom TLS certificate selected, click Upload.
      Note: AppViewX supports only password-protected Custom TLS Certificates.
      Use proxy
      Tip: The section on the right of the screen gives you a brief context of what is Proxy based routing. To read more, click Learn More (next to the Proxy based routing heading).
      A proxy server is required if the AppViewX Cloud Connector is unable to connect to your endpoints available in the internet.

      To use a proxy server for the deployment:

      1. Select the Use proxy checkbox.
      2. To select a preconfigured proxy (for the selected data center), from the Select Proxy dropdown list, select a proxy server.

      OR

      To create a new proxy server setting:

      1. Use the option shown below the Select Proxy dropdown list.

        The Add Proxy pop-up screen is displayed.

      2. Enter/Select the details required to add a proxy.
        Table 1. Field descriptions for the Add Proxy details
        Field Description
        *Proxy Name Name of the proxy server
        *Server IP IP address/FQDN of the proxy server
        *Port Port number of the proxy server
        URL From the dropdown menu, select the URL.
        Authentication To enable authentication for accessing the proxy server, select this checkbox.
        *Username
        Note: This field is enabled only when Authentication is selected.
        Enter the username required for accessing the proxy server.
        *Password
        Note: This field is enabled only when Authentication is selected.
        Enter the password required for accessing the proxy server.
    2. Click Finish.
      A confirmation message is displayed. AppViewX begins preparing the installer that you can download and proceed with the installation of the AppViewX Cloud Connector.
  11. Download the cloud connector installer and license file.
    1. On the Cloud Connector Added Successfully dialog box, when the Installer and License is Ready for Download, click Download Cloud Connector.
      Tip: Alternatively, you can click Go to Inventory and download the installer from the AppViewX Cloud Connector inventory.
      Tip: You can also choose to download the license file and the installer package individually. To do this:
      1. From the cloud connector inventory, click the Cloud Connector Name (for which you want to download the license file and the installer package).

        The selected cloud connector’s details are shown in a pane to your right.

      2. To download the AppViewX Cloud Connector installer package, click Download Cloud Connector. This is especially useful in the event that the installer has been deleted or is no longer usable.

        To download the license file, click Download License.

    2. Save the installer and the license file on the host machine.

      On the Settings :: Cloud Connector page, details of this AppViewX Cloud Connector are added in the inventory table, which is explained here.

  12. Install the AppViewX Cloud Connector Agent.
    Note: The following steps assume that:
    • All system prerequisites are fulfilled by the host machine.
    • The AppViewX Cloud Connector installer and license file are securely copied via SCP/SFTP to the host machine where the cloud connector is to be installed.
    • For installation on RHEL8+, the user must have sudo access with read/write/execute permissions for the following directories at the least:
      • /var/lib
      • /etc
      • /run
      • /usr/local/bin
      • /tmp
    1. To extract the installer, from the downloaded package, extract the tar.gz file using the command given below: tar -zxvf <filename>.tar.gz
      For example: tar - zxvf pesrv07-test-94-99-appviewx-appviewx-net-cloud-connector.tar.gz
    2. On the node where the AppViewX Cloud Connector agent will be installed, from the extracted installation package, run the ./install.sh script.
      The script will check if the installation prerequisites for the AppViewX Cloud Connector have been fulfilled.
      Note:

      Ensure that the license file is placed in the same location as the install.sh script. If the license file is placed in another location, run the install.sh script using the following command:

      ./install.sh <complete path of the license file with the filename>
      On successful verification of the prerequisites, you will be prompted to specify if you want to manage f5 BIG-IP devices and if you need auto-enrollment of the certificates.
    3. When prompted, enter the required input value(s):
      Important: If you choose to not enable any of the following features, to enable them later, you will have to reinstall the AppViewX Cloud Connector.
      1. If you want manage f5 BIG-IP devices, enter y/n for yes/no, respectively.
      2. When prompted to enable auto-enrollment of the certificate using one of the following supported auto-enrollment protocols, enter y only if the cloud connector is being installed in a demilitarized zone (DMZ) or devices in a restricted environment (that disables them from connecting to the <tenant>-aep directly.
      3. If you choose y (yes) here, enter the required protocol(s) name.
      Note: By default, the AppViewX certificate is enabled for auto-enrollment. To enable custom certificate for auto-enrollment:
      1. Execute the command ./avxctl upgrade gateway-cert.
      2. When prompted, enter the location of the custom certificate.
      Note: If you are a KUBE+ customer, the auto-enrollment gateway should be enabled as part of the installation for your KUBE+ usecases to work via the cloud connector.
    4. If you want to enable Syslog receiver for a near-real time configuration updates from the devices, enter y/n for yes/no, respectively. For configuring Syslog reception, refer to Platform User guide section, Syslog Reception.
      In case you have an older version of AppViewX on cloud and want to make use of Syslog capabilities for ADC, you must manually activate the Syslog flag by setting SYSLOG_ENABLED=true in the path ccpath/deps/properties.
    5. Enter the sudo password.
      After the relevant details have been entered, the installation proceeds. Installation logs, according to the outcome of the installation, are displayed.

      Given below are the sample installation logs:

      For installation on RHEL8+:

      Moving images and k3s binary as required for k3s installation...
      
      Triggering k3s install.....
      
      [INFO]  Skipping k3s download and verify
      [INFO]  Skipping installation of SELinux RPM
      [WARN]  Failed to find the k3s-selinux policy, please install:
          dnf install -y container-selinux
          dnf install -y https://rpm.rancher.io/k3s/stable/common/centos/8/noarch/k3s-selinux-0.4-1.el8.noarch.rpm
      
      [INFO]  Creating /usr/local/bin/kubectl symlink to k3s
      [INFO]  Creating /usr/local/bin/crictl symlink to k3s
      [INFO]  Creating /usr/local/bin/ctr symlink to k3s
      [INFO]  Creating killall script /usr/local/bin/k3s-killall.sh
      [INFO]  Creating uninstall script /usr/local/bin/k3s-uninstall.sh
      [INFO]  env: Creating environment file /etc/systemd/system/k3s.service.env
      [INFO]  systemd: Creating service file /etc/systemd/system/k3s.service
      [INFO]  systemd: Enabling k3s unit
      Created symlink /etc/systemd/system/multi-user.target.wants/k3s.service → /etc/systemd/system/k3s.service.
      [INFO]  systemd: Starting k3s
      
      
      k3s install success. Backing up the kubeconfig...
      Importing CC base image...
      unpacking docker.io/library/avx-mid-server-base:22.1.0.0 (sha256:5e1948b797dd19382f50faf06f921645337d53a1736016db81cd680c0afd7317)...done
      ***********************************************
      adding nameservers in coredns configmap
       
      configmap/coredns configured
      ***********************************************
      Deploying the Cloud Connector...
      NAME: avx-mid-server-starter
      LAST DEPLOYED: Wed May 10 11:02:29 2023
      NAMESPACE: cc
      STATUS: deployed
      REVISION: 1
      NOTES:
      1. It may take a couple of minutes for the Cloud Connector to be up.
        kubectl get pod --namespace cc
      ********************************************************************
      *    Congratulations!!! The installation completed successfully.   *
      *    Please wait till the Cloud Connector is up and running.       *
      ********************************************************************
      (1%) Cloud Connector status: Running
       Cloud Connector is up and running. 
      Note: If selinux is enabled on the node and is set to enforcing, the warning Failed to find the k3s-selinux policy... will show up in the logs. This warning can be ignored.

      For installation on an OS other than RHEL8+:

      Loaded image: rancher/k3s:v1.23.3-k3s1
      Loaded image: rancher/k3d-tools:5.2.2
      Loaded image: rancher/mirrored-pause:3.6
      [36mINFO[0m[0000] [SimpleConfig] Hostnetwork selected - disabling injection of docker host into the cluster, server load balancer and setting the api port to the k3s default 
      [33mWARN[0m[0000] No node filter specified                     
      [33mWARN[0m[0000] No node filter specified                     
      [33mWARN[0m[0000] No node filter specified                     
      [36mINFO[0m[0000] Prep: Network                                
      [36mINFO[0m[0000] Re-using existing network 'host' (8bebb4ae61001f74487d0aa6b315396405d0127c938da1206614d113295ae139) 
      [36mINFO[0m[0000] Created volume 'k3d-cc-images'               
      [36mINFO[0m[0000] Starting new tools node...                   
      [36mINFO[0m[0000] Starting Node 'k3d-cc-tools'                 
      [36mINFO[0m[0001] Creating node 'k3d-cc-server-0'              
      [36mINFO[0m[0001] Using the k3d-tools node to gather environment information 
      [36mINFO[0m[0001] Starting cluster 'cc'                        
      [36mINFO[0m[0001] Starting servers...                          
      [36mINFO[0m[0001] Starting Node 'k3d-cc-server-0'              
      [36mINFO[0m[0033] All agents already running.                  
      [36mINFO[0m[0033] All helpers already running.                 
      [36mINFO[0m[0033] Cluster 'cc' created successfully!           
      [36mINFO[0m[0034] You can now use it like this:                
      kubectl cluster-info
      Cluster setup is completed. Will start the deployment shortly...
      Importing the required images...
      [36mINFO[0m[0000] Importing image(s) into cluster 'cc'         
      [36mINFO[0m[0000] Importing images from 1 tarball(s)...        
      [36mINFO[0m[0000] Importing images '[/home/appviewx/CCTEST/deps/tools/mid-server-docker-image/avx-mid-server-base-22.1.0.0.tar]' into node 'k3d-cc-server-0'... 
      [36mINFO[0m[0024] Successfully imported image(s)               
      [36mINFO[0m[0024] Successfully imported 1 image(s) into 1 cluster(s) 
      Import in progress...
      [36mINFO[0m[0000] Importing image(s) into cluster 'cc'         
      [36mINFO[0m[0000] Importing images from 1 tarball(s)...        
      [36mINFO[0m[0000] Importing images '[/home/appviewx/CCTEST/deps/tools/mid-server-docker-image/k3d-tools-5.2.2.tar]' into node 'k3d-cc-server-0'... 
      [36mINFO[0m[0005] Successfully imported image(s)               
      [36mINFO[0m[0005] Successfully imported 1 image(s) into 1 cluster(s) 
      Import in progress...
      [36mINFO[0m[0000] Importing image(s) into cluster 'cc'         
      [36mINFO[0m[0000] Importing images from 1 tarball(s)...        
      [36mINFO[0m[0000] Importing images '[/home/appviewx/CCTEST/deps/tools/mid-server-docker-image/rancher-mirrored-coredns-coredns-1.8.6.tar]' into node 'k3d-cc-server-0'... 
      [36mINFO[0m[0007] Successfully imported image(s)               
      [36mINFO[0m[0007] Successfully imported 1 image(s) into 1 cluster(s) 
      [36mINFO[0m[0000] Importing image(s) into cluster 'cc'         
      [36mINFO[0m[0000] Importing images from 1 tarball(s)...        
      [36mINFO[0m[0000] Importing images '[/home/appviewx/CCTEST/deps/tools/mid-server-docker-image/rancher-local-path-provisioner-v0.0.21.tar]' into node 'k3d-cc-server-0'... 
      [36mINFO[0m[0004] Successfully imported image(s)               
      [36mINFO[0m[0004] Successfully imported 1 image(s) into 1 cluster(s) 
      [36mINFO[0m[0000] Importing image(s) into cluster 'cc'         
      [36mINFO[0m[0000] Importing images from 1 tarball(s)...        
      [36mINFO[0m[0000] Importing images '[/home/appviewx/CCTEST/deps/tools/mid-server-docker-image/rancher-mirrored-pause-3.6.tar]' into node 'k3d-cc-server-0'... 
      [36mINFO[0m[0003] Successfully imported image(s)               
      [36mINFO[0m[0003] Successfully imported 1 image(s) into 1 cluster(s) 
      Deploying the Cloud Connector...
      NAME: avx-mid-server-starter
      LAST DEPLOYED: Mon May 30 15:51:13 2022
      NAMESPACE: cc
      STATUS: deployed
      REVISION: 1
      NOTES:
      1. It may take a couple of minutes for the Cloud Connector to be up.
        kubectl get pod --namespace cc
      ********************************************************************
      *    Congratulations!!! The installation completed successfully.   *
      *    Please wait till the Cloud Connector is up and running.       *
      ********************************************************************
      (1%) Cloud Connector status: Running
      [32m Cloud Connector is up and running. (B[m
      
      Troubleshooting: For installation errors, refer to the Troubleshooting section.
      The AppViewX Cloud Connector consists of two important components—the starter plugin and the platform. The starter plugin component is installed along with the AppViewX Cloud Connector, in the same installation process.

      When installed, the starter plugin is used to initiate the download of the platform component. The platform component is used to host business use cases related to the AppViewX Cloud Connector. When the platform component download is in progress, it is indicated by the symbol prefixed to the platform component version number in the AppViewX Cloud Connector inventory details . A completed download/upgrade is indicated by the symbol in the same location .

      Note: Based on the internet bandwidth and the number of cloud connectors being installed, the downloading of the cloud connector may vary between 5 to 15 minutes.
  13. To approve the cloud connector installation:
    1. Go to (Menu) > Platform > Connectivity > Cloud Connector.
      The Settings :: Cloud Connector inventory page is displayed.
    2. For the cloud connector instance installed, from the Actions column, click Approve.
    Troubleshooting: If the AppViewX Cloud Connector instance has been approved but is not moved to the Running state, you can check the pod status and/or restart the pod(s), as required.