Setting Alertmanager's config-reloader container resources in victoria-metrics-k8s-stack values

[arseny-zinchenko]

Hello.
I'm want to update Alertmanager's config-reloader container resources.requests.
In my values file I have the following resources:

  alertmanager:
    enabled: true
    persistence:
      enabled: true
      storageClass: "gp2-retain"
      size: 100Mi
    
    spec:
      replicaCount: 1
      resources:
        requests:
          memory: 50Mi
          cpu: 10m

But it's applied only to the Alertmanager's container, while config-reloader is left untouched:

$ kk describe sts vmalertmanager-vm-k8s-stack
...
  Containers:
   alertmanager:
    Image:       prom/alertmanager:v0.25.0
    ...
    Requests:
      cpu:      10m
      memory:   50Mi
      ...
   config-reloader:
    Image:      jimmidyson/configmap-reload:v0.3.0
    ...
    Limits:
      cpu:     100m
      memory:  25Mi
    Requests:
      cpu:        100m
      memory:     25Mi
....

I can't see any mentions of the config-reloader configuration possible in the values.yaml or in the vmalertmanagerspec Docs.

So, is there any way to change it?

And the same question is about vmagent-vm-k8s-stack and vmalert-vm-k8s-stack Deployments.

[Haleygo]

Hello,
you can change them by setting env VM_VMALERTMANAGER_CONFIGRELOADERxxx in operator, see this doc for more available envs.