(fix): Add md-field for categoryDescription and fixed package.yaml(openebs) (#29)
* added categoryDescription as md-content, fixed package.yaml(openebs) Signed-off-by: daitya109 <adikid1996@gmail.com>
This commit is contained in:
@@ -10,8 +10,10 @@ metadata:
|
||||
support: https://slack.openebs.io/
|
||||
spec:
|
||||
displayName: container-kill
|
||||
categoryDescription: >
|
||||
categoryDescription: |
|
||||
Container kill contains chaos to disrupt state of kubernetes resources. Experiments can inject random container delete failures against specified application.
|
||||
- Executes SIGKILL on containers of random replicas of an application deployment.
|
||||
- Tests deployment sanity (replica availability & uninterrupted service) and recovery workflows of the application pod.
|
||||
keywords:
|
||||
- Kubernetes
|
||||
- Container
|
||||
|
@@ -1,4 +1,4 @@
|
||||
packageName: kubernetes
|
||||
packageName: generic
|
||||
experiments:
|
||||
- name: pod-delete
|
||||
CSV: pod-delete.chartserviceversion.yaml
|
||||
|
@@ -11,8 +11,11 @@ metadata:
|
||||
support: https://slack.kubernetes.io/
|
||||
spec:
|
||||
displayName: pod-delete
|
||||
categoryDescription: >
|
||||
categoryDescription: |
|
||||
Pod delete contains chaos to disrupt state of kubernetes resources. Experiments can inject random pod delete failures against specified application.
|
||||
- Causes (forced/graceful) pod failure of random replicas of an application deployment.
|
||||
- Tests deployment sanity (replica availability & uninterrupted service) and recovery workflows of the application pod.
|
||||
|
||||
keywords:
|
||||
- Kubernetes
|
||||
- State
|
||||
|
@@ -10,8 +10,10 @@ metadata:
|
||||
support: https://slack.kubernetes.io/
|
||||
spec:
|
||||
displayName: pod-network-latency
|
||||
categoryDescription: >
|
||||
categoryDescription: |
|
||||
Pod-network-latency contains chaos to disrupt network connectivity of kubernetes pods. Experiments can inject random network delays on the app replica pods.
|
||||
- Causes flaky access to application replica by injecting network delay using pumba.
|
||||
- The application pod should be healthy once chaos is stopped. Service-requests should be served despite chaos.
|
||||
keywords:
|
||||
- Kubernetes
|
||||
- Network
|
||||
|
@@ -10,8 +10,10 @@ metadata:
|
||||
support: https://slack.kubernetes.io/
|
||||
spec:
|
||||
displayName: pod-network-loss
|
||||
categoryDescription: >
|
||||
categoryDescription: |
|
||||
Pod-network-loss contains chaos to disrupt network connectivity to kubernetes pods. Experiments can inject percentage packet loss on the app replica pods.
|
||||
- Causes loss of access to application replica by injecting packet loss using pumba.
|
||||
- The application pod should be healthy once chaos is stopped. Service-requests should be served (say, via alternate replicas) despite chaos.
|
||||
keywords:
|
||||
- Kubernetes
|
||||
- Network
|
||||
|
@@ -1,5 +1,5 @@
|
||||
packageName: openebs
|
||||
subcharts:
|
||||
experiments:
|
||||
- name: openebs-pool-failure
|
||||
CSV: openebs-pool-failure.chartserviceversion.yaml
|
||||
desc: "openebs-pool-failure"
|
||||
|
Reference in New Issue
Block a user