#helm (2019-07)
Archive: https://archive.sweetops.com/helm/
2019-07-09
![btai avatar](https://avatars.slack-edge.com/2019-09-04/736463433650_34701761239ea7ba8207_72.jpg)
how are you guys handling the Error: "blah" has no deployed releases
when a helm install gets in a failed state? I Know you can run delete --purge
but thats not very ideal
![btai avatar](https://avatars.slack-edge.com/2019-09-04/736463433650_34701761239ea7ba8207_72.jpg)
To answer my own question theres a new --atomic
flag in helm 2.13 that will clean up a failed release.
2019-07-16
![James D. Bohrman avatar](https://avatars.slack-edge.com/2019-02-23/560246427015_e4c537417695aebb43bd_72.jpg)
What’s this I hear about Helm 3 not needing Tiller?
![Steven avatar](https://secure.gravatar.com/avatar/85c27d283a537b0c5b54590f47293fe1.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
That’s been the plan for a long time
2019-07-18
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
theres a beta out
2019-07-22
![btai avatar](https://avatars.slack-edge.com/2019-09-04/736463433650_34701761239ea7ba8207_72.jpg)
anyone else ever run into issues where you deploy a helm chart with a new image, but because of an application error, you redeploy the previous stable image, but the new image version persists? i.e running basically these two commands:
$ helm upgrade blah --set "imageTag=1.2.4"
## application error on version 1.2.4
$ helm upgrade blah --set "imageTag=1.2.3"
on paper, i’d think the image at this point should be 1.2.3, but i’ve run into the case where it continues to persist 1.2.4. i feel like helm shouldn’t care about your image tags and their semver versions and whether youre incrementing or decrementing the image version, and this shouldnt be happening?
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
I don’t quite follow. helm
doesn’t know what imageTag
means. it doesn’t know what any “value” means.
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
most likely some subtle logical bug.
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
does the helm status flip to FAILED
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
?
![btai avatar](https://avatars.slack-edge.com/2019-09-04/736463433650_34701761239ea7ba8207_72.jpg)
@Erik Osterman (Cloud Posse) exactly! which is why it’s so weird to me. but this never happens when we deploy forward (i.e. v1.2.3 -> v1.2.4) and we run hundreds of deployments a day but i’ve noticed it happen on rare occasions when we deploy backwards. (v1.2.4 -> v1.2.3)
![btai avatar](https://avatars.slack-edge.com/2019-09-04/736463433650_34701761239ea7ba8207_72.jpg)
helm deploys successfully so no FAILED
status
2019-07-31
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
Hi. I am relying on helm test
in my ci/cd pipeline. It feels very random since I sometimes get a bad address host:port
response from wget
. I have no idea why this is happening every 20th time. Any advices?
every 20th was of course an example. It is very random. Is there a reliable way of testing services that I’m not aware of?
I have readiness and liveness probes setup on the deployment.
Message Input
Message #helm-dev