You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/enterprise/installing-existing-cluster-automation.mdx
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,25 +47,23 @@ For a tutorial that demonstrates how to install a sample application using the K
47
47
48
48
[Replicated Embedded Cluster](/vendor/embedded-overview) does not support automated, or _headless_, installations with the KOTS CLI.
49
49
50
-
## Prerequisites
50
+
## Prerequisite
51
51
52
-
*Create a ConfigValues YAML file to define the configuration settings for the application. For air gap environments, ensure that you can access the ConfigValues file that you create from your installation environment.
52
+
Create a ConfigValues YAML file to define the configuration settings for the application. For air gap environments, ensure that you can access the ConfigValues file that you create from your installation environment.
53
53
54
-
A ConfigValues file includes the names of the configuration fields for the application along with a user-supplied `value` for each field. The ConfigValues file is specific to the application. For more information, see [Sharing a ConfigValues File](/vendor/releases-configvalues).
54
+
A ConfigValues file includes the names of the configuration fields for the application along with a user-supplied `value` for each field. The ConfigValues file is specific to the application. For more information, see [Sharing a ConfigValues File](/vendor/releases-configvalues).
55
55
56
-
**Example:**
56
+
**Example:**
57
57
58
-
<ConfigValuesExample/>
59
-
60
-
* (Air Gap Only) For air gap installations, ensure that the **Airgap Download Enabled** option is enabled for the license that will be used to install.
58
+
<ConfigValuesExample/>
61
59
62
60
## Install
63
61
64
62
This section provides the steps for installing an application with the KOTS CLI in different types of environments.
65
63
66
64
### Existing Cluster
67
65
68
-
To install in an existing cluster:
66
+
To install with KOTS in an existing cluster:
69
67
70
68
1. <InstallKotsCli/>
71
69
@@ -116,9 +114,9 @@ To install with kURL on a VM or bare metal server:
116
114
117
115
### Air Gap Existing Cluster
118
116
119
-
To install in an air gap existing cluster:
117
+
To install with KOTS in an air gap existing cluster:
120
118
121
-
1.Install the KOTS CLI. See [Manually Download and Install](/reference/kots-cli-getting-started#manually-download-and-install) in _Installing the KOTS CLI_.
Copy file name to clipboardExpand all lines: docs/enterprise/updating-app-manager.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ To update an application in air gap environments:
48
48
49
49
<BuildAirGapBundle/>
50
50
51
-
1. Ensure that you can access the downloaded bundle from the environment where the Admin Console is running.
51
+
1.After the build completes, download the bundle. Ensure that you can access the downloaded bundle from the environment where the Admin Console is running.
52
52
53
53
1. Run the following command to update the application:
Copy file name to clipboardExpand all lines: docs/partials/updating/_admin-console-air-gap.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ To perform an air gap update from the Admin Console:
6
6
7
7
<BuildAirGapBundle/>
8
8
9
-
1. Ensure that you can access the downloaded bundle from the environment where the Admin Console is running.
9
+
1.After the build completes, download the bundle. Ensure that you can access the downloaded bundle from the environment where the Admin Console is running.
10
10
1. In the Admin Console, go to the **Version History** tab.
0 commit comments