-
Notifications
You must be signed in to change notification settings - Fork 1
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
chore: add version labels for all internal charts #350
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,12 +2,12 @@ apiVersion: v2 | |
name: daemonset-app | ||
description: Default DaemonSet Helm Chart | ||
type: application | ||
version: 0.16.0 | ||
version: 0.16.1 | ||
appVersion: latest | ||
maintainers: | ||
- name: diranged | ||
email: [email protected] | ||
dependencies: | ||
- name: nd-common | ||
version: 0.3.1 | ||
version: 0.3.6 | ||
repository: file://../nd-common |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
{{/* | ||
This function generates an extended set of labels by combining the base labels | ||
from the "nd-common.labels" template with additional custom labels. | ||
|
||
The additional labels include: | ||
- helm.chart/name: Specifies the name of the chart (hardcoded as "daemonset-app"). | ||
- helm.chart/version: Includes the chart version dynamically from .Chart.Version. | ||
*/}} | ||
{{- define "daemonset-app.labels" -}} | ||
{{- $baseLabels := include "nd-common.labels" . | fromYaml -}} | ||
{{- $extendedLabels := merge $baseLabels (dict | ||
"helm.sh/chartName" "daemonset-app" | ||
"helm.sh/chartVersion" .Chart.Version | ||
Comment on lines
+12
to
+13
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Adding standup discussion comments for the record... I suggested we do not use the helm.sh namespace and instead use a namespace like helm.nextdoor.com or oss.nextdoor.com. This is because we are adding a new label that helm.sh themselves have not yet defined and therefore no API for it exists. In order to avoid any future naming collisions, I believe we should be name-spacing this new label use-case under our own namespace. This might be an over-optimization, so we decided to differ to status quo due to no strong opinions. cc: @diranged There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Follow up PR #351 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think that what we have is fine... |
||
) -}} | ||
{{- $extendedLabels | toYaml -}} | ||
{{- end -}} |
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.
thank you!