-
Notifications
You must be signed in to change notification settings - Fork 808
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
[chart] Node update strategy & auto driver image tag #988
[chart] Node update strategy & auto driver image tag #988
Conversation
Welcome @stevehipwell! |
Hi @stevehipwell. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/approve |
/ok-to-test |
@vdhanan any chance this could be merged? |
thanks for the PR, i'll review it today |
2a17cbc
to
95cd6f5
Compare
19df27f
to
26a652d
Compare
26a652d
to
fa02d70
Compare
@vdhanan I've rebased to capture the last chart release and updated the changelog again for the last chart release. Is there any chance of a review today, I need the update strategy feature ASAP. |
fa02d70
to
16de75b
Compare
charts/aws-ebs-csi-driver/Chart.yaml
Outdated
@@ -1,8 +1,8 @@ | |||
apiVersion: v2 | |||
appVersion: "1.1.3" | |||
appVersion: 1.1.3 |
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.
Is there a reason to add the v
elsewhere instead of just setting this to "v1.1.3"
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.
Although the spec says that appVersion
needn't be a valid SemVer version, there are tools that either don't work correctly or error if it's not. The comment about quotes being recommended is also misleading as they're only relevant if you have a version that is a different data type.
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.
Additionally, for many reasons which I won't bother listing, sticking with a valid SemVer 2 version here will cause the least potential for disruption as tools and technologies move on.
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.
Fair enough
16de75b
to
951de5f
Compare
@stevehipwell I am not an owner, so I can't trigger a merge. @vdhanan can you get this merged for Steve? |
annotations: | ||
artifacthub.io/changes: | | ||
- kind: changed | ||
description: Use chart app version as default image tag | ||
- kind: changed | ||
description: Add updateStrategy to daemonsets |
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.
i'm curious what purpose these annotations serve when we already have a helm chart changelog
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.
They will show up on artifact.io when the issue to publish there gets completed
sorry for the delayed review, and thanks for the PR -- could you please run |
@@ -54,7 +56,7 @@ spec: | |||
{{- end }} | |||
containers: | |||
- name: ebs-plugin | |||
image: {{ .Values.image.repository }}:{{ .Values.image.tag }} | |||
image: {{ printf "%s:%s" .Values.image.repository (default (printf "v%s" .Chart.AppVersion) (toString .Values.image.tag)) }} |
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.
Will .Values.image.tag be empty after change?
Can we use the v{Chart.appversion} in values.yaml continue use the tag field in the template?
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.
If image.tag is not set it will fall back to the value in appVersion. When running a helm install/upgrade you can either use --values to pass a yaml file of values that could contain image.tag to provide a version or use --set image.tag to set the version to use.
Signed-off-by: Steve Hipwell <steve.hipwell@gmail.com>
951de5f
to
10af684
Compare
Thanks @vdhanan, I've re-generated the Kustomize maifests. |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: krmichel, stevehipwell, vdhanan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Is this a bug fix or adding new feature?
This PR adds the ability to configure the node update strategy and uses the chart app version for the image tag.
Fixes #985.
What is this PR about? / Why do we need it?
With the default update strategy the more nodes added to the cluster the longer it takes to upgrade, this PR makes this customisable and sets the default to the 10% unavailable strategy used by the aws-vpc-cni and the EKS kube-proxy daemonsets.
What testing is done?
Helm template output validated.