Files
k8s-starter-pack/apps/victoria-metrics/values.yaml
T

90 lines
2.8 KiB
YAML
Raw Normal View History

# Values for the upstream victoria-metrics-k8s-stack dependency. This cluster
# collects metrics only; durable storage and visualization run on the NetBird-
# connected VPS prd-vps-hel-01.ahmza.com (NetBird address 100.71.24.9).
victoria-metrics-k8s-stack:
# Identify this source if more clusters write to the same database later.
vmagent:
enabled: true
spec:
scrapeInterval: 30s
externalLabels:
cluster: gitops-starter
resources:
requests:
cpu: 100m
memory: 128Mi
limits:
memory: 512Mi
external:
vm:
# Queries are served from the VictoriaMetrics base URL. Remote write uses
# its Prometheus-compatible ingestion endpoint. NetBird encrypts the path
# between the Talos nodes and VPS, so no public endpoint is involved.
#
# The name resolves only through internal Technitium DNS (10.10.10.10),
# where an authoritative zone maps it to the VPS's NetBird address. If
# that address changes, update Technitium rather than this file.
read:
url: http://prd-vps-hel-01.ahmza.com:8428
write:
url: http://prd-vps-hel-01.ahmza.com:8428/api/v1/write
# Storage and UI already live on prd-vps-hel-01; do not duplicate them here.
vmsingle:
enabled: false
vmcluster:
enabled: false
vmdistributed:
enabled: false
grafana:
enabled: false
# Alert delivery is a separate follow-up once notification destinations are
# chosen. Disabling it also avoids deploying rules with nowhere to notify.
vmalert:
enabled: false
alertmanager:
enabled: false
defaultRules:
enabled: false
defaultDashboards:
enabled: false
# One node-exporter Pod runs on every node, including tainted control planes.
# Talos exposes the host root filesystem read-only; mount propagation is not
# needed and can be rejected by immutable hosts, so keep it disabled.
prometheus-node-exporter:
enabled: true
hostRootFsMount:
enabled: true
mountPropagation: None
resources:
requests:
cpu: 20m
memory: 32Mi
limits:
memory: 128Mi
# Talos binds the scheduler and controller-manager metrics endpoints to
# 127.0.0.1, and runs etcd as a host service rather than a Pod. Scraping them
# from vmagent would require exposing those control-plane ports on the LAN,
# so skip them; API server, kubelet, CoreDNS, and node metrics remain.
kubeScheduler:
enabled: false
kubeControllerManager:
enabled: false
kubeEtcd:
enabled: false
# kube-state-metrics reports desired/current Kubernetes object state (for
# example unavailable Deployment replicas), complementing host metrics.
kube-state-metrics:
enabled: true
resources:
requests:
cpu: 20m
memory: 64Mi
limits:
memory: 256Mi