Skip to content

Conversation

@VitoriaOrtega
Copy link

PR Description

This PR introduces the use of the commonLabels field in the Alloy Helm chart.
It allows users to define a common set of labels that will be applied to all resources generated by the chart (Deployments, Services, ConfigMaps, etc.), ensuring consistent metadata and easier resource management.

Key Changes

  • Added the new field commonLabels in values.yaml.

  • Updated Helm template helpers to render commonLabels across all chart resources.

  • Updated documentation (README.md) to describe the new value.

  • Bumped chart version to 1.3.1.

  • Updated CHANGELOG.md accordingly.

Example Usage:

commonLabels:
  app.kubernetes.io/part-of: monitoring
  environment: production
  team: platform

This will apply the above labels to all resources created by the chart.

Benefits

  • Enables better alignment with GitOps practices and resource tracking.

  • Simplifies applying organization-wide labels such as team, environment, or owner.

  • Improves observability and filtering across Kubernetes and monitoring tools.

Which issue(s) this PR fixes

N/A

PR Checklist

  • CHANGELOG.md updated
  • Documentation added
  • Chart version bumped

@VitoriaOrtega VitoriaOrtega requested a review from a team as a code owner October 8, 2025 19:34
@CLAassistant
Copy link

CLAassistant commented Oct 8, 2025

CLA assistant check
All committers have signed the CLA.

Comment on lines +13 to +21
1.3.1 (2025-10-08)
----------

### Other changes

- Update values to use commonLabels

------------------

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should not create a new version but put this entry under Unreleased

Comment on lines +204 to +206
# -- Add additional label to all resources
commonLabels: {}

Copy link
Contributor

@kalleep kalleep Oct 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This feels like the wrong place to put this, everything else under controller will only affect e.g. daemonset, statefulset etc but this would affect all resources

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants