fix: workaround for large CRDs in metrics

This commit is contained in:
Stefan Reimer 2022-04-08 17:25:23 +02:00
parent 8b18ec3920
commit f24a5c81c0
3 changed files with 4 additions and 4 deletions

View File

@ -26,4 +26,4 @@ README.md.gotmpl
*.patch *.patch
*.sh *.sh
*.py *.py
configs jsonnet

View File

@ -64,7 +64,7 @@ function _crds() {
# Only apply if there are actually any crds # Only apply if there are actually any crds
if [ -s $TMPDIR/crds.yaml ]; then if [ -s $TMPDIR/crds.yaml ]; then
kubectl apply -f $TMPDIR/crds.yaml kubectl apply -f $TMPDIR/crds.yaml --server-side
fi fi
} }

View File

@ -41,7 +41,7 @@ istio-ingress:
metrics: metrics:
enabled: false enabled: false
namespace: monitoring namespace: monitoring
targetRevision: 0.7.4 targetRevision: 0.8.0
istio: istio:
grafana: {} grafana: {}
prometheus: {} prometheus: {}
@ -49,7 +49,7 @@ metrics:
logging: logging:
enabled: false enabled: false
namespace: logging namespace: logging
targetRevision: 0.8.0 targetRevision: 0.7.19
argocd: argocd:
enabled: false enabled: false