|
|
||
|---|---|---|
| .. | ||
| applications | ||
| argocd | ||
| cert-manager | ||
| coturn | ||
| coturn-dns | ||
| external-dns | ||
| loki | ||
| monitoring | ||
| probers | ||
| promtail | ||
| webrtc-be | ||
| README.md | ||
| all-crds.yaml | ||
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:
- Upgrading the
kube-prometheus-stackHelm chart: If you bump the chart version ink8s/monitoring/Chart.yamland update the dependencies, you must also update the CRDs to match the new version. - Missing CRD fields: If you encounter errors like
field not declared in schemaduring ArgoCD syncs, it likely means the installed CRDs are outdated.
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.