feature: Allow "extraLabels" for vmauth in victoria-metrics-k8s-stack

[micw]

Chart name and version, where you feel a lack of requested feature chart: victoria-metrics-k8s-stack version: v0.052.0

Is your feature request related to a problem? Please describe.

VM can replace prometheus in most cases. One corner case is: auto detection by tools like "Lens". This is done by searching for custom labels. The chart lacks support for this for the "vmauth" ressource. So either a custom ressource is needed or the deployment of a separate vmauth instance. See https://github.com/lensapp/lens/issues/5837#issuecomment-2988441760 for an example

Describe the solution you'd like Like vmauth.annotations, also support vmauth.extraLabels

Describe alternatives you've considered Deploy a custom instance of vmauth (either as ressource for the operator or via the vmauth chart)

Additional context Nothing to say here.

[AndrewChubatiuk]

have you tried changing .Values.vmauth.spec.serviceSpec.metadata.labels? as it's mentioned in doc all vmauth.spec variables can be found here

[AndrewChubatiuk]

hey @micw have you tried suggestion from comment above?

[micw]

That gave me: Error: UPGRADE FAILED: failed to create resource: VMAuth.operator.victoriametrics.com "infra-metrics" is invalid: spec.serviceSpec.spec: Required value

So I tried .Values.vmauth.spec.serviceSpec.**spec.**metadata.labels - that created an additional service but without the labels...

[AndrewChubatiuk]

right, serviceSpec is for additional k8s service. please try chart version 0.55.1 and set labels using .Values.vmauth.labels property. this will set labels to all vmauth resources. there's no option at the moment to set labels for vmauth service only.

[AndrewChubatiuk]

hey @micw have you tried latest k8s stack chart version and set .Values.vmauth.labels?

[AndrewChubatiuk]

alternatively you can use a solution from this issue

[AndrewChubatiuk]

closing this as answered, please open a new issue if you still have questions or issues