diff --git a/website/docs/concepts/introduction.md b/website/docs/concepts/introduction.md deleted file mode 100644 index a1e9ead..0000000 --- a/website/docs/concepts/introduction.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -id: introduction -title: Concepts -sidebar_label: Introduction ---- - -## Coming soon diff --git a/website/docs/concepts/overview.md b/website/docs/concepts/overview.md new file mode 100644 index 0000000..c28659f --- /dev/null +++ b/website/docs/concepts/overview.md @@ -0,0 +1,7 @@ +--- +id: overview +title: Overview +sidebar_label: Overview +--- + +## Coming soon diff --git a/website/docs/getting-started/basic-requirements.md b/website/docs/getting-started/basic-requirements.md deleted file mode 100644 index 2c2b97e..0000000 --- a/website/docs/getting-started/basic-requirements.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -id: basic-requirements -title: Prerequisites -sidebar_label: Basic Requirements ---- - -Before deploying LitmusChaos, make sure the following items are there - -- Kubernetes 1.15 or later - -- A Persistent volume of 20GB - - >Recommend to have a Persistent volume(PV) of 20GB, You can start with 1GB for test purposes as well. This PV is used as persistent storage to store the chaos config and chaos-metrics in the Portal. By default, litmus install would use the default storage class to allocate the PV. Provide this value - -- [Helm3](https://v3.helm.sh/) or [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) diff --git a/website/docs/getting-started/chaosagents-cluster-scope-installation.md b/website/docs/getting-started/chaosagents-cluster-scope-installation.md deleted file mode 100644 index f09254b..0000000 --- a/website/docs/getting-started/chaosagents-cluster-scope-installation.md +++ /dev/null @@ -1,135 +0,0 @@ ---- -id: chaosagents-cluster-scope-installation -title: ChaosAgents Cluster Scope Installation -sidebar_label: Cluster Scope ---- - -## Prerequisites - -- Before connecting a ChaosAgent to the [ChaosCenter](chaoscenter), learn about what is a [ChaosAgent](chaosagents) in Litmus. -- Make sure `litmusctl` is installed. - -## Installation - -Multiple external Kubernetes agents can be connected to the [ChaosCenter](chaoscenter) with the help of the command line utility litmusctl. - -The following steps will help you connect your ChaosAgents via litmusctl - -```bash -litmusctl agent connect -``` - -Next, you need to enter ChaosCenter details to login into your ChaosCenter account. Fields to be filled in: - -**ChaosCenter URL:** Enter the URL used to access the ChaosCenter. - -> Example, http://172.17.0.2:31696/ - -**Username:** Enter your LitmusPortal username.
-**Password:** Enter your LitmusPortal password. - -```bash -πŸ”₯ Connecting LitmusChaos agent - -πŸ“Ά Please enter LitmusChaos details -- -πŸ‘‰ Host URL where litmus is installed: http://172.17.0.2:31696/ -πŸ€” Username [admin]: admin -πŸ™ˆ Password: -βœ… Login Successful! -``` - -Upon successful login, there will be a list of existing projects displayed on the terminal. Select the desired project by entering the sequence number indicated against it. - -```bash -✨ Projects List: -1. MyFirstProject -2. MySecondProject - -πŸ”Ž Select Project: 1 -``` - -Next, select the installation mode as Cluster by entering the sequence number indicated against it. There will be a prerequisites check to verify ClusterRole and ClusterRoleBinding post selection. - -```shell -πŸ”Œ Installation Modes: -1. Cluster -2. Namespace - -πŸ‘‰ Select Mode [cluster]: 1 - -πŸƒ Running prerequisites check.... -πŸ”‘ clusterrole - βœ… -πŸ”‘ clusterrolebinding - βœ… - -🌟 Sufficient permissions. Connecting Agent -``` - -Next, enter the details of the new agent. - -Fields to be filled in
- -| Platforms | Download Link | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | -| **Agent Name:** | Enter the name for the new agent. | -| **Agent Description:** | Fill in details about the agent. | -| **Platform Name:** | Enter the platform name on which this agent is hosted. For example, AWS, GCP, Rancher etc. | -| **Enter the namespace:** | You can either enter an existing namespace or enter a new namespace. In cases where the namespace does not exist, litmusctl creates it for you. | -| **Enter service account:** | Enter a name for your service account. | - -```shell -πŸ”— Enter the details of the agent ---- -🀷 Agent Name: my-agent -πŸ“˜ Agent Description: This is a new agent. -πŸ“¦ Platform List -1. AWS -2. GKE -3. Openshift -4. Rancher -5. Others -πŸ”Ž Select Platform [Others]: 5 -πŸ“ Enter the namespace (new or existing) [litmus]: litmus -πŸ”‘ Enter service account [litmus]: litmus -``` - -Once, all these steps are implemented you will be able to see a summary of all the entered fields. -After verification of these details, you can proceed with the connection of the agent by entering Y. The process of connection might take up to a few seconds. - -```shell -πŸ“Œ Summary -------------------------- - -Agent Name: my-agent -Agent Description: This is a new agent. -Platform Name: Others -Namespace: litmus -Service Account: litmus -Installation Mode: cluster - -------------------------------------- - -🀷 Do you want to continue with the above details? [Y/N]: Y - -πŸ’‘ Connecting agent to Litmus Portal. -πŸƒ Agents running!! -πŸš€ Agent Connection Successful!! πŸŽ‰ -πŸ‘‰ Litmus agents can be accessed here: http://172.17.0.2:31696/targets -``` - ---- - -## **Verify the new Agent Connection** - -To verify, if the connection process was successful you can view the list of connected agents from the Targets section on your ChaosCenter and ensure that the connected agent is in Active State. - -## Resources - -#### Videos - - - -## Learn More - -- [Install ChaosAgents in Namespace Scope](chaosagents-namespace-scope-installation) -- [Install ChaosCenter in Cluster Scope](chaoscenter-cluster-scope-installation) -- [Install ChaosCenter in Namespace Scope](chaoscenter-namespace-scope-installation) -- [Setup Endpoints and Access ChaosCenter without Ingress](setup-without-ingress) -- [Setup Endpoints and Access ChaosCenter with Ingress](setup-with-ingress) diff --git a/website/docs/getting-started/chaosagents-namespace-scope-installation.md b/website/docs/getting-started/chaosagents-namespace-scope-installation.md deleted file mode 100644 index b64ce46..0000000 --- a/website/docs/getting-started/chaosagents-namespace-scope-installation.md +++ /dev/null @@ -1,139 +0,0 @@ ---- -id: chaosagents-namespace-scope-installation -title: ChaosAgents Namespace Scope Installation -sidebar_label: Namespace Scope ---- - -## Prerequisites - -- Before connecting a ChaosAgent to the [ChaosCenter](chaoscenter), learn about what is a [ChaosAgent](chaosagents) in Litmus. -- Make sure `litmusctl` is installed. - -## Installation - -Multiple external ChaosAgents can be connected to application namespace/s with the help of the command line utility `litmusctl`. - -The following steps will help you connect your ChaosAgents via litmusctl - -```bash -litmusctl agent connect -``` - -Next, you need to enter ChaosCenter details to login into your ChaosCenter account. Fields to be filled in: - -**ChaosCenter URL:** Enter the URL used to access the ChaosCenter. - -> Example, http://172.17.0.2:31696/ - -**Username:** Enter your LitmusPortal username.
-**Password:** Enter your LitmusPortal password. - -```bash -πŸ”₯ Connecting LitmusChaos agent - -πŸ“Ά Please enter LitmusChaos details -- -πŸ‘‰ Host URL where litmus is installed: http://172.17.0.2:31696/ -πŸ€” Username [admin]: admin -πŸ™ˆ Password: -βœ… Login Successful! -``` - -Upon successful login, there will be a list of existing projects displayed on the terminal. Select the desired project by entering the sequence number indicated against it. - -```bash -✨ Projects List: -1. MyFirstProject -2. MySecondProject - -πŸ”Ž Select Project: 1 -``` - -Next, select the installation mode as Namespace by entering the sequence number indicated against it. There will be a prerequisites check to verify Role and RoleBinding post selection. - -```shell -πŸ”Œ Installation Modes: -1. Cluster -2. Namespace - -πŸ‘‰ Select Mode [cluster]: 2 - -πŸƒ Running prerequisites check.... -πŸ”‘ role - βœ… -πŸ”‘ rolebinding - βœ… - -🌟 Sufficient permissions. Connecting Agent -``` - -Next, enter the details of the new agent. - -Fields to be filled in
- -| Platforms | Download Link | -| -------------------------- | -------------------------------------------------------------------------------------------------------- | -| **Agent Name:** | Enter the name for the new agent. | -| **Agent Description:** | Fill in details about the agent. | -| **Platform Name:** | Enter the platform name on which this agent is hosted. For example, AWS, GCP, Rancher etc. | -| **Enter the namespace:** | You can either enter an existing namespace (where your application is running) or create a new namespace | -| **Enter service account:** | Enter a name for your service account. | - -> Since Namespaced Scope ChaosAgent don't have Cluster Wide Permission therefore if you are willing to install the ChaosAgent in new namespace, the namespace won't be automatically created - -> If you install the Namespaced Scope ChaosAgent in the same namespace as ChaosCenter, since the subscriber is already present in the namespace, you will see this message `🚫 Subscriber already present. Please enter a different namespace` in such cases you have to create a new namespace in the cluster to install the ChaosAgent else choose the existing namespace where your application resides _(besides the ns where ChaosCenter is present)_ - -```shell -πŸ”— Enter the details of the agent ---- -🀷 Agent Name: my-agent -πŸ“˜ Agent Description: This is a new namespace agent. -πŸ“¦ Platform List -1. AWS -2. GKE -3. Openshift -4. Rancher -5. Others -πŸ”Ž Select Platform [Others]: 5 -πŸ“ Enter the namespace (new or existing) [litmus]: litmus -πŸ”‘ Enter service account [litmus]: litmus -``` - -Once, all these steps are implemented you will be able to see a summary of all the entered fields. -After verification of these details, you can proceed with the connection of the agent by entering Y. The process of connection might take up to a few seconds. - -```shell -πŸ“Œ Summary -------------------------- - -Agent Name: my-agent -Agent Description: This is a new agent. -Platform Name: Others -Namespace: litmus -Service Account: litmus -Installation Mode: namespace - -------------------------------------- - -🀷 Do you want to continue with the above details? [Y/N]: Y - -πŸ’‘ Connecting agent to Litmus Portal. -πŸƒ Agents running!! -πŸš€ Agent Connection Successful!! πŸŽ‰ -πŸ‘‰ Litmus agents can be accessed here: http://172.17.0.2:31696/targets -``` - ---- - -## **Verify the new Agent Connection** - -To verify, if the connection process was successful you can view the list of connected agents from the Targets section on your ChaosCenter and ensure that the connected agent is in Active State. - -## Resources - -#### Videos - - - -## Learn More - -- [Install ChaosAgents in Cluster Scope](chaosagents-cluster-scope-installation) -- [Install ChaosCenter in Cluster Scope](chaoscenter-cluster-scope-installation) -- [Install ChaosCenter in Namespace Scope](chaoscenter-namespace-scope-installation) -- [Setup Endpoints and Access ChaosCenter without Ingress](setup-without-ingress) -- [Setup Endpoints and Access ChaosCenter with Ingress](setup-with-ingress) diff --git a/website/docs/getting-started/chaosagents.md b/website/docs/getting-started/chaosagents.md deleted file mode 100644 index a1fe5cb..0000000 --- a/website/docs/getting-started/chaosagents.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -id: chaosagents -title: ChaosAgents -sidebar_label: ChaosAgents ---- - -A **ChaosAgent** in Litmus is nothing but the target cluster where Chaos would be injected via Litmus. There should always be atleast one or more than one ChaosAgents connected to the ChaosCenter. Each individual ChaosAgent can be chosen to be the Target Agent for Chaos Injection. - -## Types of ChaosAgents - -In Litmus, ChaosAgents can be classified into two types - -- Self Agent -- External Agent - -As part of the Litmus installation, a Self Agent would be registered as a default Agent in the ChaosCenter. The same cluster where Litmus is installed is chosen as the Self Agent by the installer. From the ChaosCenter you can now induce chaos into this Self Agent and observe the results. - -Since the ChaosCenter is Cross Cloud, you can connect multiple external Kubernetes agents to the same with the help of the command line utility litmusctl. Once connected you can manage, monitor, observe and induce chaos from the ChaosCenter to the respective ChaosAgents. diff --git a/website/docs/getting-started/installation.md b/website/docs/getting-started/installation.md new file mode 100644 index 0000000..2da57ef --- /dev/null +++ b/website/docs/getting-started/installation.md @@ -0,0 +1,204 @@ +--- +id: installation +title: ChaosCenter Cluster Scope Installation +sidebar_label: Installation +--- + +--- + +## Prerequisites + +Before deploying LitmusChaos, make sure the following items are there + +- Kubernetes 1.17 or later + +- A Persistent volume of 20GB + + :::note + Recommend to have a Persistent volume(PV) of 20GB, You can start with 1GB for test purposes as well. This PV is used as persistent storage to store the chaos config and chaos-metrics in the Portal. By default, litmus install would use the default storage class to allocate the PV. Provide this value + ::: + +- [Helm3](https://v3.helm.sh/) or [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) + +## Installation + +Installation of Litmus can be done using either of the below methods + +- [Helm3](#install-litmus-using-helm) chart +- [Kubectl](#install-litmus-using-kubectl) yaml spec file + +### Install Litmus using Helm + +The helm chart will install all the required service account configuration and ChaosCenter. + +The following steps will help you install Litmus ChaosCenter via helm. + +#### Step-1: Add the litmus helm repository + +```bash +helm repo add litmuschaos https://litmuschaos.github.io/litmus-helm/ +helm repo list +``` + +#### Step-2: Create the namespace on which you want to install Litmus ChaosCenter + +- The litmus infra components will be placed in this namespace. + +> The ChaosCenter can be placed in any namespace, but for this scenario we are choose `litmus` as the namespace. + +```bash +kubectl create ns litmus +``` + +#### Step-3: Install Litmus ChaosCenter + +```bash +helm install chaos litmuschaos/litmus-2-0-0-beta --namespace=litmus --devel +``` + +Expected Output + +``` +NAME: chaos +LAST DEPLOYED: Tue Jun 15 19:20:09 2021 +NAMESPACE: litmus +STATUS: deployed +REVISION: 1 +TEST SUITE: None +NOTES: +Thank you for installing litmus-2-0-0-beta πŸ˜€ + +Your release is named chaos and its installed to namespace: litmus. + +Visit https://docs.litmuschaos.io/docs/getstarted/ to find more info. +``` + +> **Note:** Litmus uses Kubernetes CRDs to define chaos intent. Helm3 handles CRDs better than Helm2. Before you start running a chaos experiment, verify if Litmus is installed correctly. + +### **Install Litmus using kubectl ** + +#### **Create the namespace on which you want to install Litmus ChaosCenter** + +```bash +kubectl create ns litmus +``` + +#### **Install Litmus ChaosCenter** + +Applying the manifest file will install all the required service account configuration and ChaosCenter. + +```bash +kubectl apply -f https://litmuschaos.github.io/litmus/2.0.0-Beta/litmus-2.0.0-Beta.yaml -n litmus +``` + +--- + +## **Verify your installation** + +#### **Verify if the frontend, server, and database pods are running** + +- Check the pods in the namespace where you installed Litmus: + + ```bash + kubectl get pods -n litmus + ``` + + Expected Output + + ```bash + NAME READY STATUS RESTARTS AGE + litmusportal-frontend-97c8bf86b-mx89w 1/1 Running 2 6m24s + litmusportal-server-5cfbfc88cc-m6c5j 2/2 Running 2 6m19s + mongo-0 1/1 Running 0 6m16s + ``` + +- Check the services running in the namespace where you installed Litmus: + + ```bash + kubectl get svc -n litmus + ``` + + Expected Output + + ```bash + NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE + litmusportal-frontend-service NodePort 10.100.105.154 9091:30229/TCP 7m14s + litmusportal-server-service NodePort 10.100.150.175 9002:30479/TCP,9003:31949/TCP 7m8s + mongo-service ClusterIP 10.100.226.179 27017/TCP 7m6s + ``` + +--- + +## **Accessing the ChaosCenter** + +To setup and login to ChaosCenter expand the available services just created and copy the `PORT` of the `litmusportal-frontend-service` service + +```bash +kubectl get svc -n litmus +``` + +Expected Output + +```bash +NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE +chaos-litmus-portal-mongo ClusterIP 10.104.107.117 27017/TCP 2m +litmusportal-frontend-service NodePort 10.101.81.70 9091:30385/TCP 2m +litmusportal-server-service NodePort 10.108.151.79 9002:32456/TCP,9003:31160/TCP 2m +``` + +> **Note**: In this case, the PORT for `litmusportal-frontend-service` is `30385`. Yours will be different. + +Once you have the PORT copied in your clipboard, simply use your IP and PORT in this manner `:` to access the Litmus ChaosCenter. + +For example: + +```yaml +http://172.17.0.3:30385/ +``` + +> Where `172.17.0.3` is my NodeIP and `30385` is the frontend service PORT. If using a LoadBalancer, the only change would be to provide a `:`. [Learn more about how to access ChaosCenter with LoadBalancer](../user-guide/setup-without-ingress#with-loadbalancer.md) + +You should be able to see the Login Page of Litmus ChaosCenter. The **default credentials** are + +```yaml +Username: admin +Password: litmus +``` + + + +By default you are assigned with a default project with Owner permissions. + + + +## **Verify Successful Registration of the Self Agent** + +Once the project is created, the cluster is automatically registered as a chaos target via installation of [ChaosAgents](resources#chaosagents). This is represented as [Self-Agent](resources#types-of-chaosagents) in [ChaosCenter](resources#chaoscenter). + +```bash +kubectl get pods -n litmus +``` + +```bash +NAME READY STATUS RESTARTS AGE +argo-server-58cb64db7f-pmbnq 1/1 Running 0 5m32s +chaos-exporter-547b59d887-4dm58 1/1 Running 0 5m27s +chaos-operator-ce-84ddc8f5d7-l8c6d 1/1 Running 0 5m27s +event-tracker-5bc478cbd7-xlflb 1/1 Running 0 5m28s +litmusportal-frontend-97c8bf86b-mx89w 1/1 Running 0 15m +litmusportal-server-5cfbfc88cc-m6c5j 2/2 Running 1 15m +mongo-0 1/1 Running 0 15m +subscriber-958948965-qbx29 1/1 Running 0 5m30s +workflow-controller-78fc7b6c6-w82m7 1/1 Running 0 5m32s +``` + +## Resources + + + +## Learn More + +- [Install ChaosCenter in Namespace Scope](../user-guides/chaoscenter-namespace-scope-installation.md) +- [Connect External ChaosAgents to ChaosCenter](../user-guides/chaosagents-installation.md) +- [Setup Endpoints and Access ChaosCenter without Ingress](../user-guides/setup-without-ingress.md) +- [Setup Endpoints and Access ChaosCenter with Ingress](../user-guides/setup-with-ingress.md) diff --git a/website/docs/getting-started/learning-litmus.md b/website/docs/getting-started/learning-litmus.md deleted file mode 100644 index 9022705..0000000 --- a/website/docs/getting-started/learning-litmus.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -id: learning-litmus -title: Various Ways of Learning Litmus -sidebar_label: Learning Litmus ---- - ---- - -### Through Videos - - - - - - - - - - - - - - -
- - - -
- - - -
- - - -
- ---- - -### Through Blogs - - - - - - - - - - - - - - - - - - - - - - -
- - -
-
- Getting Started with Litmus 2.0 in Google Kubernetes Engine -
- - 		- - -
-
- Getting Started with LitmusChaos 2.0 in Azure Kubernetes Service -
- -
- - -
-
- Chaos Engineering with Litmus-portal on Okteto cloud -
- - 		- - -
-
- Introducing Teaming in LitmusChaos to ease your Chaos Engineering experience -
- -
- - -
-
- Part-1: A Beginner's Practical Guide to Containerisation and Chaos Engineering with LitmusChaos 2.0 -
- - 		- - -
-
- Part-2: A Beginner’s Practical Guide to Containerisation and Chaos Engineering with LitmusChaos 2.0 -
- -
- - -
-
- Litmus 2.0 - Simplifying Chaos Engineering for Enterprises -
- - 		- - -
-
- Workflow Creation with Litmus 2.0 Beta -
- -
- - -
-
- How Litmus Orchestrates Chaos -
- - 		- - -
-
- Custom Workflow with MyHub using Litmus Portal -
- -
- ---- - -### Beginner Friendly Resources - -✨ Below is a list of beginner-level resources, everything you need to get started in your Cloud-Native Chaos Engineering journey ✨ - -[List of Beginner Friendly Resources](https://github.com/litmuschaos/litmus/tree/master/resources) diff --git a/website/docs/getting-started/chaoscenter.md b/website/docs/getting-started/resources.md similarity index 58% rename from website/docs/getting-started/chaoscenter.md rename to website/docs/getting-started/resources.md index db2f115..a89524f 100644 --- a/website/docs/getting-started/chaoscenter.md +++ b/website/docs/getting-started/resources.md @@ -1,14 +1,16 @@ --- -id: chaoscenter -title: ChaosCenter -sidebar_label: ChaosCenter +id: resources +title: Resources +sidebar_label: Resources --- --- +## ChaosCenter + The **ChaosCenter** is a single source of truth to control all the different Chaos Activities happening around Litmus. From the ChaosCenter you get the freedom to manage every single part of Litmus and shape your workflows exactly the way you want it. -**ChaosCenter comes pre-packaged** as a part of LitmusChaos installation and can be easily accessed via Ingress, NodePort or LoadBalancer. Since Litmus has Cross-Cloud support, you get seamless access to the ChaosCenter irrespectively of where you deploy it. +**ChaosCenter comes pre-packaged** as a part of LitmusChaos installation and can be easily accessed via [Ingress](setup-with-ingress), [NodePort](setup-without-ingress#with-nodeport) or [LoadBalancer](setup-without-ingress#with-loadbalancer). Since Litmus has Cross-Cloud support, you get seamless access to the ChaosCenter irrespectively of where you deploy it. > [Get a broader view of which Platforms are supported by Litmus](https://github.com/litmuschaos/litmus/tree/master/litmus-portal#platforms-support) @@ -50,3 +52,18 @@ The ChaosCenter gives you access to a plethora of features, the major ones inclu
  • Measure and Analyse the Resilience Score of each workflow
    • + +## ChaosAgents + +A **ChaosAgent** in Litmus is nothing but the target cluster where Chaos would be injected via Litmus. There should always be atleast one or more than one ChaosAgents connected to the [ChaosCenter](#chaoscenter). Each individual ChaosAgent can be chosen to be the Target Agent for Chaos Injection. + +## Types of ChaosAgents + +In Litmus, ChaosAgents can be classified into two types + +- Self Agent +- External Agent + +As part of the Litmus installation, a Self Agent would be registered as a default Agent in the ChaosCenter. The same cluster where Litmus is installed is chosen as the Self Agent by the installer. From the ChaosCenter you can now induce chaos into this Self Agent and observe the results. + +Since the ChaosCenter is Cross Cloud, you can connect multiple external Kubernetes agents to the same with the help of the command line utility [litmusctl](../litmusctl/installation.md). Once connected you can manage, monitor, observe and induce chaos from the ChaosCenter to the respective ChaosAgents. diff --git a/website/docs/getting-started/run-your-first-workflow.md b/website/docs/getting-started/run-your-first-workflow.md index cbe9a38..a0cedce 100644 --- a/website/docs/getting-started/run-your-first-workflow.md +++ b/website/docs/getting-started/run-your-first-workflow.md @@ -8,10 +8,10 @@ Welcome to this scenario, in this section you will get an overview of how to exe ## Prerequisites -Before starting with your first Chaos Workflow make sure the [Litmus ChaosCenter](chaoscenter) is installed in either one of these scopes +Before starting with your first Chaos Workflow make sure the [Litmus ChaosCenter](resources#chaoscenter) is installed in either one of these scopes -- [Cluster Scope](chaoscenter-cluster-scope-installation) -- [Namespace Scope](chaoscenter-namespace-scope-installation) +- [Cluster Scope](../user-guides/chaoscenter-cluster-scope-installation.md) +- [Namespace Scope](../user-guides/chaoscenter-namespace-scope-installation.md) ## Aim of the scenario @@ -32,7 +32,7 @@ In this scenario we will execute a pod-delete fault on a sample micro-service ap

    -2. Select **Self Agent** as the target [ChaosAgent](chaosagents) for Chaos Injection. This is where we'll select which ChaosAgent to choose as the Target Agent. +2. Select **Self Agent** as the target [ChaosAgent](resources#chaosagents) for Chaos Injection. This is where we'll select which ChaosAgent to choose as the Target Agent. Selecting Self Agent @@ -125,35 +125,16 @@ And with that you have successfully scheduled your first Chaos Workflow with Lit ## Resources -#### Videos - -#### Blogs +### Beginner Friendly Resources - - - - - -
    - - -
    -
    - Getting Started with LitmusChaos 2.0 in Azure Kubernetes Service -
    -     -     		- - -
    -
    - Getting Started with Litmus 2.0 in Google Kubernetes Engine -
    -     -
    +✨ Below is a list of beginner-level resources, everything you need to get started in your Cloud-Native Chaos Engineering journey ✨ -## Learn More +[List of Beginner Friendly Resources](https://github.com/litmuschaos/litmus/tree/master/resources) -- [Resources to Learn More about Litmus](learning-litmus) +## Various Ways of Learning Litmus + +- [Learn by Concept](../concepts/overview.md) +- [Learn by User Guides](../user-guides/overview.md) +- [Learn by Running a sample Katakoda Scenario](https://www.katacoda.com/litmusbot/scenarios/getting-started-with-litmus) diff --git a/website/docs/litmusctl/cluster-scope-installation.md b/website/docs/litmusctl/cluster-scope-installation.md index 7c77834..9790ca8 100644 --- a/website/docs/litmusctl/cluster-scope-installation.md +++ b/website/docs/litmusctl/cluster-scope-installation.md @@ -1,7 +1,127 @@ --- id: cluster-scope-installation -title: Installing Agent with Cluster Scope +title: Installing ChaosAgents with Cluster Scope sidebar_label: Cluster Scope --- -## Coming soon +Multiple external [ChaosAgents](../getting-started/chaosagents.md) can be connected to the [ChaosCenter](../getting-started/chaoscenter.md) with the help of the command line utility [litmusctl](installation) + +The following steps will help you connect your ChaosAgents via litmusctl + +```bash +litmusctl agent connect +``` + +Next, you need to enter ChaosCenter details to login into your ChaosCenter account. Fields to be filled in: + +**ChaosCenter URL:** Enter the URL used to access the ChaosCenter. + +> Example, http://172.17.0.2:31696/ + +**Username:** Enter your LitmusPortal username.
    +**Password:** Enter your LitmusPortal password. + +```bash +πŸ”₯ Connecting LitmusChaos agent + +πŸ“Ά Please enter LitmusChaos details -- +πŸ‘‰ Host URL where litmus is installed: http://172.17.0.2:31696/ +πŸ€” Username [admin]: admin +πŸ™ˆ Password: +βœ… Login Successful! +``` + +Upon successful login, there will be a list of existing projects displayed on the terminal. Select the desired project by entering the sequence number indicated against it. + +```bash +✨ Projects List: +1. MyFirstProject +2. MySecondProject + +πŸ”Ž Select Project: 1 +``` + +Next, select the installation mode as Cluster by entering the sequence number indicated against it. There will be a prerequisites check to verify ClusterRole and ClusterRoleBinding post selection. + +```shell +πŸ”Œ Installation Modes: +1. Cluster +2. Namespace + +πŸ‘‰ Select Mode [cluster]: 1 + +πŸƒ Running prerequisites check.... +πŸ”‘ clusterrole - βœ… +πŸ”‘ clusterrolebinding - βœ… + +🌟 Sufficient permissions. Connecting Agent +``` + +Next, enter the details of the new agent. + +Fields to be filled in
    + +| Platforms | Download Link | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | +| **Agent Name:** | Enter the name for the new agent. | +| **Agent Description:** | Fill in details about the agent. | +| **Platform Name:** | Enter the platform name on which this agent is hosted. For example, AWS, GCP, Rancher etc. | +| **Enter the namespace:** | You can either enter an existing namespace or enter a new namespace. In cases where the namespace does not exist, litmusctl creates it for you. | +| **Enter service account:** | Enter a name for your service account. | + +```shell +πŸ”— Enter the details of the agent ---- +🀷 Agent Name: my-agent +πŸ“˜ Agent Description: This is a new agent. +πŸ“¦ Platform List +1. AWS +2. GKE +3. Openshift +4. Rancher +5. Others +πŸ”Ž Select Platform [Others]: 5 +πŸ“ Enter the namespace (new or existing) [litmus]: litmus +πŸ”‘ Enter service account [litmus]: litmus +``` + +Once, all these steps are implemented you will be able to see a summary of all the entered fields. +After verification of these details, you can proceed with the connection of the agent by entering Y. The process of connection might take up to a few seconds. + +```shell +πŸ“Œ Summary -------------------------- + +Agent Name: my-agent +Agent Description: This is a new agent. +Platform Name: Others +Namespace: litmus +Service Account: litmus +Installation Mode: cluster + +------------------------------------- + +🀷 Do you want to continue with the above details? [Y/N]: Y + +πŸ’‘ Connecting agent to Litmus Portal. +πŸƒ Agents running!! +πŸš€ Agent Connection Successful!! πŸŽ‰ +πŸ‘‰ Litmus agents can be accessed here: http://172.17.0.2:31696/targets +``` + +--- + +## **Verify the new Agent Connection** + +To verify, if the connection process was successful you can view the list of connected agents from the Targets section on your ChaosCenter and ensure that the connected agent is in Active State. + +## Resources + +#### Videos + + + +## Learn More + +- [Learn More about Litmusctl](installation) +- [Install ChaosAgents in Namespace Scope](namespace-scope-installation) +- [Setup Endpoints and Access ChaosCenter without Ingress](../user-guides/setup-without-ingress.md) +- [Setup Endpoints and Access ChaosCenter with Ingress](../user-guides/setup-with-ingress.md) diff --git a/website/docs/litmusctl/installation.md b/website/docs/litmusctl/installation.md index 2aa2766..02a8674 100644 --- a/website/docs/litmusctl/installation.md +++ b/website/docs/litmusctl/installation.md @@ -1,7 +1,123 @@ --- id: installation -title: Installing Litmusctl +title: Litmusctl sidebar_label: Installation --- -## Coming soon +The Litmuschaos command-line tool, litmusctl, allows you to manage litmuschaos's agent plane. You can use litmusctl to create agents, project, and manage multiple litmuschaos accounts. + +## Prerequisites + +Litmusctl CLI requires the following things: + +- **kubeconfig** - litmusctl needs the kubeconfig of the k8s cluster where we need to connect litmus agents. The CLI currently uses the default path of kubeconfig i.e. `~/.kube/config`. +- **kubectl** - litmusctl is using kubectl under the hood to apply the manifest. +> To install kubectl, follow: [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) + +## Usage +For more information including a complete list of litmusctl operations, see the litmusctl reference documentation. +* For v0.3.0 or latest && compatible with Litmus-2.0.0-Beta9 or latest: Click here +* For v0.2.0 or earlier && compatible with Litmus-2.0.0-Beta8 or earlier: Click here + +## Installation + +To install the latest version of litmusctl follow the below steps: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Platformsv0.3.0v0.2.0 master(Unreleased)
    litmusctl-darwin-amd64 (MacOS)Click hereClick hereClick here
    litmusctl-linux-386Click hereClick hereClick here
    litmusctl-linux-amd64Click hereClick hereClick here
    litmusctl-linux-armClick hereClick hereClick here
    litmusctl-linux-arm64Click hereClick hereClick here
    litmusctl-windows-386Click hereClick hereClick here
    litmusctl-windows-arm64Click hereClick hereClick here
    litmusctl-windows-armClick hereClick hereClick here
    + +### Linux/MacOS + +* Extract the binary + +```shell +tar -zxvf litmusctl---.tar.gz +``` + +* Provide necessary permissions + +```shell +chmod +x litmusctl +``` + +* Move the litmusctl binary to /usr/local/bin/litmusctl. Note: Make sure to use root user or use sudo as a prefix + +```shell +mv litmusctl /usr/local/bin/litmusctl +``` + +* You can run the litmusctl command in Linux/macOS: + +```shell +litmusctl [options and parameters] +``` + +### Windows + +* Extract the binary from the zip using WinZip or any other extraction tool. + +* You can run the litmusctl command in windows: + +```shell +litmusctl.exe [options and parameters] +``` + +* To check the version of the litmusctl: + +```shell +litmusctl version +``` + +---- diff --git a/website/docs/litmusctl/namespace-scope-installation.md b/website/docs/litmusctl/namespace-scope-installation.md index ef7c553..b71f1d2 100644 --- a/website/docs/litmusctl/namespace-scope-installation.md +++ b/website/docs/litmusctl/namespace-scope-installation.md @@ -4,4 +4,132 @@ title: Installing Agent with Namespace Scope sidebar_label: Namespace Scope --- -## Coming soon +Multiple external [ChaosAgents](../getting-started/chaosagents.md) can be connected to application namespace/s with the help of the command line utility [litmusctl](installation). + +There can be one or more than one ChaosAgent in a cluster connected to different namespaces of the same cluster. + +The following steps will help you connect your ChaosAgents via litmusctl + +```bash +litmusctl agent connect +``` + +Next, you need to enter ChaosCenter details to login into your ChaosCenter account. Fields to be filled in: + +**ChaosCenter URL:** Enter the URL used to access the ChaosCenter. + +> Example, http://172.17.0.2:31696/ + +**Username:** Enter your LitmusPortal username.
    +**Password:** Enter your LitmusPortal password. + +```bash +πŸ”₯ Connecting LitmusChaos agent + +πŸ“Ά Please enter LitmusChaos details -- +πŸ‘‰ Host URL where litmus is installed: http://172.17.0.2:31696/ +πŸ€” Username [admin]: admin +πŸ™ˆ Password: +βœ… Login Successful! +``` + +Upon successful login, there will be a list of existing projects displayed on the terminal. Select the desired project by entering the sequence number indicated against it. + +```bash +✨ Projects List: +1. MyFirstProject +2. MySecondProject + +πŸ”Ž Select Project: 1 +``` + +Next, select the installation mode as Namespace by entering the sequence number indicated against it. There will be a prerequisites check to verify Role and RoleBinding post selection. + +```shell +πŸ”Œ Installation Modes: +1. Cluster +2. Namespace + +πŸ‘‰ Select Mode [cluster]: 2 + +πŸƒ Running prerequisites check.... +πŸ”‘ role - βœ… +πŸ”‘ rolebinding - βœ… + +🌟 Sufficient permissions. Connecting Agent +``` + +Next, enter the details of the new agent. + +Fields to be filled in
    + +| Platforms | Download Link | +| -------------------------- | -------------------------------------------------------------------------------------------------------- | +| **Agent Name:** | Enter the name for the new agent. | +| **Agent Description:** | Fill in details about the agent. | +| **Platform Name:** | Enter the platform name on which this agent is hosted. For example, AWS, GCP, Rancher etc. | +| **Enter the namespace:** | You can either enter an existing namespace (where your application is running) or create a new namespace | +| **Enter service account:** | Enter a name for your service account. | + +:::note +Since Namespaced Scope ChaosAgent don't have Cluster Wide Permission therefore if you are willing to install the ChaosAgent in new namespace, the namespace won't be automatically created + +If you install the Namespaced Scope ChaosAgent in the same namespace as ChaosCenter, since the subscriber is already present in the namespace, you will see this message `🚫 Subscriber already present. Please enter a different namespace` in such cases you have to create a new namespace in the cluster to install the ChaosAgent else choose the existing namespace where your application resides _(besides the ns where ChaosCenter is present)_ +::: + +```shell +πŸ”— Enter the details of the agent ---- +🀷 Agent Name: my-agent +πŸ“˜ Agent Description: This is a new namespace agent. +πŸ“¦ Platform List +1. AWS +2. GKE +3. Openshift +4. Rancher +5. Others +πŸ”Ž Select Platform [Others]: 5 +πŸ“ Enter the namespace (new or existing) [litmus]: litmus +πŸ”‘ Enter service account [litmus]: litmus +``` + +Once, all these steps are implemented you will be able to see a summary of all the entered fields. +After verification of these details, you can proceed with the connection of the agent by entering Y. The process of connection might take up to a few seconds. + +```shell +πŸ“Œ Summary -------------------------- + +Agent Name: my-agent +Agent Description: This is a new agent. +Platform Name: Others +Namespace: litmus +Service Account: litmus +Installation Mode: namespace + +------------------------------------- + +🀷 Do you want to continue with the above details? [Y/N]: Y + +πŸ’‘ Connecting agent to Litmus Portal. +πŸƒ Agents running!! +πŸš€ Agent Connection Successful!! πŸŽ‰ +πŸ‘‰ Litmus agents can be accessed here: http://172.17.0.2:31696/targets +``` + +--- + +## **Verify the new Agent Connection** + +To verify, if the connection process was successful you can view the list of connected agents from the Targets section on your ChaosCenter and ensure that the connected agent is in Active State. + +## Resources + +#### Videos + + + +## Learn More + +- [Learn More about Litmusctl](installation) +- [Install ChaosAgents in Cluster Scope](cluster-scope-installation) +- [Setup Endpoints and Access ChaosCenter without Ingress](../user-guides/setup-without-ingress.md) +- [Setup Endpoints and Access ChaosCenter with Ingress](../user-guides/setup-with-ingress.md) diff --git a/website/docs/user-guides/chaosagents-installation.md b/website/docs/user-guides/chaosagents-installation.md new file mode 100644 index 0000000..e4b399a --- /dev/null +++ b/website/docs/user-guides/chaosagents-installation.md @@ -0,0 +1,31 @@ +--- +id: chaosagents-installation +title: ChaosAgents Installation +sidebar_label: ChaosAgents +--- + +## Prerequisites + +- Before connecting a ChaosAgent to the [ChaosCenter](../getting-started/resources#chaoscenter.md), learn about what is a [ChaosAgent](../getting-started/resources#chaosagents.md) in Litmus. +- Make sure [litmusctl](../litmusctl/installation.md) is installed. + +## Connecting ChaosAgents + +* ### In Cluster Scope + + Learn to [connect ChaosAgents with Cluster Scope access using litmuctl](../litmusctl/cluster-scope-installation.md) + +* ### In Namespace Scope + + Learn to [connect ChaosAgents within a Namespace Scope access using litmuctl](../litmusctl/namespace-scope-installation.md) + +## Resources + + + +## Learn More + +- [Install ChaosCenter in Cluster Scope](chaoscenter-cluster-scope-installation) +- [Install ChaosCenter in Namespace Scope](chaoscenter-namespace-scope-installation) +- [Setup Endpoints and Access ChaosCenter without Ingress](setup-without-ingress) +- [Setup Endpoints and Access ChaosCenter with Ingress](setup-with-ingress) diff --git a/website/docs/getting-started/chaoscenter-cluster-scope-installation.md b/website/docs/user-guides/chaoscenter-cluster-scope-installation.md similarity index 72% rename from website/docs/getting-started/chaoscenter-cluster-scope-installation.md rename to website/docs/user-guides/chaoscenter-cluster-scope-installation.md index 846181f..0157346 100644 --- a/website/docs/getting-started/chaoscenter-cluster-scope-installation.md +++ b/website/docs/user-guides/chaoscenter-cluster-scope-installation.md @@ -8,7 +8,17 @@ sidebar_label: Cluster Scope ## Prerequisites -Before deploying LitmusChaos, make sure the [prerequisites](basic-requirements) are met. +Before deploying LitmusChaos, make sure the following items are there + +- Kubernetes 1.17 or later + +- A Persistent volume of 20GB + + :::note + Recommend to have a Persistent volume(PV) of 20GB, You can start with 1GB for test purposes as well. This PV is used as persistent storage to store the chaos config and chaos-metrics in the Portal. By default, litmus install would use the default storage class to allocate the PV. Provide this value + ::: + +- [Helm3](https://v3.helm.sh/) or [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) ## Installation @@ -34,7 +44,7 @@ helm repo list - The litmus infra components will be placed in this namespace. -> The ChaosCenter can be placed in any namespace +> The ChaosCenter can be placed in any namespace. ```bash kubectl create ns @@ -69,6 +79,8 @@ Visit https://docs.litmuschaos.io/docs/getstarted/ to find more info. #### **Create the namespace on which you want to install Litmus ChaosCenter** +> If you are installing Litmus in any other namespace apart from `litmus` namespace, make sure to change the same in the manifest too `https://litmuschaos.github.io/litmus/2.0.0-Beta/litmus-2.0.0-Beta.yaml`. + ```bash kubectl create ns ``` @@ -121,7 +133,7 @@ kubectl apply -f https://litmuschaos.github.io/litmus/2.0.0-Beta/litmus-2.0.0-Be #### **Verify Successful Registration of the Self Agent post [Account Configuration](setup-without-ingress)** -Once the project is created, the cluster is automatically registered as a chaos target via installation of [ChaosAgents](chaosagents). This is represented as [Self-Agent](chaosagents#types-of-chaosagents) in [ChaosCenter](chaoscenter). +Once the project is created, the cluster is automatically registered as a chaos target via installation of [ChaosAgents](../getting-started/resources#chaosagents.md). This is represented as [Self-Agent](../getting-started/resources#types-of-chaosagents.md) in [ChaosCenter](../getting-started/resources#chaoscenter.md). ```bash kubectl get pods -n litmus @@ -142,46 +154,8 @@ workflow-controller-78fc7b6c6-w82m7 1/1 Running 0 5m32s ## Resources -#### Videos - -#### Blogs - - - - - - - - - -
    - - -
    -
    - Getting Started with Litmus 2.0 in Google Kubernetes Engine -
    -     -     		- - -
    -
    - Getting Started with LitmusChaos 2.0 in Azure Kubernetes Service -
    -     -
    - - -
    -
    - Get Started with LitmusChaos in Minutes -
    -     -
    - ## Learn More - [Install ChaosCenter in Namespace Scope](chaoscenter-namespace-scope-installation) diff --git a/website/docs/getting-started/chaoscenter-namespace-scope-installation.md b/website/docs/user-guides/chaoscenter-namespace-scope-installation.md similarity index 82% rename from website/docs/getting-started/chaoscenter-namespace-scope-installation.md rename to website/docs/user-guides/chaoscenter-namespace-scope-installation.md index 43e076c..85cc1a9 100644 --- a/website/docs/getting-started/chaoscenter-namespace-scope-installation.md +++ b/website/docs/user-guides/chaoscenter-namespace-scope-installation.md @@ -8,7 +8,17 @@ sidebar_label: Namespace Scope ## Prerequisites -Before deploying LitmusChaos, make sure the [prerequisites](basic-requirements) are met. +Before deploying LitmusChaos, make sure the following items are there + +- Kubernetes 1.17 or later + +- A Persistent volume of 20GB + + :::note + Recommend to have a Persistent volume(PV) of 20GB, You can start with 1GB for test purposes as well. This PV is used as persistent storage to store the chaos config and chaos-metrics in the Portal. By default, litmus install would use the default storage class to allocate the PV. Provide this value + ::: + +- [Helm3](https://v3.helm.sh/) or [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) ## Installation @@ -194,7 +204,7 @@ service/mongo-service created #### **Verify Successful Registration of the Self Agent post [Account Configuration](setup-without-ingress)** -Once the project is created, the cluster is automatically registered as a chaos target via installation of [ChaosAgents](chaosagents). This is represented as [Self-Agent](chaosagents#types-of-chaosagents) in [ChaosCenter](chaoscenter). +Once the project is created, the cluster is automatically registered as a chaos target via installation of [ChaosAgents](../getting-started/resources#chaosagents.md). This is represented as [Self-Agent](../getting-started/resources#types-of-chaosagents.md) in [ChaosCenter](../getting-started/resources#chaosagents.md). ```bash kubectl get pods -n litmus @@ -215,46 +225,8 @@ workflow-controller-78fc7b6c6-w82m7 1/1 Running 0 5m32s ## Resources -#### Videos - -#### Blogs - - - - - - - - - -
    - - -
    -
    - Getting Started with Litmus 2.0 in Google Kubernetes Engine -
    -     -     		- - -
    -
    - Getting Started with LitmusChaos 2.0 in Azure Kubernetes Service -
    -     -
    - - -
    -
    - Get Started with LitmusChaos in Minutes -
    -     -
    - ## Learn More - [Install ChaosCenter in Cluster Scope](chaoscenter-cluster-scope-installation) diff --git a/website/docs/user-guides/introduction.md b/website/docs/user-guides/introduction.md deleted file mode 100644 index 18aa350..0000000 --- a/website/docs/user-guides/introduction.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -id: introduction -title: User Guides -sidebar_label: Introduction ---- - -## Coming soon diff --git a/website/docs/user-guides/overview.md b/website/docs/user-guides/overview.md new file mode 100644 index 0000000..c28659f --- /dev/null +++ b/website/docs/user-guides/overview.md @@ -0,0 +1,7 @@ +--- +id: overview +title: Overview +sidebar_label: Overview +--- + +## Coming soon diff --git a/website/docs/getting-started/setup-with-ingress.md b/website/docs/user-guides/setup-with-ingress.md similarity index 78% rename from website/docs/getting-started/setup-with-ingress.md rename to website/docs/user-guides/setup-with-ingress.md index ab83f49..3e37bc8 100644 --- a/website/docs/getting-started/setup-with-ingress.md +++ b/website/docs/user-guides/setup-with-ingress.md @@ -8,7 +8,7 @@ sidebar_label: Setup With Ingress ## Prerequisites -Before setting up endpoint with Ingress make sure the [Litmus ChaosCenter](chaoscenter) is installed in either one of these scopes +Before setting up endpoint with Ingress make sure the [Litmus ChaosCenter](../getting-started/resources#chaoscenter.md) is installed in either one of these scopes - [Cluster Scope](chaoscenter-cluster-scope-installation) - [Namespace Scope](chaoscenter-namespace-scope-installation) @@ -129,31 +129,6 @@ spec: kubectl apply -f -n ``` -## Resources - - - - - - -
    - - -
    -
    - AKS ingress with nginx and Key Vault certificates -
    -     -     		- - -
    -
    - Ingress -
    -     -
    - ## Learn More - [Setup Endpoints and Access ChaosCenter without Ingress](setup-without-ingress) diff --git a/website/docs/getting-started/setup-without-ingress.md b/website/docs/user-guides/setup-without-ingress.md similarity index 67% rename from website/docs/getting-started/setup-without-ingress.md rename to website/docs/user-guides/setup-without-ingress.md index 73bca92..68eda26 100644 --- a/website/docs/getting-started/setup-without-ingress.md +++ b/website/docs/user-guides/setup-without-ingress.md @@ -6,7 +6,7 @@ sidebar_label: Setup without Ingress ## Prerequisites -Before setting up endpoint with Ingress make sure the [Litmus ChaosCenter](chaoscenter) is installed in either one of these scopes +Before setting up endpoint with Ingress make sure the [Litmus ChaosCenter](../getting-started/resources#chaoscenter.md) is installed in either one of these scopes - [Cluster Scope](chaoscenter-cluster-scope-installation) - [Namespace Scope](chaoscenter-namespace-scope-installation) @@ -72,42 +72,6 @@ By default you are assigned with a default project with Owner permissions. -## Resources - - - - - - - - - -
    - - -
    -
    - NodePort -
    -     -     		- - -
    -
    - LoadBalancer -
    -     -
    - - -
    -
    - Ingress -
    -     -
    - ## Learn More - [Setup Endpoints and Access ChaosCenter with Ingress](setup-with-ingress) diff --git a/website/docusaurus.config.js b/website/docusaurus.config.js index 5c254f3..cf61d37 100644 --- a/website/docusaurus.config.js +++ b/website/docusaurus.config.js @@ -42,7 +42,7 @@ module.exports = { tagline: 'A website for testing', url: 'https://litmusdocs.netlify.app', baseUrl: '/', - onBrokenLinks: 'throw', + onBrokenLinks: 'warn', favicon: 'img/favicon.ico', organizationName: 'litmuschaos', projectName: 'litmus', diff --git a/website/sidebars.js b/website/sidebars.js index 1c48957..ce2eb75 100644 --- a/website/sidebars.js +++ b/website/sidebars.js @@ -15,41 +15,16 @@ module.exports = { // Getting Started { 'Getting Started': [ - { - Prerequisites: [ - 'getting-started/basic-requirements', - { - Resources: ['getting-started/chaoscenter', 'getting-started/chaosagents'] - } - ] - }, - { - Installation: [ - { - ChaosCenter: [ - 'getting-started/chaoscenter-cluster-scope-installation', - 'getting-started/chaoscenter-namespace-scope-installation', - 'getting-started/setup-without-ingress', - 'getting-started/setup-with-ingress' - ] - }, - { - ChaosAgents: [ - 'getting-started/chaosagents-cluster-scope-installation', - 'getting-started/chaosagents-namespace-scope-installation' - ] - } - ] - }, - 'getting-started/run-your-first-workflow', - 'getting-started/learning-litmus' + 'getting-started/resources', + 'getting-started/installation', + 'getting-started/run-your-first-workflow' ] }, // Concepts { Concepts: [ - 'concepts/introduction', + 'concepts/overview', 'concepts/litmus', 'concepts/experiment', 'concepts/probes', @@ -74,7 +49,20 @@ module.exports = { // User Guides { 'User Guides': [ - 'user-guides/introduction', + 'user-guides/overview', + { + 'Advance Installation': [ + { + ChaosCenter: [ + 'user-guides/chaoscenter-cluster-scope-installation', + 'user-guides/chaoscenter-namespace-scope-installation', + 'user-guides/setup-without-ingress', + 'user-guides/setup-with-ingress' + ] + }, + 'user-guides/chaosagents-installation', + ] + }, { 'Running Litmus': ['user-guides/air-gapped'] },