Online Installation with Embedded Cluster

This topic describes how to install an application in an online (internet-connected) environment with the Replicated Embedded Cluster installer. For information about air gap installations with Embedded Cluster, see Air Gap Installation with Embedded Cluster.

Prerequisites

Before you install, complete the following prerequisites:

• Ensure that your installation environment meets the Embedded Cluster requirements. See Embedded Cluster Requirements in Installation Requirements.

• The application release that you want to install must include an Embedded Cluster Config.

• The license used to install must have the Embedded Cluster Enabled license field enabled. See Creating and Managing Customers.

• Ensure that the required domains are accessible from servers performing the installation. See Firewall Openings for Online Installations.

Install

To install an application with Embedded Cluster:

1. In the Vendor Portal, go to Customers and click on the target customer. Click Install instructions > Embedded Cluster.

   

   View a larger version of this image

   The Embedded Cluster install instructions dialog is displayed.

   

   View a larger version of this image

2. (Optional) In the Embedded Cluster install instructions dialog, under Select a version, select a specific application version to install. By default, the latest version is selected.

3. SSH onto the machine where you will install.

4. Run the first command in the Embedded Cluster install instructions dialog to download the installation assets as a .tgz.

5. Run the second command to extract the .tgz. The will produce the following files:

   • The installer
   • The license

6. Run the third command to install the release:

   sudo ./APP_SLUG install --license LICENSE_FILE

   Where:

   • APP_SLUG is the unique slug for the application.
   • LICENSE_FILE is the customer license.
   
   
   note

   Embedded Cluster supports installation options such as installing behind a proxy and changing the data directory used by Embedded Cluster. For the list of flags supported with the Embedded Cluster install command, see Embedded Cluster Install Command Options.

7. When prompted, enter a password for accessing the KOTS Admin Console.

   The installation command takes a few minutes to complete. During installation, Embedded Cluster completes tasks to prepare the cluster and install KOTS in the cluster. Embedded Cluster also automatically runs a default set of host preflight checks which verify that the environment meets the requirements for the installer.

   Example output:

   ? Enter an Admin Console password: ********
   ? Confirm password: ********
   ✔  Host files materialized!
   ✔  Running host preflights
   ✔  Node installation finished!
   ✔  Storage is ready!
   ✔  Embedded Cluster Operator is ready!
   ✔  Admin Console is ready!
   ✔  Additional components are ready!
   Visit the Admin Console to configure and install gitea-kite: http://104.155.145.60:30000

   At this point, the cluster is provisioned and the Admin Console is deployed, but the application is not yet installed.

8. Go to the URL provided in the output to access to the Admin Console.

9. On the Admin Console landing page, click Start.

10. On the Secure the Admin Console screen, review the instructions and click Continue. In your browser, follow the instructions that were provided on the Secure the Admin Console screen to bypass the warning.

11. On the Certificate type screen, either select Self-signed to continue using the self-signed Admin Console certificate or click Upload your own to upload your own private key and certificacte.

    By default, a self-signed TLS certificate is used to secure communication between your browser and the Admin Console. You will see a warning in your browser every time you access the Admin Console unless you upload your own certificate.

12. On the login page, enter the Admin Console password that you created during installation and click Log in.

13. On the Configure the cluster screen, optionally add nodes to the cluster before deploying the application. Click Continue.

14. On the Configure [App Name] screen, complete the fields for the application configuration options. Click Continue.

15. On the Validate the environment & deploy [App Name] screen, address any warnings or failures identified by the preflight checks and then click Deploy.

    Preflight checks are conformance tests that run against the target namespace and cluster to ensure that the environment meets the minimum requirements to support the application.

The Admin Console dashboard opens.

On the Admin Console dashboard, the application status changes from Missing to Unavailable while the application is being installed. When the installation is complete, the status changes to Ready. For example:

View a larger version of this image