You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The problem is that we used to set labels on all deployed kubernetes objects (services, service accounts, etc) with the loki helm chart v 2.16.0, but after migrating to 4.8.0 this is no longer possible. We use these labels to label all objects that are part of the deployment for the same environment.
Describe the solution you'd like
It would be interesting if we could add some general labels everywhere where the template uses include "loki.labels". e.g. by adding Values.loki.genericLabels. Now it is only possible to add labels to pods with Values.loki.podLabels.
Describe alternatives you've considered
As an alternative I could add the labels with kubectl command after the deployment, but that would complicate the loki deployment.
Additional context
Not required, should be clear with the description.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The problem is that we used to set labels on all deployed kubernetes objects (services, service accounts, etc) with the loki helm chart v 2.16.0, but after migrating to 4.8.0 this is no longer possible. We use these labels to label all objects that are part of the deployment for the same environment.
Describe the solution you'd like
It would be interesting if we could add some general labels everywhere where the template uses include "loki.labels". e.g. by adding Values.loki.genericLabels. Now it is only possible to add labels to pods with Values.loki.podLabels.
Describe alternatives you've considered
As an alternative I could add the labels with kubectl command after the deployment, but that would complicate the loki deployment.
Additional context
Not required, should be clear with the description.
The text was updated successfully, but these errors were encountered: