Chore(ec2): Add charts for ec2 terminate experiment-by-id and ec2-terminate-by-tag (#440)

* Chore(ec2): Add charts for ec2 terminate experiment-by-id and ec2-terminate-by-tag

Signed-off-by: uditgaurav <udit@chaosnative.com>

* add ec2 terminates by id and tag in pkg and csv

Signed-off-by: uditgaurav <udit@chaosnative.com>
This commit is contained in:
Udit Gaurav
2021-04-15 23:14:39 +05:30
committed by GitHub
parent 579aeb0356
commit dd872759aa
15 changed files with 278 additions and 29 deletions

View File

@@ -25,6 +25,14 @@ spec:
## specify the size as percentage of free space on the file system
- name: FILESYSTEM_UTILIZATION_PERCENTAGE
value: '10'
## Number of core of CPU
- name: CPU
value: '1'
## Total number of workers default value is 4
- name: NUMBER_OF_WORKERS
value: '4'
## enter the comma separated target nodes name
- name: TARGET_NODES

View File

@@ -64,9 +64,17 @@ spec:
- name: FILESYSTEM_UTILIZATION_BYTES
value: ''
## Number of core of CPU
- name: CPU
value: '1'
## Total number of workers default value is 4
- name: NUMBER_OF_WORKERS
value: '4'
value: '4'
## Total number of vm workers
- name: VM_WORKERS
value: '1'
## enter the comma separated target nodes name
- name: TARGET_NODES

View File

@@ -62,7 +62,10 @@ spec:
## Specify the amount of memory to be consumed in mebibytes
## NOTE: for selecting this option keep MEMORY_CONSUMPTION_PERCENTAGE empty
- name: MEMORY_CONSUMPTION_MEBIBYTES
value: ''
value: ''
- name: NUMBER_OF_WORKERS
value: '1'
# ENTER THE COMMA SEPARATED TARGET NODES NAME
- name: TARGET_NODES

View File

@@ -2,17 +2,17 @@ apiVersion: litmuchaos.io/v1alpha1
kind: ChartServiceVersion
metadata:
createdAt: 2020-10-28T10:28:08Z
name: ec2-terminate
name: ec2-terminate-by-id
version: 0.1.0
annotations:
categories: Kubernetes
vendor: Mayadata
support: https://app.slack.com/client/T09NY5SBT/CNXNB0ZTN
spec:
displayName: ec2-terminate
displayName: ec2-terminate-by-id
categoryDescription: |
This experiment causes termination of an EC2 instance for a certain chaos duration.
- Causes termination of an EC2 instance before bringing it back to running state after the specified chaos duration.
- 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
@@ -32,12 +32,12 @@ spec:
app.kubernetes.io/version: latest
links:
- name: Source Code
url: https://github.com/litmuschaos/litmus-go/tree/master/experiments/kube-aws/ec2-terminate
url: https://github.com/litmuschaos/litmus-go/tree/master/experiments/kube-aws/ec2-terminate-by-id
- name: Documentation
url: https://docs.litmuschaos.io/docs/ec2-terminate/
url: https://docs.litmuschaos.io/docs/ec2-terminate-by-id/
- name: Video
url:
icon:
- url:
mediatype: ""
chaosexpcrdlink: https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/kube-aws/ec2-terminate/experiment.yaml
chaosexpcrdlink: https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/kube-aws/ec2-terminate-by-id/experiment.yaml

View File

@@ -6,20 +6,24 @@ metadata:
spec:
annotationCheck: 'false'
engineState: 'active'
chaosServiceAccount: ec2-terminate-sa
chaosServiceAccount: ec2-terminate-by-id-sa
# It can be retain/delete
jobCleanUpPolicy: 'delete'
experiments:
- name: ec2-terminate
- name: ec2-terminate-by-id
spec:
components:
env:
# set chaos duration (in sec) as desired
- name: TOTAL_CHAOS_DURATION
value: '60'
value: '30'
# set interval duration (in sec) as desired
- name: CHAOS_INTERVAL
value: '30'
# Instance ID of the target ec2 instance
# If not provided it will select randomly from the region
# Multiple IDs can also be provided as comma seperated values ex: id1,id2
- name: EC2_INSTANCE_ID
value: ''

View File

@@ -4,9 +4,9 @@ description:
Detaching an ebs volume from ec2 instance.
kind: ChaosExperiment
metadata:
name: ec2-terminate
name: ec2-terminate-by-id
labels:
name: ec2-terminate
name: ec2-terminate-by-id
app.kubernetes.io/part-of: litmus
app.kubernetes.io/component: chaosexperiment
app.kubernetes.io/version: latest
@@ -39,12 +39,15 @@ spec:
imagePullPolicy: Always
args:
- -c
- ./experiments -name ec2-terminate
- ./experiments -name ec2-terminate-by-id
command:
- /bin/bash
env:
- name: TOTAL_CHAOS_DURATION
value: '60'
value: '30'
- name: CHAOS_INTERVAL
value: '30'
# Period to wait before and after injection of chaos in sec
- name: RAMP_TIME
@@ -54,12 +57,17 @@ spec:
- name: MANAGED_NODEGROUP
value: 'disable'
# Instance ID of the target ec2 instance
# Multiple IDs can also be provided as comma seperated values ex: id1,id2
- name: EC2_INSTANCE_ID
value: ''
- name: REGION
value: ''
- name: SEQUENCE
value: 'parallel'
# Provide the path of aws credentials mounted from secret
- name: AWS_SHARED_CREDENTIALS_FILE
value: '/tmp/cloud_config.yml'
@@ -70,7 +78,7 @@ spec:
value: 'litmus'
labels:
name: ec2-terminate
name: ec2-terminate-by-id
app.kubernetes.io/part-of: litmus
app.kubernetes.io/component: experiment-job
app.kubernetes.io/version: latest

View File

@@ -2,18 +2,18 @@
apiVersion: v1
kind: ServiceAccount
metadata:
name: ec2-terminate-sa
name: ec2-terminate-by-id-sa
namespace: default
labels:
name: ec2-terminate-sa
name: ec2-terminate-by-id-sa
app.kubernetes.io/part-of: litmus
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: ec2-terminate-sa
name: ec2-terminate-by-id-sa
labels:
name: ec2-terminate-sa
name: ec2-terminate-by-id-sa
app.kubernetes.io/part-of: litmus
rules:
- apiGroups: [""]
@@ -35,15 +35,15 @@ rules:
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: ec2-terminate-sa
name: ec2-terminate-by-id-sa
labels:
name: ec2-terminate-sa
name: ec2-terminate-by-id-sa
app.kubernetes.io/part-of: litmus
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: ec2-terminate-sa
name: ec2-terminate-by-id-sa
subjects:
- kind: ServiceAccount
name: ec2-terminate-sa
name: ec2-terminate-by-id-sa
namespace: default

View File

@@ -0,0 +1,43 @@
apiVersion: litmuchaos.io/v1alpha1
kind: ChartServiceVersion
metadata:
createdAt: 2021-04-15T10:28:08Z
name: ec2-terminate-by-tag
version: 0.1.0
annotations:
categories: Kubernetes
vendor: Mayadata
support: https://app.slack.com/client/T09NY5SBT/CNXNB0ZTN
spec:
displayName: ec2-terminate-by-tag
categoryDescription: |
This experiment causes termination of an EC2 instance for a certain chaos duration.
- 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
- AWS
- Termination
platforms:
- AWS
maturity: alpha
chaosType: infra
maintainers:
- name: Udit Gaurav
email: uditgaurav@mayadata.io
provider:
name: Mayadata
labels:
app.kubernetes.io/component: chartserviceversion
app.kubernetes.io/version: latest
links:
- name: Source Code
url: https://github.com/litmuschaos/litmus-go/tree/master/experiments/kube-aws/ec2-terminate-by-tag
- name: Documentation
url: https://docs.litmuschaos.io/docs/ec2-terminate-by-tag/
- name: Video
url:
icon:
- url:
mediatype: ""
chaosexpcrdlink: https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/kube-aws/ec2-terminate-by-tag/experiment.yaml

View File

@@ -0,0 +1,36 @@
apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
name: nginx-chaos
namespace: default
spec:
annotationCheck: 'false'
engineState: 'active'
chaosServiceAccount: ec2-terminate-by-tag-sa
# It can be retain/delete
jobCleanUpPolicy: 'delete'
experiments:
- name: ec2-terminate-by-tag
spec:
components:
env:
# set chaos duration (in sec) as desired
- name: TOTAL_CHAOS_DURATION
value: '30'
# set interval duration (in sec) as desired
- name: CHAOS_INTERVAL
value: '30'
# Instance Tag of the target ec2 instances
# ex: team:devops (key:value)
- name: INSTANCE_TAG
value: ''
# provide the region name of the instace
- name: REGION
value: ''
# enable it if the target instance is a part of self-managed nodegroup.
- name: MANAGED_NODEGROUP
value: 'disable'

View File

@@ -0,0 +1,86 @@
apiVersion: litmuschaos.io/v1alpha1
description:
message: |
Detaching an ebs volume from ec2 instance.
kind: ChaosExperiment
metadata:
name: ec2-terminate-by-tag
labels:
name: ec2-terminate-by-tag
app.kubernetes.io/part-of: litmus
app.kubernetes.io/component: chaosexperiment
app.kubernetes.io/version: latest
spec:
definition:
scope: Cluster
permissions:
- apiGroups:
- ""
- "batch"
- "litmuschaos.io"
resources:
- "jobs"
- "pods"
- "events"
- "pods/log"
- "pods/exec"
- "secrets"
- "chaosengines"
- "chaosexperiments"
- "chaosresults"
verbs:
- "create"
- "list"
- "get"
- "patch"
- "update"
- "delete"
image: "litmuschaos/go-runner:latest"
imagePullPolicy: Always
args:
- -c
- ./experiments -name ec2-terminate-by-tag
command:
- /bin/bash
env:
- name: TOTAL_CHAOS_DURATION
value: '30'
- name: CHAOS_INTERVAL
value: '30'
# Period to wait before and after injection of chaos in sec
- name: RAMP_TIME
value: ''
# enable it if the target instance is a part of self-managed nodegroup.
- name: MANAGED_NODEGROUP
value: 'disable'
- name: REGION
value: ''
# Target the percentage of instance filtered from tag
- name: INSTANCE_AFFECTED_PERC
value: ''
- name: SEQUENCE
value: 'parallel'
# Provide the path of aws credentials mounted from secret
- name: AWS_SHARED_CREDENTIALS_FILE
value: '/tmp/cloud_config.yml'
# provide the LIB
# only litmus supported
- name: LIB
value: 'litmus'
labels:
name: ec2-terminate-by-tag
app.kubernetes.io/part-of: litmus
app.kubernetes.io/component: experiment-job
app.kubernetes.io/version: latest
secrets:
- name: cloud-secret
mountPath: /tmp/

View File

@@ -0,0 +1,49 @@
---
apiVersion: v1
kind: ServiceAccount
metadata:
name: ec2-terminate-by-tag-sa
namespace: default
labels:
name: ec2-terminate-by-tag-sa
app.kubernetes.io/part-of: litmus
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: ec2-terminate-by-tag-sa
labels:
name: ec2-terminate-by-tag-sa
app.kubernetes.io/part-of: litmus
rules:
- apiGroups: [""]
resources: ["pods","events","secrets"]
verbs: ["create","list","get","patch","update","delete","deletecollection"]
- apiGroups: [""]
resources: ["pods/exec","pods/log"]
verbs: ["create","list","get"]
- apiGroups: ["batch"]
resources: ["jobs"]
verbs: ["create","list","get","delete","deletecollection"]
- apiGroups: ["litmuschaos.io"]
resources: ["chaosengines","chaosexperiments","chaosresults"]
verbs: ["create","list","get","patch","update"]
- apiGroups: [""]
resources: ["nodes"]
verbs: ["patch","get","list"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: ec2-terminate-by-tag-sa
labels:
name: ec2-terminate-by-tag-sa
app.kubernetes.io/part-of: litmus
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: ec2-terminate-by-tag-sa
subjects:
- kind: ServiceAccount
name: ec2-terminate-by-tag-sa
namespace: default

View File

Before

Width:  |  Height:  |  Size: 3.1 KiB

After

Width:  |  Height:  |  Size: 3.1 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.1 KiB

View File

@@ -13,7 +13,8 @@ spec:
kube-aws contains chaos to disrupt state of aws resources running part of kubernetes cluster
experiments:
- k8-aws-ec2-terminate
- ec2-terminate
- ec2-terminate-by-id
- ec2-terminate-by-tag
- ebs-loss
keywords:
- AWS

View File

@@ -3,9 +3,12 @@ experiments:
- name: k8-aws-ec2-terminate
CSV: k8-aws-ec2-terminate.chartserviceversion.yaml
desc: "k8-aws-ec2-terminate"
- name: ec2-terminate
CSV: ec2-terminate.chartserviceversion.yaml
desc: "ec2-terminate"
- name: ec2-terminate-by-id
CSV: ec2-terminate-by-id.chartserviceversion.yaml
desc: "ec2-terminate-by-id"
- name: ec2-terminate-by-tag
CSV: ec2-terminate-by-tag.chartserviceversion.yaml
desc: "ec2-terminate-by-tag"
- name: ebs-loss
CSV: ebs-loss.chartserviceversion.yaml
desc: "ebs-loss"