Fixed upgrade docs (#157)
Signed-off-by: Jonsy13 <vedant.shrotria@chaosnative.com>
This commit is contained in:
parent
158467c135
commit
ec4bb42c24
|
|
@ -7,43 +7,38 @@ sidebar_label: Upgrade
|
||||||
---
|
---
|
||||||
|
|
||||||
## Upgrade ChaosCenter
|
## Upgrade ChaosCenter
|
||||||
To upgrade Litmus ChaosCenter from 2.0.0-Beta9 to 2.0.0, you can follow these steps:
|
|
||||||
|
|
||||||
1. Disconnect the agent components
|
To upgrade Litmus ChaosCenter from 2.3.0 to 2.4.0, you can follow these steps:
|
||||||
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.
|
|
||||||
|
|
||||||
<img src={require('../assets/disconnect-image.png').default} width="800" />
|
|
||||||
|
|
||||||
|
> Note: This step is not required if using Helm, Helm upgrade should work.
|
||||||
2. Upgrade the control plane (ChaosCenter)
|
|
||||||
To upgrade ChaosCenter, you can re-apply the manifest using the kubectl.
|
|
||||||
|
|
||||||
```bash
|
1. Upgrade the control plane (ChaosCenter)
|
||||||
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/2.0.0/docs/2.0.0/litmus-2.0.0.yaml
|
To upgrade ChaosCenter, you can re-apply the manifest using the kubectl.
|
||||||
```
|
|
||||||
|
```bash
|
||||||
2. Reinstall the agent components using litmusctl
|
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/2.4.0/litmus-2.4.0.yaml
|
||||||
>Note: While reinstallation, make sure to use the same agent name
|
```
|
||||||
|
|
||||||
To reinstall the ChaosAgents, use [Litmusctl](../litmusctl/usage-non-interactive-mode.md)
|
|
||||||
|
|
||||||
## Upgrade Mongodb DB Schema
|
## Upgrade Mongodb DB Schema
|
||||||
> Note: This step is not required for upgrading 2.0.0-Beta9 to 2.0.0
|
|
||||||
|
|
||||||
To upgrade the DB schema, make sure to delete the PV before re-installing ChaosCenter.
|
> Note: This step is not required if using Helm, Helm upgrade should work.
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
`kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/litmus-portal/upgrade-agents/control-plane/upgrade-agent.yaml`
|
||||||
|
|
||||||
## Upgrade ChaosAgent
|
## Upgrade ChaosAgent
|
||||||
|
|
||||||
To upgrade your ChaosAgent, you can follow these steps:
|
To upgrade your ChaosAgent, you can follow these steps:
|
||||||
|
|
||||||
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.
|
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.
|
||||||
|
|
||||||
<img src={require('../assets/user-guides/upgrade/upgrade-agent.png').default} width="800" />
|
<img src={require('../assets/user-guides/upgrade/upgrade-agent.png').default} width="800" />
|
||||||
|
|
||||||
|
|
||||||
Alternatively you can run the following command using litmusctl in the cluster containing the agent by providing `<CLUSTER_ID>` and `<PROJECT_ID>`.
|
Alternatively you can run the following command using litmusctl in the cluster containing the agent by providing `<CLUSTER_ID>` and `<PROJECT_ID>`.
|
||||||
|
|
||||||
```
|
```
|
||||||
litmusctl upgrade agent --cluster-id="<CLUSTER_ID>" --project-id="<PROJECT_ID>"
|
litmusctl upgrade agent --cluster-id="<CLUSTER_ID>" --project-id="<PROJECT_ID>"
|
||||||
```
|
```
|
||||||
|
|
||||||
> Note: v0.5.0 of [litmusctl](https://github.com/litmuschaos/litmusctl/blob/master/README.md) is required.
|
> Note: v0.7.0 of [litmusctl](https://github.com/litmuschaos/litmusctl/blob/master/README.md) is required.
|
||||||
|
|
|
||||||
|
|
@ -9,23 +9,14 @@ sidebar_label: Upgrade
|
||||||
## Upgrade ChaosCenter
|
## Upgrade ChaosCenter
|
||||||
To upgrade Litmus ChaosCenter from 2.1.0 to 2.2.0, you can follow these steps:
|
To upgrade Litmus ChaosCenter from 2.1.0 to 2.2.0, you can follow these steps:
|
||||||
|
|
||||||
1. Disconnect the agent components
|
> Note: This step is not required if using Helm, Helm upgrade should work.
|
||||||
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.
|
|
||||||
|
|
||||||
<img src={require('../assets/disconnect-image.png').default} width="800" />
|
|
||||||
|
|
||||||
|
1. Upgrade the control plane (ChaosCenter)
|
||||||
2. Upgrade the control plane (ChaosCenter)
|
|
||||||
To upgrade ChaosCenter, you can re-apply the manifest using the kubectl.
|
To upgrade ChaosCenter, you can re-apply the manifest using the kubectl.
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/2.2.0/litmus-2.2.0.yaml
|
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/2.2.0/litmus-2.2.0.yaml
|
||||||
```
|
```
|
||||||
|
|
||||||
2. Reinstall the agent components using litmusctl
|
|
||||||
>Note: While reinstallation, make sure to use the same agent name
|
|
||||||
|
|
||||||
To reinstall the ChaosAgents, use [Litmusctl](../litmusctl/usage-non-interactive-mode.md)
|
|
||||||
|
|
||||||
## Upgrade Mongodb DB Schema
|
## Upgrade Mongodb DB Schema
|
||||||
> Note: This step is not required for upgrading 2.1.0 to 2.2.0
|
> Note: This step is not required for upgrading 2.1.0 to 2.2.0
|
||||||
|
|
|
||||||
|
|
@ -10,6 +10,8 @@ sidebar_label: Upgrade
|
||||||
|
|
||||||
To upgrade Litmus ChaosCenter from 2.2.0 to 2.3.0, you can follow these steps:
|
To upgrade Litmus ChaosCenter from 2.2.0 to 2.3.0, you can follow these steps:
|
||||||
|
|
||||||
|
> Note: This step is not required if using Helm, Helm upgrade should work.
|
||||||
|
|
||||||
1. Upgrade the control plane (ChaosCenter)
|
1. Upgrade the control plane (ChaosCenter)
|
||||||
To upgrade ChaosCenter, you can re-apply the manifest using the kubectl.
|
To upgrade ChaosCenter, you can re-apply the manifest using the kubectl.
|
||||||
|
|
||||||
|
|
@ -17,12 +19,6 @@ To upgrade Litmus ChaosCenter from 2.2.0 to 2.3.0, you can follow these steps:
|
||||||
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/2.3.0/mkdocs/docs/2.3.0/litmus-2.3.0.yaml
|
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/2.3.0/mkdocs/docs/2.3.0/litmus-2.3.0.yaml
|
||||||
```
|
```
|
||||||
|
|
||||||
2. Reinstall the agent components using litmusctl
|
|
||||||
|
|
||||||
> Note: While reinstallation, make sure to use the same agent name
|
|
||||||
|
|
||||||
To reinstall the ChaosAgents, use [Litmusctl](../litmusctl/usage-non-interactive-mode.md)
|
|
||||||
|
|
||||||
## Upgrade Mongodb DB Schema
|
## Upgrade Mongodb DB Schema
|
||||||
|
|
||||||
> Note: This step is not required for upgrading 2.2.0 to 2.3.0
|
> Note: This step is not required for upgrading 2.2.0 to 2.3.0
|
||||||
|
|
|
||||||
|
|
@ -10,24 +10,15 @@ sidebar_label: Upgrade
|
||||||
|
|
||||||
To upgrade Litmus ChaosCenter from 2.3.0 to 2.4.0, you can follow these steps:
|
To upgrade Litmus ChaosCenter from 2.3.0 to 2.4.0, you can follow these steps:
|
||||||
|
|
||||||
1. Disconnect the agent components
|
> Note: This step is not required if using Helm, Helm upgrade should work.
|
||||||
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.
|
|
||||||
|
|
||||||
<img src={require('../assets/disconnect-image.png').default} width="800" />
|
1. Upgrade the control plane (ChaosCenter)
|
||||||
|
|
||||||
2. Upgrade the control plane (ChaosCenter)
|
|
||||||
To upgrade ChaosCenter, you can re-apply the manifest using the kubectl.
|
To upgrade ChaosCenter, you can re-apply the manifest using the kubectl.
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/2.4.0/litmus-2.4.0.yaml
|
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/2.4.0/litmus-2.4.0.yaml
|
||||||
```
|
```
|
||||||
|
|
||||||
3. Reinstall the agent components using litmusctl
|
|
||||||
|
|
||||||
> Note: While reinstallation, make sure to use the same agent name
|
|
||||||
|
|
||||||
To reinstall the ChaosAgents, use [Litmusctl](../litmusctl/usage-non-interactive-mode.md)
|
|
||||||
|
|
||||||
## Upgrade Mongodb DB Schema
|
## Upgrade Mongodb DB Schema
|
||||||
|
|
||||||
> Note: This step is not required if using Helm, Helm upgrade should work.
|
> Note: This step is not required if using Helm, Helm upgrade should work.
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue