Fix observability issues and refactor metrics stack to ArgoCD

- Resolved "connection refused" on startup probe by explicitly mapping management.server.port in application.yaml.
- Adjusted startupProbe to a 70s window (10s delay + 12 * 5s) to accommodate application initialization.
- Externalized VictoriaMetrics stack (Operator, Single, Agent, Alert) into separate ArgoCD Application manifests.
- Removed bundled VictoriaMetrics templates from the MovieNight Helm chart.
- Configured vmagent with Kubernetes pod-based service discovery for metrics scraping.
- Ensured consistency between Helm values and externalized observability components.

Co-authored-by: devitq <118541411+devitq@users.noreply.github.com>
This commit is contained in:
google-labs-jules[bot]
2026-05-23 00:30:37 +00:00
co-authored by devitq
parent 2d6012866b
commit 47baaf8fce
14 changed files with 150 additions and 497 deletions
+1 -17
View File
@@ -136,22 +136,6 @@ app.kubernetes.io/component: {{ $component }}
{{- if .Values.observability.grafana.datasource.url -}}
{{- .Values.observability.grafana.datasource.url -}}
{{- else -}}
{{- printf "http://%s.%s.svc:%v" (include "movienight.victoriaMetricsName" .) .Release.Namespace .Values.observability.victoriaMetrics.service.port -}}
{{- end -}}
{{- end -}}
{{- define "movienight.vmagentRemoteWriteURL" -}}
{{- if .Values.observability.vmagent.remoteWriteUrl -}}
{{- .Values.observability.vmagent.remoteWriteUrl -}}
{{- else -}}
{{- printf "http://%s:%v/api/v1/write" (include "movienight.victoriaMetricsName" .) .Values.observability.victoriaMetrics.service.port -}}
{{- end -}}
{{- end -}}
{{- define "movienight.backendMetricsTarget" -}}
{{- if .Values.backend.management.enabled -}}
{{- printf "%s-backend:%v" (include "movienight.fullname" .) .Values.backend.management.port -}}
{{- else -}}
{{- printf "%s-backend:%v" (include "movienight.fullname" .) .Values.backend.service.port -}}
{{- .Values.observability.victoriaMetrics.url -}}
{{- end -}}
{{- end -}}