# What this PR does Now it is possible to change engine deployment update strategy in values.yaml. ## Which issue(s) this PR fixes This is due to #334 and #316, as with rolling update, race conditions might happen when there is still an old engine pod running. Co-authored-by: Joey Orlando <joey.orlando@grafana.com> |
||
|---|---|---|
| .. | ||
| oncall | ||
| cr.yaml | ||
| ct.yaml | ||
| kind.yml | ||
| README.md | ||
| simple.yml | ||
| values-arm64.yml | ||
| values-local-image.yml | ||
How to run the chart locally
-
Create the cluster with kind
Make sure ports 30001 and 30002 are free on your machine
kind create cluster --image kindest/node:v1.24.7 --config kind.yml -
Install the helm chart
helm install helm-testing \ ../oncall --wait --timeout 30m \ --wait-for-jobs \ --values ci/simple.yml \ --values ci/values-arm64.yml -
Get credentials
echo "\n\nOpen Grafana on localhost:30002 with credentials - user: admin, password: $(kubectl get secret --namespace default helm-testing-grafana -o jsonpath="{.data.admin-password}" | base64 --decode ; echo)" echo "Open Plugins -> Grafana OnCall -> fill form: backend url: localhost:30001, grafana url: localhost: 30001, token below" export POD_NAME=$(kubectl get pods --namespace default -l "app.kubernetes.io/name=oncall,app.kubernetes.io/instance=helm-testing,app.kubernetes.io/component=engine" -o jsonpath="{.items[0].metadata.name}") -
Clean up
kind delete cluster