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: user/enterprise/tcie-3.x-upgrading.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,36 +6,36 @@ layout: en_enterprise
6
6
7
7
## Backups
8
8
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.
10
10
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.
12
12
13
13
### Encryption Key
14
14
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.
16
16
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.
> 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.
34
34
35
35
## Update Replicated on the Platform
36
36
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:
39
39
40
40
`curl https://kots.io/install | bash`
41
41
@@ -61,9 +61,9 @@ On Ubuntu 16.04 and later, travis-worker ships inside a Docker container. To upd
61
61
62
62
In the rare event something goes wrong and/or you'd like to restore from a backup, please use the following steps:
63
63
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.
0 commit comments