adding minimal keywords for searching in chaoshub (#502)

* adding minimal keywords for searching on chaoshub

Signed-off-by: shubham chaudhary <shubham@chaosnative.com>

* adding k8s keywords

Signed-off-by: shubham chaudhary <shubham@chaosnative.com>

charts/aws-ssm/aws-ssm-chaos-by-id/aws-ssm-chaos-by-id.chartserviceversion.yaml

@@ -15,11 +15,9 @@ spec:
     - Causes chaos on AWS ec2 instances with given instance ID(s) using SSM docs for total chaos duration with the specified chaos interval.
     - Tests deployment sanity (replica availability & uninterrupted service) and recovery workflows of the target application pod(if provided).
   keywords:
-    - Kubernetes
     - SSM
     - AWS
-    - Document
-    - Run Command
+    - EC2
   platforms:
     - AWS
   maturity: alpha

charts/aws-ssm/aws-ssm-chaos-by-tag/aws-ssm-chaos-by-tag.chartserviceversion.yaml

@@ -15,11 +15,9 @@ spec:
     - Causes chaos on AWS ec2 instances with given instance tag using SSM docs for total chaos duration with the specified chaos interval.
     - Tests deployment sanity (replica availability & uninterrupted service) and recovery workflows of the target application pod(if provided).
   keywords:
-    - Kubernetes
     - SSM
     - AWS
-    - Document
-    - Run Command
+    - EC2
   platforms:
     - AWS
   maturity: alpha

charts/azure/azure-disk-loss/azure-disk-loss.chartserviceversion.yaml

@@ -13,9 +13,7 @@ spec:
     This experiment causes the detachment of the disk from the VM for a certain chaos duration
     - Causes detachment of the disk from the VM and then reattachment of the disk to the VM
     - It helps to check the performance of the application on the instance. 
-    
   keywords: 
-    - Kubernetes
     - Azure
     - Disk
     - AKS

charts/azure/azure-instance-stop/azure-instance-stop.chartserviceversion.yaml

@@ -15,9 +15,8 @@ spec:
     - Causes termination of an azure instance before bringing it back to running state after the specified chaos duration.
     - It helps to check the performance of the application on the instance. 
   keywords:
-    - Kubernetes
     - Azure
-    - Termination
+    - Scaleset
     - AKS
   platforms:
     - Azure

charts/azure/azure.chartserviceversion.yaml

@@ -17,7 +17,8 @@ spec:
   keywords:
     - Azure
     - Instance
-    - State  
+    - AKS
+    - Scaleset
   maintainers:
     - name: Udit Gaurav
       email: udit.gaurav@mayadata.io

charts/cassandra/cassandra-pod-delete/cassandra-pod-delete.chartserviceversion.yaml

@@ -15,6 +15,7 @@ spec:
     It tests statefulset sanity (replica availability & uninterrupted service) and recovery workflows of the cassandra pod
   keywords:
     - Kubernetes
+    - K8S
     - Cassandra
     - Pod
   platforms:

charts/cassandra/cassandra.chartserviceversion.yaml

@@ -17,9 +17,9 @@ spec:
     - cassandra-pod-delete
   keywords:
     - Kubernetes
+    - K8S
     - Pod
     - Cassandra
-    - Statefulset
   maintainers:
     - name: ksatchit
       email: karthik.s@mayadata.io

charts/coredns/coredns-pod-delete/coredns-pod-delete.chartserviceversion.yaml

@@ -16,8 +16,10 @@ spec:
     - Tests of successful resolution of app services during chaos injection
   keywords:
     - Kubernetes
+    - K8S
     - CoreDNS
-    - Pod delete 
+    - DNS
+    - Pod
   platforms:
     - GKE
     - Minikube

charts/coredns/coredns.chartserviceversion.yaml

@@ -12,15 +12,13 @@ spec:
   categoryDescription: >
     CoreDNS is an open-source system for DNS management of containerized applications.
     It helps to resolve services to IP address. It will install all the experiments which can be used to inject chaos into containerized applications.
-
   experiments:
     - coredns-pod-delete
-
   keywords:
     - Kubernetes
-    - Container
-    - node
-    - pod
+    - K8S
+    - Pod
+    - CoreDNS
     - DNS
   maintainers:
     - name: Raj Babu Das

charts/gcp/gcp-vm-disk-loss/gcp-vm-disk-loss.chartserviceversion.yaml

@@ -10,9 +10,8 @@ spec:
   categoryDescription: >
     Causes loss of a non-boot storage persistent disk from a GCP VM instance for a specified duration of time 
   keywords: 
-    - "persistent-disks" 
-    - "kubernetes" 
-    - "gcp" 
+    - "Disk" 
+    - "GCP" 
   platforms: 
     - "GCP"
   maturity: alpha

charts/gcp/gcp-vm-instance-stop/gcp-vm-instance-stop.chartserviceversion.yaml

@@ -10,9 +10,8 @@ spec:
   categoryDescription: >
     Stops GCP VM instances and GKE nodes for a specified duration of time and later restarts them 
   keywords: 
-    - "vm-instances" 
-    - "kubernetes" 
-    - "gcp" 
+    - "VM" 
+    - "GCP" 
   platforms: 
     - "GCP"
   maturity: alpha

charts/gcp/gcp.chartserviceversion.yaml

@@ -13,10 +13,9 @@ spec:
   - gcp-vm-instance-stop
   - gcp-vm-disk-loss
   keywords: 
-    - "pods" 
-    - "kubernetes" 
-    - "disk"
-    - "gcp"
+    - "VM"
+    - "Disk"
+    - "GCP"
   maintainers: 
     - name: neelanjan00 
       email: neelanjan@chaosnative.com

charts/generic/byoc-pod-delete/byoc-pod-delete.chartserviceversion.yaml

@@ -13,8 +13,10 @@ spec:
   categoryDescription: |
     Byoc Pod delete contains chaos to disrupt state of kubernetes resources. It uses chaostoolkit to inject random pod delete failures against specified applications
   keywords:
+    - BYOC
+    - K8S
     - Kubernetes
-    - State
+    - Pod
   platforms:
      - Minikube
   maturity: alpha

charts/generic/container-kill/container-kill.chartserviceversion.yaml

@@ -16,6 +16,8 @@ spec:
     - Tests deployment sanity (replica availability & uninterrupted service) and recovery workflows of the application pod.
   keywords:
     - Kubernetes
+    - K8S
+    - Pod
     - Container 
   platforms:
     - GKE

charts/generic/disk-fill/disk-fill.chartserviceversion.yaml

@@ -17,8 +17,9 @@ spec:
     - Tests the Ephemeral Storage Limits, to ensure those parameters are sufficient.
   keywords:
     - Kubernetes
+    - K8S
+    - Pod
     - Disk
-    - State 
   platforms:
     - GKE
     - EKS

charts/generic/docker-service-kill/docker-service-kill.chartserviceversion.yaml

@@ -16,6 +16,7 @@ spec:
     - The application node should be healthy once chaos is stopped and the services are reaccessable. 
   keywords:
     - Kubernetes
+    - K8S
     - Node
     - Service
     - Docker 

charts/generic/generic.chartserviceversion.yaml

@@ -38,9 +38,9 @@ spec:
     - pod-dns-spoof
     - pod-cpu-hog-exec
     - pod-memory-hog-exec
-
   keywords:
     - Kubernetes
+    - K8S
     - Container
     - Node
     - Pod
@@ -50,8 +50,10 @@ spec:
     - Network
     - CPU
     - Memory
+    - Stress
     - Service
     - DNS
+    - Scale
   maintainers:
     - name: ksatchit
       email: karthik.s@mayadata.io

charts/generic/kubelet-service-kill/kubelet-service-kill.chartserviceversion.yaml

@@ -17,6 +17,7 @@ spec:
     
   keywords:
     - Kubernetes
+    - K8S
     - Kubelet
     - Node
     - Service

charts/generic/node-cpu-hog/node-cpu-hog.chartserviceversion.yaml

@@ -16,8 +16,8 @@ spec:
     - After test, the recovery should be manual for the application pod and node in case they are not in an appropriate state.
   keywords:
     - Kubernetes
+    - K8S
     - CPU
-    - State
     - Node
   platforms:
     - GKE

charts/generic/node-drain/node-drain.chartserviceversion.yaml

@@ -15,8 +15,9 @@ spec:
     Drain the node where application pod is scheduled
   keywords:
     - Kubernetes
+    - K8S
     - Node 
-    - State
+    - Drain
   platforms:
     - GKE
     - AWS(KOPS)

charts/generic/node-io-stress/node-io-stress.chartserviceversion.yaml

@@ -16,10 +16,10 @@ spec:
     - The amount of disk stress can be either specifed as the size in percentage of the total free space on the file system or simply in Gigabytes(GB)
   keywords:
     - Kubernetes
+    - K8S
     - Disk
     - IO
     - Filesystem
-    - State 
     - Node
   platforms:
     - GKE

charts/generic/node-memory-hog/node-memory-hog.chartserviceversion.yaml

@@ -16,8 +16,8 @@ spec:
     - After the test, the recovery should be manual for the application pod and node in case they are not in an appropriate state. 
   keywords:
     - Kubernetes
+    - K8S
     - Memory
-    - State 
     - Node
   platforms:
     - GKE

charts/generic/node-poweroff/node-poweroff.chartserviceversion.yaml

@@ -14,12 +14,12 @@ spec:
     Node poweroff contains chaos experiment to poweroff a node via SSH.
   keywords:
     - Kubernetes
+    - K8S
     - Poweroff
-    - State
     - Node
-    - SSH
   platforms:
     - KVM/LibVirt based K8s
+    - EKS
   maturity: alpha
   chaosType: infra
   maintainers:

charts/generic/node-restart/node-restart.chartserviceversion.yaml

@@ -14,14 +14,12 @@ spec:
     Node restart contains chaos to restart the node via SSH.
   keywords:
     - Kubernetes
+    - K8S
     - Restart
-    - State
     - Node
-    - SSH
   platforms:
-    - GKE
+    - KVM/LibVirt based K8s
     - EKS
-    - AKS
   maturity: alpha
   chaosType: infra
   maintainers:

charts/generic/node-taint/node-taint.chartserviceversion.yaml

@@ -15,8 +15,8 @@ spec:
     Taint the node where application pod is scheduled
   keywords:
     - Kubernetes
+    - K8S
     - Node 
-    - State
     - Taint
   platforms:
     - GKE

charts/generic/pod-autoscaler/pod-autoscaler.chartserviceversion.yaml

@@ -15,10 +15,9 @@ spec:
     This experiment can be used for other scenarios as well, such as for checking the Node auto-scaling feature. For example, check if the pods are successfully rescheduled within a specified period in cases where the existing nodes are already running at the specified limits.
   keywords:
     - Kubernetes
+    - K8S
     - Scale
-    - State
-    - Node
-    - Replicas
+    - Pod
   platforms:
     - GKE
     - EKS

charts/generic/pod-cpu-hog-exec/pod-cpu-hog-exec.chartserviceversion.yaml

@@ -16,7 +16,11 @@ spec:
     - The application pod should be healthy once chaos is stopped. Expectation is that service-requests should be served despite chaos.
   keywords:
     - Kubernetes
+    - K8S
     - CPU
+    - Pod
+    - Exec
+    - Stress
   platforms:
     - GKE
     - Packet(Kubeadm)

charts/generic/pod-cpu-hog/pod-cpu-hog.chartserviceversion.yaml

@@ -17,7 +17,10 @@ spec:
     - The application pod should be healthy once chaos is stopped. Expectation is that service-requests should be served despite chaos.
   keywords:
     - Kubernetes
+    - K8S
     - CPU
+    - Pod
+    - Stress
   platforms:
     - GKE
     - Packet(Kubeadm)

charts/generic/pod-delete/pod-delete.chartserviceversion.yaml

@@ -17,7 +17,8 @@ spec:
  
   keywords:
     - Kubernetes
-    - State 
+    - K8S
+    - Pod
   platforms:
     - GKE
     - Konvoy

charts/generic/pod-dns-error/pod-dns-error.chartserviceversion.yaml

@@ -10,10 +10,10 @@ spec:
   categoryDescription: >
     Pod DNS Error injects dns failure/error in target pod containers
   keywords:
-    - "pods"
-    - "kubernetes"
-    - "generic"
-    - "dns"
+    - "Pod"
+    - K8S
+    - "Kubernetes"
+    - "DNS"
   maturity: alpha
   minKubeVersion: 1.12.0
   provider:

charts/generic/pod-dns-spoof/pod-dns-spoof.chartserviceversion.yaml

@@ -10,10 +10,10 @@ spec:
   categoryDescription: >
     Pod DNS Spoof can spoof particular dns requests in target pod container to desired target hostnames
   keywords:
-    - "pods"
-    - "kubernetes"
-    - "generic"
-    - "dns"
+    - "Pod"
+    - K8S
+    - "Kubernetes"
+    - "DNS"
   maturity: alpha
   minKubeVersion: 1.12.0
   provider:

charts/generic/pod-io-stress/pod-io-stress.chartserviceversion.yaml

@@ -16,7 +16,11 @@ spec:
     - The application pod should be healthy once chaos is stopped. Expectation is that service-requests should be served despite chaos.
   keywords:
     - Kubernetes
+    - K8S
     - Memory
+    - Pod
+    - IO
+    - Stress
   platforms:
     - GKE
     - Packet(Kubeadm)

charts/generic/pod-memory-hog-exec/pod-memory-hog-exec.chartserviceversion.yaml

@@ -16,7 +16,11 @@ spec:
     - The application pod should be healthy once chaos is stopped. Expectation is that service-requests should be served despite chaos.
   keywords:
     - Kubernetes
+    - K8S
     - Memory
+    - Pod
+    - Exec 
+    - Stress 
   platforms:
     - GKE
     - Packet(Kubeadm)

charts/generic/pod-memory-hog/pod-memory-hog.chartserviceversion.yaml

@@ -17,7 +17,10 @@ spec:
     - The application pod should be healthy once chaos is stopped. Expectation is that service-requests should be served despite chaos.
   keywords:
     - Kubernetes
+    - K8S
     - Memory
+    - Pod 
+    - Stress
   platforms:
     - GKE
     - Packet(Kubeadm)

charts/generic/pod-network-corruption/pod-network-corruption.chartserviceversion.yaml

@@ -16,7 +16,9 @@ spec:
     - The application pod should be healthy once chaos is stopped. Service-requests should be served (say, via alternate replicas) despite chaos.
   keywords:
     - Kubernetes
+    - K8S
     - Network
+    - Pod
     - Corruption
   platforms:
     - GKE

charts/generic/pod-network-duplication/pod-network-duplication.chartserviceversion.yaml

@@ -16,7 +16,9 @@ spec:
     - The application pod should be healthy once chaos is stopped. Service-requests should be served (say, via alternate replicas) despite chaos.
   keywords:
     - Kubernetes
+    - K8S
     - Network
+    - Pod
     - Duplication
   platforms:
     - GKE

charts/generic/pod-network-latency/pod-network-latency.chartserviceversion.yaml

@@ -16,7 +16,10 @@ spec:
     - The application pod should be healthy once chaos is stopped. Service-requests should be served despite chaos.
   keywords:
     - Kubernetes
+    - K8S
     - Network
+    - Pod 
+    - Latency
   platforms:
     - GKE
     - Minikube 

charts/generic/pod-network-loss/pod-network-loss.chartserviceversion.yaml

@@ -16,7 +16,10 @@ spec:
     - The application pod should be healthy once chaos is stopped. Service-requests should be served (say, via alternate replicas) despite chaos.
   keywords:
     - Kubernetes
+    - K8S
     - Network
+    - Pod
+    - Loss
   platforms:
     - GKE
     - Minikube 

charts/kafka/kafka-broker-disk-failure/kafka-broker-disk-failure.chartserviceversion.yaml

@@ -13,6 +13,7 @@ spec:
      Detaching a persistent disk from a node/instance for kafka
   keywords:
     - Kubernetes
+    - K8S
     - Disk
     - Kafka
   platforms:

charts/kafka/kafka-broker-pod-failure/kafka-broker-pod-failure.chartserviceversion.yaml

@@ -15,8 +15,8 @@ spec:
     This chaos experiment kills (random or specified) kafka broker pods
   keywords:
     - Kubernetes
+    - K8S
     - Pod
-    - State 
     - Kafka
   platforms:
     - GKE

charts/kafka/kafka.chartserviceversion.yaml

@@ -16,7 +16,10 @@ spec:
     - kafka-broker-pod-failure
   keywords:
     - Kubernetes
+    - K8S
     - Kafka
+    - Disk 
+    - Pod
   maintainers:
     - name: ksatchit
       email: karthik.s@mayadata.io

charts/kube-aws/ebs-loss-by-id/ebs-loss-by-id.chartserviceversion.yaml

@@ -15,11 +15,9 @@ spec:
     - Causes ebs volume loss from node or ec2 instance for a certain chaos interval from total chaos duration.
     - Tests deployment sanity (replica availability & uninterrupted service) and recovery workflows of the application pod
   keywords:
-    - Kubernetes
     - EBS
     - Volume
-    - ID
-    - State 
+    - AWS
   platforms:
     - AWS
   maturity: alpha

charts/kube-aws/ebs-loss-by-tag/ebs-loss-by-tag.chartserviceversion.yaml

@@ -15,11 +15,9 @@ spec:
     - Causes ebs volume loss by tag from node or ec2 instance for certain chaos interval from total chaos duration.
     - Tests deployment sanity (replica availability & uninterrupted service) and recovery workflows of the application pod
   keywords:
-    - Kubernetes
     - EBS
     - Volume
-    - Tag
-    - State 
+    - AWS 
   platforms:
     - AWS
   maturity: alpha

charts/kube-aws/ec2-terminate-by-id/ec2-terminate-by-id.chartserviceversion.yaml

@@ -15,9 +15,8 @@ spec:
     - Causes termination of an EC2 instance provided by instance ID before bringing it back to running state after the specified chaos duration.
     - It helps to check the performance of the application on the ec2 instance. 
   keywords:
-    - Kubernetes
+    - EC2
     - AWS
-    - Termination
   platforms:
     - AWS
   maturity: alpha

charts/kube-aws/ec2-terminate-by-tag/ec2-terminate-by-tag.chartserviceversion.yaml

@@ -15,9 +15,8 @@ spec:
     - Causes termination of an EC2 instance using instance tags before bringing it back to running state after the specified chaos duration.
     - It helps to check the performance of the application on the ec2 instance. 
   keywords:
-    - Kubernetes
+    - EC2
     - AWS
-    - Termination
   platforms:
     - AWS
   maturity: alpha

charts/kube-aws/kube-aws.chartserviceversion.yaml

@@ -19,7 +19,7 @@ spec:
   keywords:
     - AWS
     - EC2
-    - State
+    - EBS
   maintainers:
     - name: ksatchit
       email: karthik.s@mayadata.io

charts/openebs/openebs-control-plane-chaos/openebs-control-plane-chaos.chartserviceversion.yaml

@@ -13,6 +13,7 @@ spec:
      Kill all openebs control plane pods and check if gets scheduled again. 
   keywords:
     - Kubernetes
+    - K8S
     - OpenEBS
   platforms:
     - GKE

charts/openebs/openebs-nfs-provisioner-kill/openebs-nfs-provisioner-kill.chartserviceversion.yaml

@@ -13,6 +13,7 @@ spec:
     Kill the OpenEBS NFS provisioner container and check if pods consuming the NFS PVs continue to be available and volumes are writable (RWM mode)
   keywords:
     - Kubernetes
+    - K8S
     - OpenEBS
     - NFS
   platforms:

charts/openebs/openebs-pool-container-failure/openebs-pool-container-failure.chartserviceversion.yaml

@@ -14,6 +14,7 @@ spec:
      Kill the pool container and check if gets scheduled again. 
   keywords:
     - Kubernetes
+    - K8S
     - Storage Pool
     - OpenEBS
   platforms:

charts/openebs/openebs-pool-disk-loss/openebs-pool-disk-loss.chartserviceversion.yaml

@@ -16,6 +16,7 @@ spec:
     - Tests deployment sanity (replica availability & uninterrupted service) and recovery workflows of the application pod.
   keywords:
     - Kubernetes
+    - K8S
     - Storage Pool
     - OpenEBS
   platforms:

charts/openebs/openebs-pool-network-delay/openebs-pool-network-delay.chartserviceversion.yaml

@@ -13,8 +13,10 @@ spec:
      Network delay to pool pod belonging to a OpenEBS PVC 
   keywords:
     - Kubernetes
+    - K8S
     - Storage Pool
     - OpenEBS
+    - Network
   platforms:
     - GKE
     - EKS

charts/openebs/openebs-pool-network-loss/openebs-pool-network-loss.chartserviceversion.yaml

@@ -13,8 +13,10 @@ spec:
      Network loss to pool pod belonging to a OpenEBS PVC 
   keywords:
     - Kubernetes
+    - K8S
     - Storage Pool
     - OpenEBS
+    - Network
   platforms:
     - GKE
     - EKS

charts/openebs/openebs-pool-pod-failure/openebs-pool-pod-failure.chartserviceversion.yaml

@@ -14,6 +14,7 @@ spec:
      Kill the pool pod and check if gets scheduled again. 
   keywords:
     - Kubernetes
+    - K8S
     - Storage Pool
     - OpenEBS
   platforms:

charts/openebs/openebs-target-container-failure/openebs-target-container-failure.chartserviceversion.yaml

@@ -14,6 +14,7 @@ spec:
      Kill the cstor target/Jiva controller container and check if gets created again
   keywords:
     - Kubernetes
+    - K8S
     - Storage Controller
     - OpenEBS
   platforms:

charts/openebs/openebs-target-network-delay/openebs-target-network-delay.chartserviceversion.yaml

@@ -15,7 +15,8 @@ spec:
   keywords:
     - OpenEBS
     - Kubernetes
-    - Network Delay 
+    - K8S
+    - Network
   platforms:
     - GKE
     - EKS

charts/openebs/openebs-target-network-loss/openebs-target-network-loss.chartserviceversion.yaml

@@ -14,8 +14,9 @@ spec:
     Network loss to the target pod belonging to an OpenEBS PVC
   keywords:
     - Kubernetes
+    - K8S
     - OpenEBS 
-    - Network Loss
+    - Network
   platforms:
     - GKE
     - EKS

charts/openebs/openebs-target-pod-failure/openebs-target-pod-failure.chartserviceversion.yaml

@@ -14,6 +14,7 @@ spec:
      Kill the cstor target/Jiva controller pod and check if gets created again
   keywords:
     - Kubernetes
+    - K8S
     - Storage Controller
     - OpenEBS
   platforms:

charts/openebs/openebs.chartserviceversion.yaml

@@ -27,9 +27,14 @@ spec:
     - openebs-pool-disk-loss
     - openebs-nfs-provisioner-kill
   keywords:
+    - Kubernetes
+    - K8S
     - OpenEBS
     - CAS
     - Storage
+    - Network 
+    - Pod
+    - Pool  
   maintainers:
     - name: ksatchit
       email: karthik.s@mayadata.io

charts/vmware/vm-poweroff/vm-poweroff.chartserviceversion.yaml

@@ -16,7 +16,6 @@ spec:
     - Currently, the experiment is supported for vsphere version 6.X (Support for 7.X will be added soon)
 
   keywords:
-    - Kubernetes
     - Vmware
     - VM
   platforms:

charts/vmware/vmware.chartserviceversion.yaml

@@ -14,8 +14,8 @@ spec:
   experiments:
     - vm-poweroff
   keywords:
-    - Kubernetes
     - vmware
+    - VM
   maintainers:
     - name: Delphine Joyneer
       email: golkonda.joyneer@wipro.com