Skip to content

Commit ec4bb42

Browse files
authored
Fixed upgrade docs (#157)
Signed-off-by: Jonsy13 <[email protected]>
1 parent 158467c commit ec4bb42

File tree

4 files changed

+24
-51
lines changed

4 files changed

+24
-51
lines changed

website/docs/user-guides/upgrade.md

Lines changed: 18 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -7,43 +7,38 @@ sidebar_label: Upgrade
77
---
88

99
## Upgrade ChaosCenter
10-
To upgrade Litmus ChaosCenter from 2.0.0-Beta9 to 2.0.0, you can follow these steps:
11-
12-
1. Disconnect the agent components
13-
To disconnect agents, you can do it from the chaoscenter by clicking the `disconnect` button. With this, the subscriber deployment and agent-config will be removed from the agent cluster.
14-
15-
<img src={require('../assets/disconnect-image.png').default} width="800" />
16-
17-
18-
2. Upgrade the control plane (ChaosCenter)
19-
To upgrade ChaosCenter, you can re-apply the manifest using the kubectl.
20-
21-
```bash
22-
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/2.0.0/docs/2.0.0/litmus-2.0.0.yaml
23-
```
24-
25-
2. Reinstall the agent components using litmusctl
26-
>Note: While reinstallation, make sure to use the same agent name
27-
28-
To reinstall the ChaosAgents, use [Litmusctl](../litmusctl/usage-non-interactive-mode.md)
10+
11+
To upgrade Litmus ChaosCenter from 2.3.0 to 2.4.0, you can follow these steps:
12+
13+
> Note: This step is not required if using Helm, Helm upgrade should work.
14+
15+
1. Upgrade the control plane (ChaosCenter)
16+
To upgrade ChaosCenter, you can re-apply the manifest using the kubectl.
17+
18+
```bash
19+
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/2.4.0/litmus-2.4.0.yaml
20+
```
2921

3022
## Upgrade Mongodb DB Schema
31-
> Note: This step is not required for upgrading 2.0.0-Beta9 to 2.0.0
3223

33-
To upgrade the DB schema, make sure to delete the PV before re-installing ChaosCenter.
24+
> Note: This step is not required if using Helm, Helm upgrade should work.
25+
26+
To upgrade the DB schema, deploy the [upgrade-agent](https://raw.githubusercontent.com/litmuschaos/litmus/master/litmus-portal/upgrade-agents/control-plane/upgrade-agent.yaml) in your k8s cluster where ChaosCenter is installed. This manifest will create a Job, which will upgrade the mongoDB schema.
27+
28+
`kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/litmus-portal/upgrade-agents/control-plane/upgrade-agent.yaml`
3429

3530
## Upgrade ChaosAgent
31+
3632
To upgrade your ChaosAgent, you can follow these steps:
3733

3834
1. If an upgrade is available, you will get an option to upgrade your agent in the ChaosCenter. Upon clicking on the upgrade option, a modal will pop up providing you the litmusctl command which you can execute and your ChaosAgent will be upgraded.
3935

4036
<img src={require('../assets/user-guides/upgrade/upgrade-agent.png').default} width="800" />
4137

42-
4338
Alternatively you can run the following command using litmusctl in the cluster containing the agent by providing `<CLUSTER_ID>` and `<PROJECT_ID>`.
4439

4540
```
4641
litmusctl upgrade agent --cluster-id="<CLUSTER_ID>" --project-id="<PROJECT_ID>"
4742
```
4843

49-
> Note: v0.5.0 of [litmusctl](https://github.com/litmuschaos/litmusctl/blob/master/README.md) is required.
44+
> Note: v0.7.0 of [litmusctl](https://github.com/litmuschaos/litmusctl/blob/master/README.md) is required.

website/versioned_docs/version-2.2.0/user-guides/upgrade.md

Lines changed: 2 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -9,23 +9,14 @@ sidebar_label: Upgrade
99
## Upgrade ChaosCenter
1010
To upgrade Litmus ChaosCenter from 2.1.0 to 2.2.0, you can follow these steps:
1111

12-
1. Disconnect the agent components
13-
To disconnect agents, you can do it from the chaoscenter by clicking the `disconnect` button. With this, the subscriber deployment and agent-config will be removed from the agent cluster.
14-
15-
<img src={require('../assets/disconnect-image.png').default} width="800" />
12+
> Note: This step is not required if using Helm, Helm upgrade should work.
1613
17-
18-
2. Upgrade the control plane (ChaosCenter)
14+
1. Upgrade the control plane (ChaosCenter)
1915
To upgrade ChaosCenter, you can re-apply the manifest using the kubectl.
2016

2117
```bash
2218
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/2.2.0/litmus-2.2.0.yaml
2319
```
24-
25-
2. Reinstall the agent components using litmusctl
26-
>Note: While reinstallation, make sure to use the same agent name
27-
28-
To reinstall the ChaosAgents, use [Litmusctl](../litmusctl/usage-non-interactive-mode.md)
2920

3021
## Upgrade Mongodb DB Schema
3122
> Note: This step is not required for upgrading 2.1.0 to 2.2.0

website/versioned_docs/version-2.3.0/user-guides/upgrade.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -10,19 +10,15 @@ sidebar_label: Upgrade
1010

1111
To upgrade Litmus ChaosCenter from 2.2.0 to 2.3.0, you can follow these steps:
1212

13+
> Note: This step is not required if using Helm, Helm upgrade should work.
14+
1315
1. Upgrade the control plane (ChaosCenter)
1416
To upgrade ChaosCenter, you can re-apply the manifest using the kubectl.
1517

1618
```bash
1719
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/2.3.0/mkdocs/docs/2.3.0/litmus-2.3.0.yaml
1820
```
1921

20-
2. Reinstall the agent components using litmusctl
21-
22-
> Note: While reinstallation, make sure to use the same agent name
23-
24-
To reinstall the ChaosAgents, use [Litmusctl](../litmusctl/usage-non-interactive-mode.md)
25-
2622
## Upgrade Mongodb DB Schema
2723

2824
> Note: This step is not required for upgrading 2.2.0 to 2.3.0

website/versioned_docs/version-2.4.0/user-guides/upgrade.md

Lines changed: 2 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -10,24 +10,15 @@ sidebar_label: Upgrade
1010

1111
To upgrade Litmus ChaosCenter from 2.3.0 to 2.4.0, you can follow these steps:
1212

13-
1. Disconnect the agent components
14-
To disconnect agents, you can do it from the chaoscenter by clicking the `disconnect` button. With this, the subscriber deployment and agent-config will be removed from the agent cluster.
15-
16-
<img src={require('../assets/disconnect-image.png').default} width="800" />
13+
> Note: This step is not required if using Helm, Helm upgrade should work.
1714
18-
2. Upgrade the control plane (ChaosCenter)
15+
1. Upgrade the control plane (ChaosCenter)
1916
To upgrade ChaosCenter, you can re-apply the manifest using the kubectl.
2017

2118
```bash
2219
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/2.4.0/litmus-2.4.0.yaml
2320
```
2421

25-
3. Reinstall the agent components using litmusctl
26-
27-
> Note: While reinstallation, make sure to use the same agent name
28-
29-
To reinstall the ChaosAgents, use [Litmusctl](../litmusctl/usage-non-interactive-mode.md)
30-
3122
## Upgrade Mongodb DB Schema
3223

3324
> Note: This step is not required if using Helm, Helm upgrade should work.

0 commit comments

Comments
 (0)