-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Set up helm charts versioning #7448
Conversation
Implements part of #7405 Separates `version` from `appVersion` in both `linkerd-crds` and `linkerd-control-plane` charts. In `linkerd-crds` embeds `version` as a label in the CRDs. In `linkerd-control-plane`, embeds `linkerd-crds`'s `version` as a new entry in the `linkerd-config` ConfigMap, to use in a new `linkerd check` that will be implemented in a separate PR.
@@ -16,8 +16,7 @@ dependencies: | |||
- name: partials | |||
version: 0.1.0 | |||
repository: file://../partials | |||
# this version will be updated by the CI before publishing the Helm tarball | |||
version: 0.1.0 | |||
version: 1.0.0-edge |
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.
So do we begin updating this now with the year.month.edge-number now? If not, when is this bumped?
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.
Unlike appVersion
, this has to follow semver's major.minor.patch[-pre-release identifier]
. I proposed in #7405 the following bumping criteria:
- patch: bump for minor changes
- minor: bump for new additions in templates or to values.yaml
- major: bump for backwards-incompatible changes made to values.yaml
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.
Sounds good. So lets say edge-21.12.3
is the first edge with these changes.
The GitHub release and linkerd version
output will still be edge-21.12.3
, but the Helm version for linkerd-control-plane would be 1.0.1-edge
?
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.
Correct. For linkerd-control-plane
, helm will expose both the chart and the app versions:
$ helm ls -A
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
linkerd-crds linkerd 1 2021-12-10 11:47:32.885183008 -0500 -05 deployed linkerd-crds-1.0.0-edge
linkerd-control-plane linkerd 1 2021-12-10 11:47:59.548941284 -0500 -05 deployed linkerd-control-plane-1.0.0-edge edge-21.12.2
dc6d78b
to
7d8daa5
Compare
Implements part of #7405
Separates
version
fromappVersion
in bothlinkerd-crds
andlinkerd-control-plane
charts.In
linkerd-crds
embedsversion
as a label in the CRDs.In
linkerd-control-plane
, embedslinkerd-crds
'sversion
as a newentry in the
linkerd-config
ConfigMap, to use in a newlinkerd check
that will be implemented in a separate PR.