litmuschaos
/
litmus-docs
mirror of https://github.com/litmuschaos/litmus-docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
litmus-docs/website/docs/getting-started-cluster-sco...

5.4 KiB
Raw Blame History

id title sidebar_label
cluster-scope-installation Litmus Cluster Scope Installation Cluster Scope

Prerequisites

Before deploying LitmusChaos, make sure the prerequisites are met.

Installation

Installation of Litmus can be done using either of the below methods

Install Litmus using Helm

The helm chart will install all the required service account configuration and chaos control plane.

The following steps will help you install litmus via helm.

Step-1: Add the litmus helm repository

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

  • The litmus infra components will be placed in this namespace.

The chaos control plane can be placed in any namespace, in this case we are using litmus as the namespace of our choice.

kubectl create ns <LITMUS_PORTAL_NAMESPACE>

Step-3: Install the litmus chaos control plane

helm install chaos litmuschaos/litmus-2-0-0-beta --namespace=<LITMUS_PORTAL_NAMESPACE> --devel

<span style={{color: 'green'}}>Expected Output

NAME: chaos
LAST DEPLOYED: Tue Jun 15 19:20:09 2021
NAMESPACE: <LITMUS_PORTAL_NAMESPACE>
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

kubectl create ns <LITMUS_PORTAL_NAMESPACE>

Install Litmus

Applying the manifest file will install all the required service account configuration and chaos control plane.

kubectl apply -f https://litmuschaos.github.io/litmus/2.0.0-Beta/litmus-2.0.0-Beta.yaml -n <LITMUS_PORTAL_NAMESPACE>

Verify your installation

Verify if the frontend, server, and database pods are running

  • Check the pods in the namespace where you installed Litmus:

    kubectl get pods -n <LITMUS_PORTAL_NAMESPACE>

    <span style={{color: 'green'}}>Expected Output

    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:

    kubectl get svc -n <LITMUS_PORTAL_NAMESPACE>

    <span style={{color: 'green'}}>Expected Output

    NAME                            TYPE        CLUSTER-IP      EXTERNAL-IP PORT(S)                       AGE
litmusportal-frontend-service   NodePort    10.100.105.154  <none>      9091:30229/TCP                7m14s
litmusportal-server-service     NodePort    10.100.150.175  <none>      9002:30479/TCP,9003:31949/TCP 7m8s
mongo-service                   ClusterIP   10.100.226.179  <none>      27017/TCP                     7m6s

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