video-iac/k8s
Seth Call e46c9146de udpdate some things 2026-02-20 10:37:31 -06:00
..
applications fix 2026-02-16 15:22:33 -06:00
argocd try this 2026-02-08 16:38:58 -06:00
authelia udpdate some things 2026-02-20 10:37:31 -06:00
cert-manager update staging to have a second cluster and better procss isolation 2026-01-06 06:04:29 -06:00
console fix 2026-02-19 09:41:29 -06:00
coturn update staging to have a second cluster and better procss isolation 2026-01-06 06:04:29 -06:00
coturn-dns matching prod to staging 2026-01-08 04:55:26 -06:00
crds Try to sync crds always with pre-commit 2025-12-12 15:31:23 -06:00
external-dns apply 2026-02-15 18:28:41 -06:00
loki log level 2026-01-16 16:15:03 -06:00
monitoring Bump webrtc and the crash log reporter link for loki to have a time range 2026-01-12 21:48:08 -06:00
probers fix(k8s): update metrics-server to 7.2.14 and disable broken probers 2026-01-31 10:13:40 -06:00
promtail update staging to have a second cluster and better procss isolation 2026-01-06 06:04:29 -06:00
webrtc-be bump coturn 2026-02-08 15:42:15 -06:00
DEBUGGING.md Adding loki support 2025-12-11 22:57:03 -06:00
README.md Apply grafana dashboard sidecare 2025-12-07 15:37:46 -06:00
activate-stg Adding loki support 2025-12-11 22:57:03 -06:00

README.md

Kubernetes Configuration

This directory contains Kubernetes manifests and configuration for the video infrastructure.

Managing CRDs

The file all-crds.yaml contains all Custom Resource Definitions (CRDs) required by the monitoring stack (Prometheus Operator).

When to update CRDs

You should regenerate all-crds.yaml by running scripts/update-crds.sh when:

  1. Upgrading the kube-prometheus-stack Helm chart: If you bump the chart version in k8s/monitoring/Chart.yaml and update the dependencies, you must also update the CRDs to match the new version.

  2. Missing CRD fields: If you encounter errors like field not declared in schema during ArgoCD syncs, it likely means the installed CRDs are outdated.

  3. Apply the CRDs: Since Helm does not manage CRD upgrades, you must apply the updated CRDs manually. You may need --force-conflicts if ArgoCD previously managed these resources:

    kubectl apply --server-side --force-conflicts -f k8s/all-crds.yaml
    
  4. Commit and Push: Commit the updated k8s/all-crds.yaml to the repository.

    git add k8s/all-crds.yaml
    git commit -m "Update Prometheus CRDs"
    git push
    

How to update

Run the update script from the repository root:

./scripts/update-crds.sh

This script extracts the CRDs from the local kube-prometheus-stack chart package and concatenates them into k8s/all-crds.yaml.