|
2 | 2 | displayed_sidebar: kots |
3 | 3 | --- |
4 | 4 |
|
5 | | -# About KOTS and kURL |
| 5 | +import Kots from "../docs/partials/kots/_kots-definition.mdx" |
6 | 6 |
|
7 | | -This topic describes Replicated KOTS and Replicated kURL, used for installing and upgrading applications in a Kubernetes cluster, and the Replicated admin console, used for managing application instances. |
| 7 | +# Introduction to KOTS |
| 8 | + |
| 9 | +This topic provides an introduction to the Replicated KOTS installer, including information about KOTS features, installation options, and user interfaces. |
8 | 10 |
|
9 | 11 | :::note |
10 | | -You must have the Replicated KOTS entitlement to use the KOTS and kURL installers and features. |
| 12 | +The Replicated KOTS entitlement is required to install applications with KOTS. For more information, see [Pricing](https://www.replicated.com/pricing) on the Replicated website. |
11 | 13 | ::: |
12 | 14 |
|
13 | | -## Replicated KOTS |
| 15 | +## Overview |
| 16 | + |
| 17 | +<Kots/> |
14 | 18 |
|
15 | | -Vendors that want to provide a UI-based installation and management experience for applications can leverage KOTS, which provides highly successful installs in diverse environments using a single installer. KOTS is a kubectl plugin that automates installations, making it quick and easy to install with minimal expertise. Applications are deployed securely to on-prem, online, and air gap environments. |
| 19 | +KOTS communicates securely with the Replicated vendor platform to synchronize customer licenses, check for available application updates, send instance data, share customer-generated support bundles, and more. |
16 | 20 |
|
17 | | -When KOTS is combined with kURL, kURL provisions an embedded cluster on a virtual machine (VM) or bare metal server for customers that do not have their own Kubernetes cluster. Then KOTS installs the application on the embedded cluster. For more information about kURL, see [kURL](#kurl). |
| 21 | +Installing an application with KOTS provides access to feautures such as: |
18 | 22 |
|
19 | | -KOTS also provides the Replicated admin console to make it easy for customers to install, upgrade, and manage their application instance. Customers can also use the kots CLI for installing and manage applications. For more information, see [Admin Console](#admin-console) and [kots CLI](#kots-cli). |
| 23 | +* Support for air gap installations |
| 24 | +* Support for installations on VMs or bare metal servers |
| 25 | +* The KOTS admin console, which provides a user interface where customers can install and manage their application instances |
| 26 | +* Instance telemetry automatically sent to the vendor portal for instances running in customer environments |
| 27 | +* Strict preflight checks that block installation if environment requirements are not met |
| 28 | +* Backup and restore with Replicated snapshots |
| 29 | +* Support for marking releases as required to prevent users from skipping them during upgrades |
20 | 30 |
|
21 | 31 | KOTS is an open source project that is maintained by Replicated. For more information, see the [kots](https://github.com/replicatedhq/kots) repository in GitHub. |
22 | 32 |
|
23 | | -## Admin Console |
| 33 | +## About Installing with KOTS |
24 | 34 |
|
25 | | -The admin console is a customer-facing user interface that includes built-in functionality allowing users to install, manage, update, configure, monitor, backup and restore, and troubleshoot their application instances. The admin console communicates securely with KOTS to synchronize licenses, check for upgrades, and so on. |
| 35 | +KOTS can be used to install applications in Kubernetes clusters, including: |
| 36 | +* Existing clusters brought by the user |
| 37 | +* Online or air gapped clusters |
| 38 | +* Embedded clusters provisioned on VMs or bare metal servers with Replicated embedded cluster or Replicated kURL |
26 | 39 |
|
27 | | - |
| 40 | +To install an application with KOTS, users first run an installation script to install KOTS in the target cluster and deploy the KOTS admin console. After KOTS is installed, users can log in to the KOTS admin console to upload their license file, configure the application, run preflight checks, and install and deploy the application. |
28 | 41 |
|
29 | | -[View a larger version of this image](/images/guides/kots/application.png) |
| 42 | +The following diagram demonstrates how a single release promoted to the Stable channel in the Replicated vendor platform can be installed using KOTS in an embedded cluster on a VM, in an air gapped cluster, and in an existing internet-connected cluster: |
| 43 | + |
| 44 | +<img alt="Embedded cluster, air gap, and existing cluster app installation workflows" src="/images/kots-installation-overview.png" width="650px"/> |
| 45 | + |
| 46 | +[View a larger version of this image](/images/kots-installation-overview.png) |
| 47 | + |
| 48 | +As shown in the diagram above: |
| 49 | +* For installations in existing internet-connected clusters, users run a command to install KOTS in their cluster. |
| 50 | +* For embedded cluster installations on VMs or bare metal servers, users run an installation script that both provisions a cluster in their environment and installs KOTS in the cluster. |
| 51 | +* For installations in air gapped clusters, users download air gap bundles for KOTS and the application from the Replicated download portal and then provide the bundles during installation. |
30 | 52 |
|
31 | | -<!-- |
32 | | -The admin console features include: |
| 53 | +All users must provide a license file to install with KOTS. After KOTS is installed in the cluster, users can access the KOTS admin console to provide their license file and deploy the application. |
33 | 54 |
|
34 | | -- **Config Screen:** Customize the customer-facing Config screen in the admin console to collect required or optional values from your customers that are used to run your application. |
35 | | -- **Custom Admin Console:** Customize the admin console with your company's branding, release notes, custom graphs display, application status display, and more. |
36 | | -- **Backup and Restore:** Enable backup and restore capabilities so that customers can implement full disaster recovery protection for the application and the admin console. |
37 | | -- **RBAC:** Use role-based access control (RBAC) for clusters and namespaces. By default, the KOTS installation sets RBAC for the cluster, but you can scope it to namespaces instead. |
38 | | ---> |
| 55 | +For more information about how to install applications with KOTS, see the [Installing an Application](/enterprise/installing-overview) section. |
39 | 56 |
|
40 | | -## kots CLI |
| 57 | +## KOTS User Interfaces |
41 | 58 |
|
42 | | -The kots command-line interface (CLI) is a kubectl plugin. Customers can run commands with the kots CLI to install and manage their application instances with KOTS programmatically. For more information, see [Installing the kots CLI](/reference/kots-cli-getting-started). |
| 59 | +This section describes the KOTS interfaces available to users for installing and managing applications. |
43 | 60 |
|
44 | | -## kURL |
| 61 | +### KOTS Admin Console |
| 62 | + |
| 63 | +KOTS provides an admin console to make it easy for users to install, manage, update, configure, monitor, backup and restore, and troubleshoot their application instance from a GUI. |
| 64 | + |
| 65 | +The following shows an example of the admin console dashboard for an application: |
| 66 | + |
| 67 | + |
| 68 | + |
| 69 | +[View a larger version of this image](/images/guides/kots/application.png) |
45 | 70 |
|
46 | | -Replicated kURL provisions Kubernetes clusters, which allow customers who do not have an existing cluster to install your application without provisioning a cluster themselves. Clusters created by kURL are called _embedded clusters_. Embedded clusters can be provisioned in online or air gap environments. |
| 71 | +### kots CLI |
47 | 72 |
|
48 | | -kURL has a built-in integration with KOTS through its KOTS add-on. With this integration, customers can run a kURL installation script in their virtual machine (VM) or bare metal server, which creates a cluster and then automatically installs KOTS in the cluster. Your application is then deployed with KOTS. |
| 73 | +The kots command-line interface (CLI) is a kubectl plugin. Customers can run commands with the kots CLI to install and manage their application instances with KOTS programmatically. |
49 | 74 |
|
50 | | -For information about how to install applications in embedded clusters, see [Installing with kURL](/enterprise/installing-embedded-cluster). For information about how to create a specification for kURL, see [Creating a Kubernetes Installer](/vendor/packaging-embedded-kubernetes). |
| 75 | +For information about getting started with the kots CLI, see [Installing the kots CLI](/reference/kots-cli-getting-started). |
51 | 76 |
|
52 | | -kURL is an open source project that is maintained by Replicated. For more information, see the [kURL repository](https://github.com/replicatedhq/kURL) in GitHub and the [kURL documentation](https://kurl.sh). |
| 77 | +The kots CLI can also be used to install an application without needing to access the admin console. This can be useful for automating installations and upgrades. For information about how to run automated installations with the kots CLI, see [Installing with Automation](/enterprise/installing-existing-cluster-automation). |
0 commit comments