victoria-metrics-agent:
  # Ships to victoria-metrics-single. The write path is /api/v1/write,
  # the same endpoint any Prometheus remote_write client uses — this is
  # the one config line that actually wires the two components together;
  # the chart names don't imply it on their own.
  #
  # Cluster-internal Service DNS: this call happens from a pod, so
  # CoreDNS resolves it. Same reasoning as everywhere else in this
  # project that a Service name (not an Ingress hostname) is correct
  # here — see claude.md's registry-hostname convention for the one case
  # where cluster DNS specifically does NOT work (a node-level pull),
  # which does not apply to this pod-to-pod write.
  remoteWrite:
    - url: http://victoria-metrics-single-server.monitoring.svc.cluster.local:8428/api/v1/write

  # config.scrape_configs is left at the chart's own default — it already
  # includes kubernetes-nodes-cadvisor (kubelet's cAdvisor endpoint,
  # comment literally says "COPY from Prometheus helm chart") and
  # kubernetes-service-endpoints (the prometheus.io/scrape annotation
  # convention node-exporter's Service carries). Nothing here needs a
  # scrape target the chart doesn't already define out of the box.

  resources:
    requests:
      cpu: 25m
      memory: 64Mi
    limits:
      memory: 192Mi