Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

maxKill functionality not working using helm chart #344

Open
lathikakodoth opened this issue Jun 2, 2021 · 1 comment
Open

maxKill functionality not working using helm chart #344

lathikakodoth opened this issue Jun 2, 2021 · 1 comment

Comments

@lathikakodoth
Copy link

When I try chaoskube with --max-kill=3 option it is not accepting , though logs does mention the value is taken .The number of pods killed is by default 1

From logs :
time="2021-06-02T10:30:45Z" level=info msg="setting pod filter" annotations= excludedPodNames="" includedPodNames="" kinds= labels="app=playground" maxKill=3 minimumAge=0s namespaceLabels= namespaces=

Command used :
helm install ${name}
stable/chaoskube
--set interval=${interval},rbac.create=true,labels=${label},namespaces=${namespace}
--set rbac.serviceAccountName=chaoskube,dryRun=false
--set maxKill=3,

@linki
Copy link
Owner

linki commented Jun 8, 2021

You're using an old version of the chart (stable/chaoskube) where this flag is not supported.

Please use the following to use the new chart: #275 (comment)

$ helm repo add chaoskube https://linki.github.io/chaoskube
$ helm repo update
$ helm install chaoskube chaoskube/chaoskube --set chaoskube.args.max-kill=3 --set image.tag=v0.21.0 ...

The image tag is currently needed because the default in the chart is wrong.

Here's the relevant values.yaml where you can see all the parameters: https://github.com/linki/chaoskube/blob/master/chart/chaoskube/values.yaml

Let me know if this works for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants