refactors directory and file structure

Signed-off-by: neelanjan00 <neelanjan.manna@harness.io>

faults/kubernetes/node-cpu-hog/engine.yaml

@@ -0,0 +1,38 @@
+---
+apiVersion: litmuschaos.io/v1alpha1
+kind: ChaosEngine
+metadata:
+  name: nginx-chaos
+  namespace: default
+spec:
+  # It can be active/stop
+  engineState: 'active'
+  #ex. values: ns1:name=percona,ns2:run=nginx
+  auxiliaryAppInfo: ''
+  chaosServiceAccount: node-cpu-hog-sa
+  experiments:
+    - name: node-cpu-hog
+      spec:
+        components:
+          env:
+            # set chaos duration (in sec) as desired
+            - name: TOTAL_CHAOS_DURATION
+              value: '60'
+
+            ## ENTER THE NUMBER OF CORES OF CPU FOR CPU HOGGING
+            ## OPTIONAL VALUE IN CASE OF EMPTY VALUE IT WILL TAKE NODE CPU CAPACITY
+            - name: NODE_CPU_CORE
+              value: '1'
+
+            ## LOAD CPU WITH GIVEN PERCENT LOADING FOR THE CPU STRESS WORKERS.
+            ## 0 IS EFFECTIVELY A SLEEP (NO LOAD) AND 100 IS FULL LOADING
+            - name: CPU_LOAD
+              value: '0'
+
+            ## percentage of total nodes to target
+            - name: NODES_AFFECTED_PERC
+              value: ''
+
+            # provide the comma separated target node names
+            - name: TARGET_NODES
+              value: ''

faults/kubernetes/node-cpu-hog/fault.yaml

@@ -0,0 +1,102 @@
+---
+apiVersion: litmuschaos.io/v1alpha1
+description:
+  message: |
+    Give a CPU spike on a node belonging to a deployment
+kind: ChaosExperiment
+metadata:
+  name: node-cpu-hog
+  labels:
+    name: node-cpu-hog
+    app.kubernetes.io/part-of: litmus
+    app.kubernetes.io/component: chaosexperiment
+    app.kubernetes.io/version: ci
+spec:
+  definition:
+    scope: Cluster
+    permissions:
+      # Create and monitor the experiment & helper pods
+      - apiGroups: [""]
+        resources: ["pods"]
+        verbs: ["create", "delete", "get", "list", "patch", "update", "deletecollection"]
+      # Performs CRUD operations on the events inside chaosengine and chaosresult
+      - apiGroups: [""]
+        resources: ["events"]
+        verbs: ["create", "get", "list", "patch", "update"]
+      # Fetch configmaps details and mount it to the experiment pod (if specified)
+      - apiGroups: [""]
+        resources: ["configmaps"]
+        verbs: ["get", "list"]
+      # Track and get the runner, experiment, and helper pods log
+      - apiGroups: [""]
+        resources: ["pods/log"]
+        verbs: ["get", "list", "watch"]
+      # for creating and managing to execute commands inside target container
+      - apiGroups: [""]
+        resources: ["pods/exec"]
+        verbs: ["get", "list", "create"]
+      # for configuring and monitor the experiment job by the chaos-runner pod
+      - apiGroups: ["batch"]
+        resources: ["jobs"]
+        verbs: ["create", "list", "get", "delete", "deletecollection"]
+      # for creation, status polling and deletion of litmus chaos resources used within a chaos workflow
+      - apiGroups: ["litmuschaos.io"]
+        resources: ["chaosengines", "chaosexperiments", "chaosresults"]
+        verbs: ["create", "list", "get", "patch", "update", "delete"]
+      # for experiment to perform node status checks
+      - apiGroups: [""]
+        resources: ["nodes"]
+        verbs: ["get", "list"]
+    image: "chaosnative/go-runner:ci"
+    imagePullPolicy: Always
+    args:
+      - -c
+      - ./experiments -name node-cpu-hog
+    command:
+      - /bin/bash
+    env:
+      - name: TOTAL_CHAOS_DURATION
+        value: '60'
+
+      # Period to wait before and after injection of chaos in sec
+      - name: RAMP_TIME
+        value: ''
+
+      ## ENTER THE NUMBER OF CORES OF CPU FOR CPU HOGGING
+      ## OPTIONAL VALUE IN CASE OF EMPTY VALUE IT WILL TAKE NODE CPU CAPACITY
+      - name: NODE_CPU_CORE
+        value: ''
+
+      ## LOAD CPU WITH GIVEN PERCENT LOADING FOR THE CPU STRESS WORKERS.
+      ## 0 IS EFFECTIVELY A SLEEP (NO LOAD) AND 100 IS FULL LOADING
+      - name: CPU_LOAD
+        value: '100'
+
+      # ENTER THE COMMA SEPARATED TARGET NODES NAME
+      - name: TARGET_NODES
+        value: ''
+
+      - name: NODE_LABEL
+        value: ''
+
+      # provide lib image
+      - name: LIB_IMAGE
+        value: 'chaosnative/go-runner:ci'
+
+      ## percentage of total nodes to target
+      - name: NODES_AFFECTED_PERC
+        value: ''
+
+      - name: DEFAULT_HEALTH_CHECK
+        value: 'false'
+
+      ## it defines the sequence of chaos execution for multiple target nodes
+      ## supported values: serial, parallel
+      - name: SEQUENCE
+        value: 'parallel'
+
+    labels:
+      name: node-cpu-hog
+      app.kubernetes.io/part-of: litmus
+      app.kubernetes.io/component: experiment-job
+      app.kubernetes.io/version: ci

faults/kubernetes/node-cpu-hog/node-cpu-hog.chartserviceversion.yaml

@@ -0,0 +1,37 @@
+---
+apiVersion: litmuschaos.io/v1alpha1
+kind: ChartServiceVersion
+metadata:
+  name: node-cpu-hog
+  version: 0.1.0
+  annotations:
+    categories: Kubernetes
+    vendor: Harness
+spec:
+  displayName: Node CPU Hog
+  categoryDescription: |
+    Node CPU hog fault disrupts the state of Kubernetes resources. This fault injects a CPU spike on a node where the application pod is scheduled.
+    - CPU hog on a particular node where the application deployment is available.
+    - After test, the recovery should be manual for the application pod and node in case they are not in an appropriate state.
+  keywords:
+    - Kubernetes
+  platforms:
+    - GKE
+    - EKS
+    - AKS
+    - Kind
+    - Rancher
+    - OpenShift(OKD)
+  experiments:
+    - node-cpu-hog
+  chaosType: infra
+  minKubeVersion: 1.12.0
+  labels:
+    app.kubernetes.io/component: chartserviceversion
+    app.kubernetes.io/version: ci
+  links:
+    - name: Documentation
+      url: https://docs.harness.io/category/kl0mxwpfw1-hce-category
+  icon:
+    - url:
+      mediatype: ""