Jonathan Johnson
Jonathan Johnson
This [Katacoda scenario that teaches chaoskube](https://katacoda.com/javajon/courses/kubernetes-chaos/chaoskube) as well as [this scenario at O'Reilly learning](https://learning.oreilly.com/scenarios/kubernetes-chaos-chaoskube/9781492083948/) relies on the Helm chart. These scenarios will be updated/fixed as soon as the new chart...
Tried this: ```bash kubectl create namespace chaoskube helm repo add chaoskube https://linki.github.io/chaoskube helm repo update helm install chaoskube chaoskube/chaoskube \ --version 0.1.0 \ --namespace chaoskube \ --set 'tag=v0.21.0' \ --set...
It's best to peg it at a released version. The tag default is current blank (""), which is a covert way of defining "latest". Suggested latest as default to be...
With the default tag as "" then what version of Chaoskube will be used? The missing value "" seems very indeterministic, not self-documenting, and can easily break idempotency over time....
As part of this Helm chart installation update, it should be registered on the chaos list at [Artifacthub.io](https://artifacthub.io/packages/search?ts_query_web=chaos).
Updated the chart install at [Katacoda scenario for Chaoskube](https://www.katacoda.com/javajon/courses/kubernetes-chaos/chaoskube). The chart installs and ChaosKube appears healthy as seen in step 2. However, the Pod killing is no longer performing its...
@linki > When I look at the code it looks like given the "" tag value it will use the chart's appVersion (the released version) rather than latest. Isn't that...
It's already live: https://www.katacoda.com/javajon/courses/kubernetes-chaos
@mkilchhofer see updates for #275
Perhaps there are Chartify ideas there that can be salvaged or collaborate efforts. May want to mention something in this project's readme as Chartify is found in awesome and blogs...