config-reloader throttling of CPU in vmagent

VictoriaMetrics / operator

Kubernetes operator for Victoria Metrics

Apache License 2.0

422 stars 140 forks source link

config-reloader throttling of CPU in vmagent #1079

Closed stevenhong127 closed 2 weeks ago

stevenhong127 commented 3 weeks ago

`Status: FIRING 🔥 Annotations:

summary: Processes experience elevated CPU throttling.
description: 33.33% throttling of CPU in namespace monitoring for container config-reloader in pod vmagent-***. Details:
container: config-reloader `

When deploying VMAgent using vm-operator, it is currently not possible to specify the resource limits for the config-reloader, which often leads to CPU throttling alerts for VMAgent. Is there a plan to improve and add support for this in the future?

f41gh7 commented 3 weeks ago

Hello,

It's possible to globally rise limit per CRD object with env variables for operator: VM_VMALERTDEFAULT_CONFIGRELOADERCPU 100m VM_VMAGENTDEFAULT_CONFIGRELOADERCPU 100m VM_VMAUTHDEFAULT_CONFIGRELOADERCPU 100m VM_VMALERTMANAGER_CONFIGRELOADERCPU 100m https://docs.victoriametrics.com/operator/vars/

Or patch value directly per CRD object:

kind: VMAgent
spec:
  containers:
  - name: config-reloader
     resources:
       limits:
          cpu: 200m

stevenhong127 commented 3 weeks ago

Hello,

It's possible to globally rise limit per CRD object with env variables for operator: VM_VMALERTDEFAULT_CONFIGRELOADERCPU 100m VM_VMAGENTDEFAULT_CONFIGRELOADERCPU 100m VM_VMAUTHDEFAULT_CONFIGRELOADERCPU 100m VM_VMALERTMANAGER_CONFIGRELOADERCPU 100m https://docs.victoriametrics.com/operator/vars/

Or patch value directly per CRD object:
kind: VMAgent
spec:
  containers:
  - name: config-reloader
     resources:
       limits:
          cpu: 200m

got it, thank you.