-
Notifications
You must be signed in to change notification settings - Fork 803
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
Pin helm version to v2.6.2 #486
Conversation
helm/helm#3275 has caused serious amounts of downtime in the last week or so for various deployments at Berkeley, so let's recommend people use the last known version that did not have these issues.
/cc @ryanlovett who was bitten by this again today. Would be great if someone other than me could validate the commands! |
CHANGELOG.md
Outdated
|
||
```bash | ||
curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get > install-helm.bash | ||
bash install-helm.bash --version 2.6.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The version needs a 'v' in front, v2.6.2.
doc/source/setup-helm.rst
Outdated
@@ -15,11 +15,16 @@ terminal: | |||
|
|||
.. code:: bash | |||
|
|||
curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get | bash | |||
curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get > install-helm.bash | |||
bash install-helm.bash --version 2.6.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here too, "v2.6.2"
CHANGELOG.md
Outdated
```bash | ||
curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get > install-helm.bash | ||
bash install-helm.bash --version 2.6.2 | ||
helm install --upgrade |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no '--upgrade' flag to helm install
in 2.6.2. I think you meant helm init --upgrade
?
Fixed, @ryanlovett! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1!
looks great! |
@yuvipanda @choldgraf @ryanlovett About helm version v2.6.2The Helm annotation allowing deletion of jobs through annotations like One clusterrole, clusterrolebinding, role, rolebinding, serviceaccount, daemonset, and one job. |
Ugh, I hate technology. Should we consider just moving away from helm?
…On Wed, Feb 7, 2018 at 5:05 PM, Erik Sundell ***@***.***> wrote:
@yuvipanda <https://github.com/yuvipanda> @choldgraf
<https://github.com/choldgraf> @ryanlovett <https://github.com/ryanlovett>
About helm version v2.6.2
The Helm annotation allowing deletion of jobs through annotations like "
helm.sh/hook-delete-policy": hook-succeeded that was introduced in Helm
v2.7.0 <helm/helm#2692>. Without it
non-fixed names for the roles is troublesome as I end up getting "it
already exist" issues...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#486 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAB23onA0tQma8-7EQXHB9nnB6XoJrjpks5tSkhKgaJpZM4R6kCS>
.
--
Yuvi Panda T
http://yuvi.in/blog
|
Helm has a Would one option be to make the pre-puller a separate chart, and get people to run two commands?
where the pre-puller could pull the image as an initContainer, then either switch to a |
@manics i have considered that also! If that is done, I think one might resolve some issues with helm upgrades where the hook resources are already existing and errors like that. Depends, I dont grasp this fully: If you use helm to upgrade a DaemonSet as part of a hook, or not, will that behave differently when it comes the the " already exist" error? One does not get this error when we upgrade the hub deployment or a serviceaccount object etc... But we get it if the resource is a hook? Or do we? Hmmm... All in all, I'm thinking that the use of Hooks can cause some issues, and we do it in order to order things before others. By having two charts, one updated after another, one could circumvent that. One might also introduce other issues, I know I don't know all the consequences. |
helm/helm#3275 has caused
serious amounts of downtime in the last week or so for
various deployments at Berkeley, so let's recommend people use
the last known version that did not have these issues.