refactors directory and file structure
Signed-off-by: neelanjan00 <neelanjan.manna@harness.io>
This commit is contained in:
@@ -0,0 +1,39 @@
|
||||
---
|
||||
apiVersion: litmuschaos.io/v1alpha1
|
||||
kind: ChartServiceVersion
|
||||
metadata:
|
||||
name: pod-cpu-hog
|
||||
version: 0.1.0
|
||||
annotations:
|
||||
categories: Kubernetes
|
||||
vendor: Harness
|
||||
spec:
|
||||
displayName: Pod CPU Hog
|
||||
categoryDescription: |
|
||||
Pod-CPU-Hog fault consumes the CPU resources of specified containers in Kubernetes pods.
|
||||
- Causes CPU resource consumption on specified application containers using cgroups and litmus nsutil which consume CPU resources of the given target containers.
|
||||
- It can test the application's resilience to potential slowness/unavailability of some replicas due to high CPU load.
|
||||
- The application pod should be healthy once chaos is stopped. Expectation is that service-requests should be served despite chaos.
|
||||
keywords:
|
||||
- Kubernetes
|
||||
platforms:
|
||||
- GKE
|
||||
- Packet(Kubeadm)
|
||||
- Minikube
|
||||
- EKS
|
||||
- AKS
|
||||
- Kind
|
||||
experiments:
|
||||
- pod-cpu-hog
|
||||
- sock-shop
|
||||
- sock-shop-promProbe
|
||||
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:
|
||||
- base64data: ""
|
||||
mediatype: ""
|
Reference in New Issue
Block a user