Mention Prometheus data retention in docs

This commit is contained in:
stefanprodan
2019-07-04 15:07:05 +03:00
parent c4b066c845
commit 61fe78a982
2 changed files with 5 additions and 1 deletions
+2 -1
View File
@@ -71,7 +71,8 @@ version-set:
sed -i '' "s/tag: $$current/tag: $$next/g" charts/flagger/values.yaml && \
sed -i '' "s/appVersion: $$current/appVersion: $$next/g" charts/flagger/Chart.yaml && \
sed -i '' "s/version: $$current/version: $$next/g" charts/flagger/Chart.yaml && \
echo "Version $$next set in code, deployment and charts"
sed -i '' "s/newTag: $$current/newTag: $$next/g" kustomize/base/flagger/kustomization.yaml && \
echo "Version $$next set in code, deployment, chart and kustomize"
version-up:
@next="$(VERSION_MINOR).$$(($(PATCH) + 1))" && \
@@ -147,6 +147,9 @@ kubectl apply -k github.com/weaveworks/flagger/kustomize/kubernetes
This deploys Flagger and Prometheus in the `flagger-system` namespace,
sets the metrics server URL to `http://flagger-prometheus.flagger-system:9090` and the mesh provider to `kubernetes`.
The Prometheus instance has a two hours data retention and is configured to scrape all pods in your cluster that
have the `prometheus.io/scrape: "true"` annotation.
To target a specific provider you need to specify it in the canary custom resource:
```yaml