Allow deployment labels to use "grafana-operator.labels" instead of just "grafana-operator-labels.selectorLabels" #1546
Labels
enhancement
New feature or request
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Is your feature request related to a problem? Please describe.
We have a set of labels that we need to apply to our cluster in order for our service to deploy (enforced by keda), and we would like to not have to disable these checks for this operator.
We have to keep a copy of your chart local and change the selectorLabels to
labels
to get the deployment to pass.(If applicable)If your feature request solves a bug please provide a link to the community issue
No
Describe the solution you'd like
We would love a way to allow the user to select which set of labels to use for the deployment template, or alternatively use the labels as the default for the Pod
Describe alternatives you've considered
We are currently copying your template into our own private repo so we can update the labels field.
Additional context
We know our requirements are not to everyone's like, which is why I'm suggesting having a switch to allow one set of values or the other
Existing solutions
Not so much an existing solution, but something that's easy to implement
Proposed change
#1560
The text was updated successfully, but these errors were encountered: