github/flagger
1
0
Fork 0
mirror of https://github.com/fluxcd/flagger.git synced 2026-04-15 06:57:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

Change GitHub raw URLs to Weaveworks org

Browse Source
This commit is contained in:
stefanprodan
2019-03-23 13:38:57 +02:00
parent 39fd3d46ba
commit d222dd1069
14 changed files with 41 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
docs/gitbook/install/flagger-install-on-eks-appmesh.md
View File

@@ -125,12 +125,6 @@ Install the App Mesh sidecar injector in the `appmesh-system` namespace:
The above script generates a certificate signed by Kubernetes CA,
registers the App Mesh mutating webhook and deploys the injector.
Deploy Prometheus in the `appmesh-system` namespace:
```bash
kubectl apply -f ./prometheus
```
Create a mesh called global in the `appmesh-system` namespace:
```bash
@@ -145,7 +139,20 @@ kubectl -n appmesh-system describe mesh
Status:
Mesh Condition:
Status: True
Type: Active
Type: MeshActive
```
### Install Prometheus
In order to expose the App Mesh metrics to Flagger,
you'll need to use Prometheus to scrapes the Envoy sidecars.
Deploy Prometheus in the `appmesh-system` namespace:
```bash
REPO=https://raw.githubusercontent.com/weaveworks/flagger/master
kubectl apply -f ${REPO}/artifacts/eks/appmesh-prometheus.yaml
```
### Install Flagger and Grafana
@@ -162,7 +169,7 @@ Deploy Flagger in the _**appmesh-system**_ namespace:
helm upgrade -i flagger flagger/flagger \
--namespace=appmesh-system \
--set meshProvider=appmesh \
--set metricsServer=http://prometheus.appmesh:9090
--set metricsServer=http://prometheus.appmesh-system:9090
```
You can install Flagger in any namespace as long as it can talk to the Istio Prometheus service on port 9090.

8
docs/gitbook/install/flagger-install-on-google-cloud.md
View File

@@ -2,7 +2,7 @@
This guide walks you through setting up Flagger and Istio on Google Kubernetes Engine.
![GKE Cluster Overview](https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/diagrams/flagger-gke-istio.png)
![GKE Cluster Overview](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-gke-istio.png)
### Prerequisites
@@ -208,12 +208,12 @@ stable/cert-manager
### Istio Gateway TLS setup
![Istio Let's Encrypt](https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/diagrams/istio-cert-manager-gke.png)
![Istio Let's Encrypt](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/istio-cert-manager-gke.png)
Create a generic Istio Gateway to expose services outside the mesh on HTTPS:
```bash
REPO=https://raw.githubusercontent.com/stefanprodan/flagger/master
REPO=https://raw.githubusercontent.com/weaveworks/flagger/master
kubectl apply -f ${REPO}/artifacts/gke/istio-gateway.yaml
```
@@ -332,7 +332,7 @@ Because Flagger uses the Istio HTTP metrics to run the canary analysis you have
Prometheus configuration that's similar to the one that comes with the official Istio Helm chart.
```bash
REPO=https://raw.githubusercontent.com/stefanprodan/flagger/master
REPO=https://raw.githubusercontent.com/weaveworks/flagger/master
kubectl apply -f ${REPO}/artifacts/gke/istio-prometheus.yaml
```

2
docs/gitbook/install/flagger-install-on-kubernetes.md
View File

@@ -132,7 +132,7 @@ helm upgrade -i flagger-loadtester flagger/loadtester \
Deploy with kubectl:
```bash
export REPO=https://raw.githubusercontent.com/stefanprodan/flagger/master
export REPO=https://raw.githubusercontent.com/weaveworks/flagger/master
kubectl -n test apply -f ${REPO}/artifacts/loadtester/deployment.yaml
kubectl -n test apply -f ${REPO}/artifacts/loadtester/service.yaml