Skip to content

Commit ca498e0

Browse files
authored
Update tcie-3.x-upgrading.md
1 parent 26f6db3 commit ca498e0

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

user/enterprise/tcie-3.x-upgrading.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -6,36 +6,36 @@ layout: en_enterprise
66

77
## Backups
88

9-
> Before upgrading, we **strongly recommend** making a backup of PostgreSQL database, Redis and RabbitMQ data.
9+
> Before upgrading, we **strongly recommend** backing up the PostgreSQL database, Redis, and RabbitMQ data.
1010
11-
It is recommended that your Travis CI Enterprise (TCIE) deployment recipes are automated. Thus backing up just data should be sufficient strategy to restore the TCIE 3.x installation from scratch and fill it with the data from the backup/dump files.
11+
It is recommended that your Travis CI Enterprise (TCIE) deployment recipes be automated. Thus, backing up just data should be a sufficient strategy to restore the TCIE 3.x installation from scratch and fill it with the data from the backup/dump files.
1212

1313
### Encryption Key
1414

15-
Without the encryption key you cannot access the information in your production database. To make sure that you can always recover your database, make a backup of this key.
15+
Without the encryption key, you cannot access the information in your production database. To ensure you can always recover your database, make a backup of this key.
1616

17-
> Without the encryption key the information in the database is not recoverable.
17+
> Without the encryption key, the information in the database is not recoverable.
1818
1919
{{ site.data.snippets.enterprise_3_encryption_key_backup }}
2020

2121
## Update your Travis CI Enterprise Platform
2222

23-
Run `kubectl kots admin-console -n [namspace]` to access admin console on `http://localhost:8800`.
23+
Run `kubectl kots admin-console -n [namspace]` to access the admin console on `http://localhost:8800`.
2424

2525
Click *Check for updates* in *Version history* menu:
2626

2727
![Check for updates](/images/tcie-3.x-check-updates.png)
2828

29-
If there’s a new version it will appear in *all versions* list. Click *deploy* to replace current installation with a new version:
29+
If there’s a new version it will appear in *all versions* list. Click *deploy* to replace the current installation with a new version:
3030

3131
![All versions](/images/tcie-3.x-list-of-versions.png)
3232

33-
> There will be a small amount of downtime while an update is installed. For this reason we recommend that you perform each update during a maintenance window.
33+
> There will be a small amount of downtime while an update is installed. For this reason, we recommend that you perform each update during a maintenance window.
3434
3535
## Update Replicated on the Platform
3636

37-
To update Replicated KOTS version on the Platform installation you'll want to run
38-
following command:
37+
To update the Replicated KOTS version on the Platform installation, you'll want to run
38+
the following command:
3939

4040
`curl https://kots.io/install | bash`
4141

@@ -61,9 +61,9 @@ On Ubuntu 16.04 and later, travis-worker ships inside a Docker container. To upd
6161

6262
In the rare event something goes wrong and/or you'd like to restore from a backup, please use the following steps:
6363

64-
1. Make sure you have backed up PostgreSQL database, Redis and RabbitMQ data - these services should be separate pods in Kubernetes cluster or run by you externally to TCIE 3.x installation
65-
2. Make a fresh install of Travis CI
66-
3. Restore the data in aforementioned tools in respective pods using their specific restore commands
64+
1. Make sure you have backed up PostgreSQL database, Redis, and RabbitMQ data - these services should be separate pods in the Kubernetes cluster or run by you externally to TCIE 3.x installation.
65+
2. Make a fresh install of Travis CI.
66+
3. Restore the data in the aforementioned tools in respective pods using their specific restore commands.
6767

6868
## Contact Enterprise Support
6969

0 commit comments

Comments
 (0)