operator: add VPA support to vmalert, vmalertmanager, vmagent, vlagent, vlsingle, vtsingle, vmsingle

[AndrewChubatiuk]

fixes #2252

---

Summary by cubic

Add VerticalPodAutoscaler support via a new spec.vpa field for vmagent, vmalert, vmalertmanager, vmsingle, vlsingle, vtsingle, vlagent, and vmanomaly. The operator now creates, updates, and deletes VPAs for these resources; enable with VM_VPA_API_ENABLED=true.

• New Features

  • New spec.vpa with validation across the listed CRDs; CRD schemas, docs, and deepcopy updated.
  • Operator reconciles VPAs per resource:
    • vmagent: targets the Deployment; invalid with daemonSetMode; with sharding, a VPA per shard.
    • vlagent: target follows workload — StatefulSet by default, DaemonSet when k8sCollector.enabled is true.
    • vmalert, vmsingle, vlsingle, vtsingle: target the Deployment.
    • vmalertmanager, vmanomaly: target the StatefulSet.
  • Removing spec.vpa deletes the corresponding VPA.

• Migration

  • Set VM_VPA_API_ENABLED=true on the operator; reconciliation errors if spec.vpa is set without it.
  • Add spec.vpa in your CRs to enable; remove it to disable.
  • For vmagent, do not set spec.vpa when daemonSetMode: true; with sharding, VPAs are created per shard automatically.

^{Written for commit 78fe37c. Summary will update on new commits.}

[cubic-dev-ai]

1 issue found across 20 files

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

1 issue found across 20 files (changes from recent commits).

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>