Skip to content

Latest commit

 

History

History
90 lines (57 loc) · 3.59 KB

installing-existing-cluster.mdx

File metadata and controls

90 lines (57 loc) · 3.59 KB

import IntroExisting from "../partials/install/_intro-existing.mdx" import PrereqsExistingCluster from "../partials/install/_prereqs-existing-cluster.mdx" import LicenseFile from "../partials/install/_license-file-prereq.mdx" import InstallCommandPrompts from "../partials/install/_kots-install-prompts.mdx" import AppNameUI from "../partials/install/_placeholder-app-name-UI.mdx"

Online Installation in Existing Clusters with KOTS

Prerequisites

Complete the following prerequisites:

Install {#online}

To install KOTS and the application in an existing cluster:

  1. Run one of these commands to install the Replicated KOTS CLI and KOTS. As part of the command, you also specify a name and version for the application that you will install.

    • For the latest application version:

      curl https://kots.io/install | bash
kubectl kots install APP_NAME

    • For a specific application version:

      curl https://kots.io/install | bash
kubectl kots install APP_NAME --app-version-label=VERSION_LABEL

    Replace, where applicable:

    • VERSION_LABEL with the label for the version of the application to install. For example, --app-version-label=3.0.1.

    Examples:

    curl https://kots.io/install | bash
kubectl kots install application-name
    curl https://kots.io/install | bash
kubectl kots install application-name --app-version-label=3.0.1

  3. Access the Admin Console on port 8800. If the port forward is active, go to http://localhost:8800 to access the Admin Console.

    If you need to reopen the port forward to the Admin Console, run the following command:

    kubectl kots admin-console -n NAMESPACE

    Replace NAMESPACE with the namespace where KOTS is installed.

  4. Log in with the password that you created during installation.

  5. Upload your license file.

  6. On the config screen, complete the fields for the application configuration options and then click Continue.

  7. On the Preflight checks page, the application-specific preflight checks run automatically. 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. Click Deploy.

    :::note Replicated recommends that you address any warnings or failures, rather than dismissing them. Preflight checks help ensure that your environment meets the requirements for application deployment. :::

  8. (Minimal RBAC Only) If you are installing with minimal role-based access control (RBAC), KOTS recognizes if the preflight checks failed due to insufficient privileges. When this occurs, a kubectl CLI preflight command displays that lets you manually run the preflight checks. The Admin Console then automatically displays the results of the preflight checks. Click Deploy.

    kubectl CLI preflight command

    View a larger version of this image

The Admin Console dashboard opens.

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

Admin Console dashboard

View a larger version of this image