Updated Litmus Installation + Wordlist

Signed-off-by: Sayan Mondal <sayan@chaosnative.com>

.wordlist.txt

@@ -159,6 +159,7 @@ cp
 cpu
 Cpu
 cr
+CronWorkflow
 CrashLoopBackOff
 crd
 CRD
@@ -224,6 +225,7 @@ ENVs
 EoT
 EOT
 errored
+else's
 et
 eth
 ethernet
@@ -400,6 +402,9 @@ msg
 MustRunAs
 mv
 myhtop
+MyHub
+MyHubs
+myhub
 mysql
 namespace
 namespaced
@@ -510,6 +515,7 @@ ResourceRequirements
 responseCode
 restorecon
 rlt
+rightarrow
 RMW
 RoleBinding
 roleRef
@@ -639,6 +645,7 @@ VMware
 volumeMount
 WithError
 WebUI
+weightage
 wordpress
 workDays
 workHours

website/docs/litmus-installation.md

@@ -29,11 +29,29 @@ The helm chart will install all the CRDs, required service account configuration
 helm install chaos litmuschaos/litmus-2.0 --namespace litmus
 ```
 
+<span style={{color: 'green'}}><b>Expected Output</b></span>
+
+```
+NAME: chaos
+LAST DEPLOYED: Mon Mar 15 18:27:42 2021
+NAMESPACE: litmus
+STATUS: deployed
+REVISION: 1
+TEST SUITE: None
+NOTES:
+Thank you for installing litmus-portal 😀
+
+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.
 
 ### **Verify your installation**
 
-**Verify if the Chaos Operator is running**
+**Verify if the Frontend, Backend and Database Pods are running**
 
 ```bash
 kubectl get pods -n litmus
@@ -41,10 +59,11 @@ kubectl get pods -n litmus
 
 <span style={{color: 'green'}}><b>Expected Output</b></span>
 
-<div style={{background: '#F5F5F5', padding: '1rem'}}>
+```bash
-
+chaos-litmus-portal-frontend-ff8b554dc-q5rl4   1/1     Running   0          2m6s
-chaos-operator-ce-554d6c8f9f-slc8k  1/1   Running   0   6m41s
+chaos-litmus-portal-mongo-6764cfdd59-c9r56     1/1     Running   0          2m6s
-</div>
+chaos-litmus-portal-server-5ffbccbfff-dknv8    2/2     Running   0          2m6s
+```
 
 <br />
 
@@ -56,14 +75,11 @@ kubectl get crds | grep chaos
 
 <span style={{color: 'green'}}><b>Expected Output</b></span>
 
-<div style={{background: '#F5F5F5', padding: '1rem'}}>
+```bash
-chaosengines.litmuschaos.io 2019-10-02T08:45:25Z
+chaosengines.litmuschaos.io            2021-03-15T12:57:27Z
-<br />
+chaosexperiments.litmuschaos.io        2021-03-15T12:57:27Z
-chaosexperiments.litmuschaos.io 2019-10-02T08:45:26Z
+chaosresults.litmuschaos.io            2021-03-15T12:57:27Z
-<br />
+```
-chaosresults.litmuschaos.io 2019-10-02T08:45:26Z
-<br />
-</div>
 
 <br />
 
@@ -75,11 +91,47 @@ kubectl api-resources | grep chaos
 
 <span style={{color: 'green'}}><b>Expected Output</b></span>
 
-<div style={{background: '#F5F5F5', padding: '1rem'}}>
+```bash
 chaosengines                   litmuschaos.io          true         ChaosEngine
-<br />
 chaosexperiments               litmuschaos.io          true         ChaosExperiment
-<br />
 chaosresults                   litmuschaos.io          true         ChaosResult
-<br />
+```
-</div>
+
+### **Setup the Portal**
+
+To setup and login to Litmus Portal expand the available services just created and copy the `PORT` of the `litmusportal-frontend-service` service
+
+```bash
+kubectl get svc -n litmus
+```
+
+<span style={{color: 'green'}}><b>Expected Output</b></span>
+
+```bash
+NAME                            TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                         AGE
+chaos-litmus-portal-mongo       ClusterIP   10.104.107.117   <none>        27017/TCP                       2m
+litmusportal-frontend-service   NodePort    10.101.81.70     <none>        9091:30385/TCP                  2m
+litmusportal-server-service     NodePort    10.108.151.79    <none>        9002:32456/TCP,9003:31160/TCP   2m
+```
+
+> **Note**: In this case the PORT for `litmusportal-frontend-service` is `30385`. Yours will be different.
+
+### **Accessing the Portal**
+
+Once you have the PORT copied in your clipboard, simply use your NodeIP and PORT in this manner `<NodeIP>:<PORT>` to access the portal.
+
+For example:
+
+```yaml
+http://172.17.0.3:30385/
+```
+> Where `172.17.0.3` is my NodeIP and `30385` is the frontend service PORT. You can also use a LoadBalancer if not NodePort, the only change would be to provide a `<LoadBalancerIP>:<PORT>`
+
+You should be able to see the Login Page of Litmus. The **default credentials** are
+
+```yaml
+Username: admin
+Password: litmus
+```
+
+![Login](https://i.ibb.co/x7jzYDz/Login.png)