Go to file
Seth Call 3eb1042484 poke 2026-01-03 23:50:58 -06:00
docker healthchecks 2025-04-06 17:57:45 -05:00
k8s docker redis specificy 2026-01-03 23:31:30 -06:00
k8s-notes more 2025-04-06 17:58:43 -05:00
scripts Preparing for webrtc-be crash alerts 2025-12-13 14:53:22 -06:00
terraform bump to 32 k8s 2025-11-11 15:40:01 -06:00
.gitignore Go ahead and attempt loki again 2025-12-06 18:46:53 -06:00
NOTES.md healthcheck and monitoring 2025-10-05 17:43:16 -05:00
README.md poke 2026-01-03 23:50:58 -06:00
bitbucket-pipelines.yml Be sure to push argocd for production 2025-07-20 17:21:40 -05:00

README.md

README

This README would normally document whatever steps are necessary to get your application up and running.

What is this repository for?

Development Setup

  1. Install Pre-commit Hooks (Required for CRD management):
    ./scripts/setup-hooks.sh
    
    This ensures that k8s/crds/all-crds.yaml is automatically updated whenever you modify the monitoring Helm chart.

Monitoring Chart Patch (Critical)

The included chart k8s/monitoring/charts/kube-prometheus-stack-75.12.0.tgz is MANUALLY PATCHED.

Why? The upstream chart (v65.x+) introduced a field trackTimestampsStaleness in the ServiceMonitor CRD. Our cluster is running an older version of the Prometheus Operator/CRDs that does not support this field. The upstream chart renders this field unconditionally in some templates (specifically kubelet), causing ArgoCD sync to fail with a schema validation error ("field not declared in schema").

How was it patched?

  1. Unpacked the official kube-prometheus-stack-75.12.0.tgz.
  2. Modified templates/exporters/kubelet/servicemonitor.yaml.
  3. Wrapped trackTimestampsStaleness in a conditional block:
    {{- if .Values.kubelet.serviceMonitor.trackTimestampsStaleness }}
    trackTimestampsStaleness: {{ .Values.kubelet.serviceMonitor.trackTimestampsStaleness }}
    {{- end }}
    
  4. Repackaged the chart using tar -czf.
  5. Force added to git (git add -f) because charts/*.tgz is ignored.

When to delete? You can revert to the official upstream chart once the Prometheus Operator CRDs on the cluster are upgraded to a version that includes trackTimestampsStaleness in the ServiceMonitor schema (likely Prometheus Operator >= v0.68.0 or similar).

How do I get set up?

  • Summary of set up
  • Configuration
  • Dependencies
  • Database configuration
  • How to run tests
  • Deployment instructions

Contribution guidelines

  • Writing tests
  • Code review
  • Other guidelines

Who do I talk to?

  • Repo owner or admin
  • Other community or team contact

Apply terraform

Install ArgoCD

kubectl create namespace argocd kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml

Add Bitbucket SSH Key secret