Skip to content
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

Helm Chart app.labels are not applied to all deployed resources #9158

Open
Moglum opened this issue Jun 13, 2024 · 1 comment
Open

Helm Chart app.labels are not applied to all deployed resources #9158

Moglum opened this issue Jun 13, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@Moglum
Copy link

Moglum commented Jun 13, 2024

What happened?

The Helm Chart value app.labels is described as:

# Common labels & annotations shared across all deployed resources

But it's only applied to ServiceMonitor, NetworkPolicy, and PodDisruptionBudget

What did you expect to happen?

The Labels should get applied to all Deployments, Services, ConfigMaps and arguably even Resources deployed by the Subcharts.

How can we reproduce it (as minimally and precisely as possible)?

Template the Helm Chart with the following values snippet

app:
  labels:
    foo: bar

and look at the resulting manifests.

Anything else we need to know?

An easy fix would be to include .Values.app.labels into kubernetes-dashboard.labels here


and removing the 3 occurrences where .Values.app.labels are used directly.

If the labels should be propagated to the subcharts (which I think they should) that could be also easily done in values.yaml

I'd be happy to submit a PR for this if you agree with the solution.
Thank you in advance

What browsers are you seeing the problem on?

No response

Kubernetes Dashboard version

7.5.0

Kubernetes version

any

Dev environment

No response

@Moglum Moglum added the kind/bug Categorizes issue or PR as related to a bug. label Jun 13, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants