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>
2021-09-01 15:26:28 +05:30
parent ef7595e3b3
commit fa29cf9905
60 changed files with 113 additions and 70 deletions
--- a/charts/generic/byoc-pod-delete/byoc-pod-delete.chartserviceversion.yaml
+++ b/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
--- a/charts/generic/container-kill/container-kill.chartserviceversion.yaml
+++ b/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
--- a/charts/generic/disk-fill/disk-fill.chartserviceversion.yaml
+++ b/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
--- a/charts/generic/docker-service-kill/docker-service-kill.chartserviceversion.yaml
+++ b/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 
--- a/charts/generic/generic.chartserviceversion.yaml
+++ b/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
--- a/charts/generic/kubelet-service-kill/kubelet-service-kill.chartserviceversion.yaml
+++ b/charts/generic/kubelet-service-kill/kubelet-service-kill.chartserviceversion.yaml
@@ -17,6 +17,7 @@ spec:
    
  keywords:
    - Kubernetes
+    - K8S
    - Kubelet
    - Node
    - Service
--- a/charts/generic/node-cpu-hog/node-cpu-hog.chartserviceversion.yaml
+++ b/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
--- a/charts/generic/node-drain/node-drain.chartserviceversion.yaml
+++ b/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)
--- a/charts/generic/node-io-stress/node-io-stress.chartserviceversion.yaml
+++ b/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
--- a/charts/generic/node-memory-hog/node-memory-hog.chartserviceversion.yaml
+++ b/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
--- a/charts/generic/node-poweroff/node-poweroff.chartserviceversion.yaml
+++ b/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:
--- a/charts/generic/node-restart/node-restart.chartserviceversion.yaml
+++ b/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:
--- a/charts/generic/node-taint/node-taint.chartserviceversion.yaml
+++ b/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
--- a/charts/generic/pod-autoscaler/pod-autoscaler.chartserviceversion.yaml
+++ b/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
--- a/charts/generic/pod-cpu-hog-exec/pod-cpu-hog-exec.chartserviceversion.yaml
+++ b/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)
--- a/charts/generic/pod-cpu-hog/pod-cpu-hog.chartserviceversion.yaml
+++ b/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)
--- a/charts/generic/pod-delete/pod-delete.chartserviceversion.yaml
+++ b/charts/generic/pod-delete/pod-delete.chartserviceversion.yaml
@@ -17,7 +17,8 @@ spec:
 
  keywords:
    - Kubernetes
-    - State 
+    - K8S
+    - Pod
  platforms:
    - GKE
    - Konvoy
--- a/charts/generic/pod-dns-error/pod-dns-error.chartserviceversion.yaml
+++ b/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:
--- a/charts/generic/pod-dns-spoof/pod-dns-spoof.chartserviceversion.yaml
+++ b/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:
--- a/charts/generic/pod-io-stress/pod-io-stress.chartserviceversion.yaml
+++ b/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)
--- a/charts/generic/pod-memory-hog-exec/pod-memory-hog-exec.chartserviceversion.yaml
+++ b/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)
--- a/charts/generic/pod-memory-hog/pod-memory-hog.chartserviceversion.yaml
+++ b/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)
--- a/charts/generic/pod-network-corruption/pod-network-corruption.chartserviceversion.yaml
+++ b/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
--- a/charts/generic/pod-network-duplication/pod-network-duplication.chartserviceversion.yaml
+++ b/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
--- a/charts/generic/pod-network-latency/pod-network-latency.chartserviceversion.yaml
+++ b/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 
--- a/charts/generic/pod-network-loss/pod-network-loss.chartserviceversion.yaml
+++ b/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