Add VictoriaMetrics as a second metrics backend, configure Grafana to use it by default, and expose the monitoring endpoints on internal routes. Include the generated Prometheus-compatible scrape configuration, alert evaluation, and a one-shot vmctl history import. Add generic Kubernetes workload and route templates.
The scrape config reads the existing Uptime Kuma metrics password from a namespace-local Secret; victoria-secrets.yaml.example documents the required key without storing credentials. Fix duplicate DNS fields in the Deployment template.
Validation: rendered kube-prometheus-stack 86.2.3 with the repository values and confirmed the Prometheus ServiceAccount and ClusterRole names used by the manifests; yamllint, Prettier, kubeconform, and git diff --check passed. The VictoriaMetrics config dry-run could not run because the local Docker daemon is unavailable. No cluster changes were applied.
Add VictoriaMetrics as a second metrics backend, configure Grafana to use it by default, and expose the monitoring endpoints on internal routes. Include the generated Prometheus-compatible scrape configuration, alert evaluation, and a one-shot vmctl history import. Add generic Kubernetes workload and route templates.
The scrape config reads the existing Uptime Kuma metrics password from a namespace-local Secret; `victoria-secrets.yaml.example` documents the required key without storing credentials. Fix duplicate DNS fields in the Deployment template.
Validation: rendered kube-prometheus-stack 86.2.3 with the repository values and confirmed the Prometheus ServiceAccount and ClusterRole names used by the manifests; yamllint, Prettier, kubeconform, and `git diff --check` passed. The VictoriaMetrics config dry-run could not run because the local Docker daemon is unavailable. No cluster changes were applied.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Add VictoriaMetrics as a second metrics backend, configure Grafana to use it by default, and expose the monitoring endpoints on internal routes. Include the generated Prometheus-compatible scrape configuration, alert evaluation, and a one-shot vmctl history import. Add generic Kubernetes workload and route templates.
The scrape config reads the existing Uptime Kuma metrics password from a namespace-local Secret;
victoria-secrets.yaml.exampledocuments the required key without storing credentials. Fix duplicate DNS fields in the Deployment template.Validation: rendered kube-prometheus-stack 86.2.3 with the repository values and confirmed the Prometheus ServiceAccount and ClusterRole names used by the manifests; yamllint, Prettier, kubeconform, and
git diff --checkpassed. The VictoriaMetrics config dry-run could not run because the local Docker daemon is unavailable. No cluster changes were applied.