Skip to content

Commit 1a14a45

Browse files
committed
edits
1 parent 4ca54a3 commit 1a14a45

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/enterprise/installing-existing-cluster-automation.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ To install with KOTS in an existing cluster:
8080

8181
The following shows an example of the output from the kots install command:
8282

83-
```bash
83+
```
8484
• Deploying Admin Console
8585
• Creating namespace ✓
8686
• Waiting for datastore to be ready ✓

docs/vendor/releases-configvalues.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ For more information about installing from the command line, see [Installing fro
2424

2525
During installation, KOTS automatically generates a ConfigValues file and saves the file in a directory called `upstream`. After installation, you can view the generated ConfigValues file in the Admin Console **View files** tab or from the command line by running the `kubectl kots get config` command.
2626

27-
To get the ConfigValues file for a release:
27+
To get the ConfigValues file from an installed application instance:
2828

2929
1. Install the target release in a development environment. You can either install the release with Replicated Embedded Cluster or install in an existing cluster with KOTS. For more information, see [Online Installation with Embedded Cluster](/enterprise/installing-embedded) or [Online Installation in Existing Clusters](/enterprise/installing-existing-cluster).
3030

0 commit comments

Comments
 (0)