rudderlabs / rudderstack-helm

Open-source, warehouse-first Customer Data Pipeline and Segment-alternative. Collects and routes clickstream data and builds your customer data lake on your data warehouse.
MIT License
61 stars 48 forks source link

feat: add optional additional labels to resources #66

Closed bdashrad closed 9 months ago

bdashrad commented 1 year ago

Description of the change

Allow adding arbitrary labels to different resources in the chart. Useful for monitoring and other things, and fairly common. I followed example code from the ingress-nginx and argo-cd charts.

Type of change

Related issues

Checklists

Development

Code review

bdashrad commented 1 year ago

@rahulkumark

service account and telegraf sidecar aren't configured to use common labels.

I didn't add additional labels to the service account, but will push that change now.

Telegraf sidecar is a container added to the pod, so it still gets pod labels specified above.

Common labels are also not configured on postgres sub-chart resources.

The postgres chart is a copy of the bitnami postgresql chart, embedded in the repo, and already supports adding extra labels (I add them on our own deployment here: https://github.com/rudderlabs/rudderstack-helm/blob/master/charts/postgresql/values.yaml#L296)

Instead of adding a new commonLabels section to the postgres chart, I'd prefer to see the chart use https://helm.sh/docs/helm/helm_dependency/ in Chart.yaml, pointing to the actual upstream chart instead of copying it's contents into charts/. This means not having to maintain a separate copy of this upstream chart, and ensuring we get bug fixes instead of relying on manual updates.

bdashrad commented 10 months ago

Hello! Looking for an update here 😄

gitcommitshow commented 9 months ago

Thanks Brad for the contribution and the followup. I am discussing with the team about how to move this one forward. Will get back to you.