Chore(actions): Update GitHub Chaos Actions Name (litmuschaos#18)

Signed-off-by: udit <[email protected]>

Co-authored-by: udit <[email protected]>

Dockerfile

@@ -1,8 +1,8 @@
 FROM golang:latest
 
 LABEL name="Kubernetes Chaos"
-LABEL repository="http://github.com/mayadata-io/github-chaos-actions"
-LABEL homepage="http://github.com/mayadata-io/github-chaos-actions"
+LABEL repository="http://github.com/litmuschaos/github-chaos-actions"
+LABEL homepage="http://github.com/litmuschaos/github-chaos-actions"
 
 LABEL maintainer="LitmusChaos"
 LABEL com.github.actions.name="Kubernetes Chaos"

experiments/container-kill/README.md

@@ -1,6 +1,6 @@
 # Container Kill Experiment
 
-This experiment executes SIGKILL on container of random replicas of an application deployment. It tests the deployment sanity (replica availability & uninterrupted service) and recovery workflows of an application. Check <a href="https://docs.litmuschaos.io/docs/container-kill/">container kill docs</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/mayadata-io/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
+This experiment executes SIGKILL on container of random replicas of an application deployment. It tests the deployment sanity (replica availability & uninterrupted service) and recovery workflows of an application. Check <a href="https://docs.litmuschaos.io/docs/container-kill/">container kill docs</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/litmuschaos/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
 
 #### Sample workflow 
 
@@ -22,7 +22,7 @@ jobs:
     runs-on: ubuntu-latest
 
     - name: Running container kill chaos experiment
-      uses: mayadata-io/[email protected]
+      uses: litmuschaos/[email protected]
       env:
         KUBE_CONFIG_DATA: ${{ secrets.KUBE_CONFIG_DATA }}
         ##If litmus is not installed

experiments/disk-fill/README.md

@@ -1,6 +1,6 @@
 # Disk Fill Experiment
 
-This chaos action causes Disk Stress by filling up the Ephemeral Storage of the Pod using one of it containers. It forced the Pod to get Evicted if the Pod exceeds it Ephemeral Storage Limit.It tests the Ephemeral Storage Limits, to ensure those parameters are sufficient. Check <a href="https://docs.litmuschaos.io/docs/disk-fill/">disk fill docs</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/mayadata-io/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
+This chaos action causes Disk Stress by filling up the Ephemeral Storage of the Pod using one of it containers. It forced the Pod to get Evicted if the Pod exceeds it Ephemeral Storage Limit.It tests the Ephemeral Storage Limits, to ensure those parameters are sufficient. Check <a href="https://docs.litmuschaos.io/docs/disk-fill/">disk fill docs</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/litmuschaos/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
 
 **NOTE**: Appropriate Ephemeral Storage Requests and Limits should be set for the application before running the chaos action. 
 
@@ -24,7 +24,7 @@ jobs:
     runs-on: ubuntu-latest
 
     - name: Running disk-fill chaos experiment
-      uses: mayadata-io/[email protected]
+      uses: litmuschaos/[email protected]
       env:
         KUBE_CONFIG_DATA: ${{ secrets.KUBE_CONFIG_DATA }}
         ##If litmus is not installed

experiments/node-cpu-hog/README.md

@@ -1,6 +1,6 @@
 # Node CPU Hog Experiment
 
-This experiment causes CPU resource exhaustion on the Kubernetes node. The experiment aims to verify the resiliency of applications whose replicas may be evicted on account on nodes turning unschedulable (Not Ready) due to lack of CPU resources. Check <a href="https://docs.litmuschaos.io/docs/node-cpu-hog/">node cpu hog docs</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/mayadata-io/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
+This experiment causes CPU resource exhaustion on the Kubernetes node. The experiment aims to verify the resiliency of applications whose replicas may be evicted on account on nodes turning unschedulable (Not Ready) due to lack of CPU resources. Check <a href="https://docs.litmuschaos.io/docs/node-cpu-hog/">node cpu hog docs</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/litmuschaos/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
 
 #### Sample workflow 
 
@@ -21,7 +21,7 @@ jobs:
     runs-on: ubuntu-latest
 
     - name: Running node-cpu-hog chaos experiment
-      uses: mayadata-io/[email protected]
+      uses: litmuschaos/[email protected]
       env:
         KUBE_CONFIG_DATA: ${{ secrets.KUBE_CONFIG_DATA }}
         ##If litmus is not installed

experiments/node-io-stress/README.md

@@ -1,7 +1,7 @@
 # Node IO Stress Experiment
 
 This experiment causes IO stress on the Kubernetes node. The experiment aims to verify the resiliency of applications that share this disk resource for ephemeral or persistent storage purposes.
-. Check <a href="https://docs.litmuschaos.io/docs/node-io-stress/">node io stress docs</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/mayadata-io/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
+. Check <a href="https://docs.litmuschaos.io/docs/node-io-stress/">node io stress docs</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/litmuschaos/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
 
 #### Sample workflow 
 
@@ -20,7 +20,7 @@ jobs:
     runs-on: ubuntu-latest
 
     - name: Running node-io-stress chaos experiment
-      uses: mayadata-io/[email protected]
+      uses: litmuschaos/[email protected]
       env:
         KUBE_CONFIG_DATA: ${{ secrets.KUBE_CONFIG_DATA }}
         ##if litmus is not installed

experiments/node-memory-hog/README.md

@@ -1,6 +1,6 @@
 # Node Memory Hog Experiment
 
-This experiment causes Memory exhaustion on the Kubernetes node. The experiment aims to verify the resiliency of applications whose replicas may be evicted on account on nodes turning unschedulable due to lack of Memory resources. Check <a href="https://docs.litmuschaos.io/docs/node-memory-hog/">node memory hog docs</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/mayadata-io/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
+This experiment causes Memory exhaustion on the Kubernetes node. The experiment aims to verify the resiliency of applications whose replicas may be evicted on account on nodes turning unschedulable due to lack of Memory resources. Check <a href="https://docs.litmuschaos.io/docs/node-memory-hog/">node memory hog docs</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/litmuschaos/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
 
 #### Sample workflow 
 
@@ -21,7 +21,7 @@ jobs:
     runs-on: ubuntu-latest
 
     - name: Running node-memory-hog chaos experiment
-      uses: mayadata-io/[email protected]
+      uses: litmuschaos/[email protected]
       env:
         KUBE_CONFIG_DATA: ${{ secrets.KUBE_CONFIG_DATA }}
         ##if litmus is not installed

experiments/pod-autoscaler/README.md

@@ -1,6 +1,6 @@
 # Pod Autoscaler Experiment
 
-This experiment Scale the application replicas and test the node autoscaling on cluster. Check <a href="https://docs.litmuschaos.io/docs/pod-autoscaler/">pod scaler docs</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/mayadata-io/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
+This experiment Scale the application replicas and test the node autoscaling on cluster. Check <a href="https://docs.litmuschaos.io/docs/pod-autoscaler/">pod scaler docs</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/litmuschaos/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
 
 #### Sample workflow 
 
@@ -19,7 +19,7 @@ jobs:
     runs-on: ubuntu-latest
 
     - name: Running pod autoscaler chaos experiment
-      uses: mayadata-io/[email protected]
+      uses: litmuschaos/[email protected]
       env:
         KUBE_CONFIG_DATA: ${{ secrets.KUBE_CONFIG_DATA }}
         ##If litmus is not installed

experiments/pod-cpu-hog/README.md

@@ -1,6 +1,6 @@
 # Pod CPU Hog Experiment
 
-This experiment causes CPU resource consumption on specified application containers by starting one or more md5sum calculation process on the special file /dev/zero. It Can test the application's resilience to potential slowness/unavailability of some replicas due to high CPU load. Check <a href="https://docs.litmuschaos.io/docs/pod-cpu-hog/">pod cpu hog docs</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/mayadata-io/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
+This experiment causes CPU resource consumption on specified application containers by starting one or more md5sum calculation process on the special file /dev/zero. It Can test the application's resilience to potential slowness/unavailability of some replicas due to high CPU load. Check <a href="https://docs.litmuschaos.io/docs/pod-cpu-hog/">pod cpu hog docs</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/litmuschaos/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
 
 #### Sample workflow 
 
@@ -21,7 +21,7 @@ jobs:
     runs-on: ubuntu-latest
 
     - name: Running pod-cpu-hog chaos experiment
-      uses: mayadata-io/[email protected]
+      uses: litmuschaos/[email protected]
       env:
         KUBE_CONFIG_DATA: ${{ secrets.KUBE_CONFIG_DATA }}
         ##If litmus is not installed

experiments/pod-delete/README.md

@@ -1,6 +1,6 @@
 # Pod Delete Experiment
 
-This experiment causes (forced/graceful) pod failure of random replicas of an application deployment. It tests deployment sanity (replica availability & uninterrupted service) and recovery workflows of the application pod. Check <a href="https://docs.litmuschaos.io/docs/pod-delete/">pod delete docs</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/mayadata-io/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
+This experiment causes (forced/graceful) pod failure of random replicas of an application deployment. It tests deployment sanity (replica availability & uninterrupted service) and recovery workflows of the application pod. Check <a href="https://docs.litmuschaos.io/docs/pod-delete/">pod delete docs</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/litmuschaos/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
 
 #### Sample workflow 
 
@@ -21,7 +21,7 @@ jobs:
     runs-on: ubuntu-latest
 
     - name: Running pod delete chaos experiment
-      uses: mayadata-io/[email protected]
+      uses: litmuschaos/[email protected]
       env:
         KUBE_CONFIG_DATA: ${{ secrets.KUBE_CONFIG_DATA }}
         ##If litmus is not installed

experiments/pod-memory-hog/README.md

@@ -1,6 +1,6 @@
 # Pod Memory Hog Experiment
 
-This experiment causes Memory resource consumption on specified application containers by using dd command which will used to consume memory of the application container for certain duration of time. It can test the application's resilience to potential slowness/unavailability of some replicas due to high Memory load. Check <a href="https://docs.litmuschaos.io/docs/pod-memory-hog/">node memory hog docs</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/mayadata-io/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
+This experiment causes Memory resource consumption on specified application containers by using dd command which will used to consume memory of the application container for certain duration of time. It can test the application's resilience to potential slowness/unavailability of some replicas due to high Memory load. Check <a href="https://docs.litmuschaos.io/docs/pod-memory-hog/">node memory hog docs</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/litmuschaos/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
 
 #### Sample workflow 
 
@@ -21,7 +21,7 @@ jobs:
     runs-on: ubuntu-latest
 
     - name: Running pod-memory-hog chaos experiment
-      uses: mayadata-io/[email protected]
+      uses: litmuschaos/[email protected]
       env:
         KUBE_CONFIG_DATA: ${{ secrets.KUBE_CONFIG_DATA }}
         ##If litmus is not installed

experiments/pod-network-corruption/README.md

@@ -1,6 +1,6 @@
 # Pod Network Corruption Experiment
 
-This chaos action Injects packet corruption on the specified container by starting a traffic control (tc) process with netem rules to add egress packet corruption. Corruption is injected via pumba library with command pumba netem corruption by passing the relevant network interface, packet-corruption-percentage, chaos duration and regex filter for container name. Check <a href="https://docs.litmuschaos.io/docs/pod-network-corruption/">pod network corruption docs</a> for more info.To know more and get started with chaos-actions visit <a href="https://github.com/mayadata-io/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
+This chaos action Injects packet corruption on the specified container by starting a traffic control (tc) process with netem rules to add egress packet corruption. Corruption is injected via pumba library with command pumba netem corruption by passing the relevant network interface, packet-corruption-percentage, chaos duration and regex filter for container name. Check <a href="https://docs.litmuschaos.io/docs/pod-network-corruption/">pod network corruption docs</a> for more info.To know more and get started with chaos-actions visit <a href="https://github.com/litmuschaos/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
 
 #### Sample workflow 
 
@@ -21,7 +21,7 @@ jobs:
     runs-on: ubuntu-latest
 
     - name: Running pod network corruption chaos experiment
-      uses: mayadata-io/[email protected]
+      uses: litmuschaos/[email protected]
       env:
         KUBE_CONFIG_DATA: ${{ secrets.KUBE_CONFIG_DATA }}
         ##If litmus is not installed

experiments/pod-network-duplication/README.md

@@ -1,6 +1,6 @@
 # Pod Network Duplication Experiment
 
-This chaos action Injects packet dupication on the specified container by starting a traffic control (tc) process with netem rules to add disrupt network connectivity to kubernetes pods. Check <a href="https://docs.litmuschaos.io/docs/pod-network-duplication/">pod network duplication docs</a> for more info.To know more and get started with chaos-actions visit <a href="https://github.com/mayadata-io/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
+This chaos action Injects packet dupication on the specified container by starting a traffic control (tc) process with netem rules to add disrupt network connectivity to kubernetes pods. Check <a href="https://docs.litmuschaos.io/docs/pod-network-duplication/">pod network duplication docs</a> for more info.To know more and get started with chaos-actions visit <a href="https://github.com/litmuschaos/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
 
 #### Sample workflow 
 
@@ -19,7 +19,7 @@ jobs:
     runs-on: ubuntu-latest
 
     - name: Running pod network duplication chaos experiment
-      uses: mayadata-io/[email protected]
+      uses: litmuschaos/[email protected]
       env:
         KUBE_CONFIG_DATA: ${{ secrets.KUBE_CONFIG_DATA }}
         ##If litmus is not installed

experiments/pod-network-latency/README.md

@@ -1,6 +1,6 @@
 # Pod Network Latency Experiment
 
-This experiment causes flaky access to application replica by injecting network delay using pumba. It injects latency on the specified container by starting a traffic control (tc) process with netem rules to add egress delays. It Can test the application's resilience to lossy/flaky network. Check <a href="https://docs.litmuschaos.io/docs/pod-network-latency/">pod network latency</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/mayadata-io/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
+This experiment causes flaky access to application replica by injecting network delay using pumba. It injects latency on the specified container by starting a traffic control (tc) process with netem rules to add egress delays. It Can test the application's resilience to lossy/flaky network. Check <a href="https://docs.litmuschaos.io/docs/pod-network-latency/">pod network latency</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/litmuschaos/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
 
 #### Sample workflow 
 
@@ -21,7 +21,7 @@ jobs:
     runs-on: ubuntu-latest
 
     - name: Running pod-network-latency chaos experiment
-      uses: mayadata-io/[email protected]
+      uses: litmuschaos/[email protected]
       env:
         KUBE_CONFIG_DATA: ${{ secrets.KUBE_CONFIG_DATA }}
         #If litmus is not installed

experiments/pod-network-loss/README.md

@@ -1,6 +1,6 @@
 # Pod Network Loss Experiment
 
-This experiment injects chaos to disrupt network connectivity to kubernetes pods.The application pod should be healthy once chaos is stopped. It causes loss of access to application replica by injecting packet loss using pumba. Check <a href="https://docs.litmuschaos.io/docs/pod-network-loss/">pod network loss</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/mayadata-io/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
+This experiment injects chaos to disrupt network connectivity to kubernetes pods.The application pod should be healthy once chaos is stopped. It causes loss of access to application replica by injecting packet loss using pumba. Check <a href="https://docs.litmuschaos.io/docs/pod-network-loss/">pod network loss</a> for more info. To know more and get started with chaos-actions visit <a href="https://github.com/litmuschaos/github-chaos-actions/blob/master/README.md">github-chaos-actions</a>. 
 
 #### Sample workflow 
 
@@ -21,7 +21,7 @@ jobs:
     runs-on: ubuntu-latest
 
     - name: Running pod-network-loss chaos experiment
-      uses: mayadata-io/[email protected]
+      uses: litmuschaos/[email protected]
       env:
         KUBE_CONFIG_DATA: ${{ secrets.KUBE_CONFIG_DATA }}
         ##If litmus is not installed