From d222dd1069359405c5ffc9ed50b733a5f5e1593b Mon Sep 17 00:00:00 2001 From: stefanprodan Date: Sat, 23 Mar 2019 13:38:57 +0200 Subject: [PATCH] Change GitHub raw URLs to Weaveworks org --- charts/flagger/Chart.yaml | 2 +- charts/grafana/Chart.yaml | 2 +- charts/grafana/README.md | 2 +- charts/loadtester/Chart.yaml | 2 +- docs/gitbook/README.md | 2 +- docs/gitbook/how-it-works.md | 8 +++---- .../install/flagger-install-on-eks-appmesh.md | 23 ++++++++++++------- .../flagger-install-on-google-cloud.md | 8 +++---- .../install/flagger-install-on-kubernetes.md | 2 +- docs/gitbook/tutorials/canary-helm-gitops.md | 12 +++++----- docs/gitbook/usage/ab-testing.md | 4 ++-- docs/gitbook/usage/alerting.md | 4 ++-- docs/gitbook/usage/monitoring.md | 2 +- docs/gitbook/usage/progressive-delivery.md | 2 +- 14 files changed, 41 insertions(+), 34 deletions(-) diff --git a/charts/flagger/Chart.yaml b/charts/flagger/Chart.yaml index 2a2c3f8d..5491e73c 100644 --- a/charts/flagger/Chart.yaml +++ b/charts/flagger/Chart.yaml @@ -6,7 +6,7 @@ kubeVersion: ">=1.11.0-0" engine: gotpl description: Flagger is a Kubernetes operator that automates the promotion of canary deployments using Istio routing for traffic shifting and Prometheus metrics for canary analysis. home: https://docs.flagger.app -icon: https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/logo/flagger-icon.png +icon: https://raw.githubusercontent.com/weaveworks/flagger/master/docs/logo/flagger-icon.png sources: - https://github.com/weaveworks/flagger maintainers: diff --git a/charts/grafana/Chart.yaml b/charts/grafana/Chart.yaml index b515e7a0..9c985be8 100644 --- a/charts/grafana/Chart.yaml +++ b/charts/grafana/Chart.yaml @@ -3,7 +3,7 @@ name: grafana version: 1.0.0 appVersion: 5.4.3 description: Grafana dashboards for monitoring Flagger canary deployments -icon: https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/logo/flagger-icon.png +icon: https://raw.githubusercontent.com/weaveworks/flagger/master/docs/logo/flagger-icon.png home: https://flagger.app sources: - https://github.com/weaveworks/flagger diff --git a/charts/grafana/README.md b/charts/grafana/README.md index 913436c2..15c54f98 100644 --- a/charts/grafana/README.md +++ b/charts/grafana/README.md @@ -2,7 +2,7 @@ Grafana dashboards for monitoring progressive deployments powered by Istio, Prometheus and Flagger. -![flagger-grafana](https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/screens/grafana-canary-analysis.png) +![flagger-grafana](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/grafana-canary-analysis.png) ## Prerequisites diff --git a/charts/loadtester/Chart.yaml b/charts/loadtester/Chart.yaml index 01a00e86..9743f58b 100644 --- a/charts/loadtester/Chart.yaml +++ b/charts/loadtester/Chart.yaml @@ -6,7 +6,7 @@ kubeVersion: ">=1.11.0-0" engine: gotpl description: Flagger's load testing services based on rakyll/hey that generates traffic during canary analysis when configured as a webhook. home: https://docs.flagger.app -icon: https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/logo/flagger-icon.png +icon: https://raw.githubusercontent.com/weaveworks/flagger/master/docs/logo/flagger-icon.png sources: - https://github.com/weaveworks/flagger maintainers: diff --git a/docs/gitbook/README.md b/docs/gitbook/README.md index 670620e6..a5e983ee 100644 --- a/docs/gitbook/README.md +++ b/docs/gitbook/README.md @@ -13,7 +13,7 @@ Flagger implements a control loop that gradually shifts traffic to the canary wh indicators like HTTP requests success rate, requests average duration and pods health. Based on analysis of the **KPIs** a canary is promoted or aborted, and the analysis result is published to **Slack**. -![Flagger overview diagram](https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/diagrams/flagger-canary-overview.png) +![Flagger overview diagram](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-canary-overview.png) Flagger can be configured with Kubernetes custom resources and is compatible with any CI/CD solutions made for Kubernetes. Since Flagger is declarative and reacts to Kubernetes events, diff --git a/docs/gitbook/how-it-works.md b/docs/gitbook/how-it-works.md index 03378a7a..bd4ba089 100644 --- a/docs/gitbook/how-it-works.md +++ b/docs/gitbook/how-it-works.md @@ -4,7 +4,7 @@ a horizontal pod autoscaler \(HPA\) and creates a series of objects \(Kubernetes deployments, ClusterIP services and Istio virtual services\) to drive the canary analysis and promotion. -![Flagger Canary Process](https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/diagrams/flagger-canary-hpa.png) +![Flagger Canary Process](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-canary-hpa.png) ### Canary Custom Resource @@ -251,7 +251,7 @@ and for backend HTTP APIs that are accessible only from inside the mesh. ### Canary Stages -![Flagger Canary Stages](https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/diagrams/flagger-canary-steps.png) +![Flagger Canary Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-canary-steps.png) A canary deployment is triggered by changes in any of the following objects: @@ -579,12 +579,12 @@ Flagger metric checks will fail with "no values found for metric istio_requests_ Flagger comes with a load testing service based on [rakyll/hey](https://github.com/rakyll/hey) that generates traffic during analysis when configured as a webhook. -![Flagger Load Testing Webhook](https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/diagrams/flagger-load-testing.png) +![Flagger Load Testing Webhook](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-load-testing.png) First you need to deploy the load test runner in a namespace with Istio sidecar injection enabled: ```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 diff --git a/docs/gitbook/install/flagger-install-on-eks-appmesh.md b/docs/gitbook/install/flagger-install-on-eks-appmesh.md index 4fed0684..19552fa8 100644 --- a/docs/gitbook/install/flagger-install-on-eks-appmesh.md +++ b/docs/gitbook/install/flagger-install-on-eks-appmesh.md @@ -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. diff --git a/docs/gitbook/install/flagger-install-on-google-cloud.md b/docs/gitbook/install/flagger-install-on-google-cloud.md index bdb0da57..94a2f7b7 100644 --- a/docs/gitbook/install/flagger-install-on-google-cloud.md +++ b/docs/gitbook/install/flagger-install-on-google-cloud.md @@ -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 ``` diff --git a/docs/gitbook/install/flagger-install-on-kubernetes.md b/docs/gitbook/install/flagger-install-on-kubernetes.md index 2a07ff62..73120559 100644 --- a/docs/gitbook/install/flagger-install-on-kubernetes.md +++ b/docs/gitbook/install/flagger-install-on-kubernetes.md @@ -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 diff --git a/docs/gitbook/tutorials/canary-helm-gitops.md b/docs/gitbook/tutorials/canary-helm-gitops.md index a8a73b49..9117f1ff 100644 --- a/docs/gitbook/tutorials/canary-helm-gitops.md +++ b/docs/gitbook/tutorials/canary-helm-gitops.md @@ -29,7 +29,7 @@ You can find the chart source [here](https://github.com/stefanprodan/flagger/tre Create a test namespace with Istio sidecar injection enabled: ```bash -export REPO=https://raw.githubusercontent.com/stefanprodan/flagger/master +export REPO=https://raw.githubusercontent.com/weaveworks/flagger/master kubectl apply -f ${REPO}/artifacts/namespaces/test.yaml ``` @@ -79,7 +79,7 @@ Flagger will route all traffic to the primary pods and scale to zero the `fronte Open your browser and navigate to the frontend URL: -![Podinfo Frontend](https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/screens/demo-frontend.png) +![Podinfo Frontend](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/demo-frontend.png) Now let's install the `backend` release without exposing it outside the mesh: @@ -104,7 +104,7 @@ frontend Initialized 0 2019-02-12T17:50:50Z Click on the ping button in the `frontend` UI to trigger a HTTP POST request that will reach the `backend` app: -![Jaeger Tracing](https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/screens/demo-frontend-jaeger.png) +![Jaeger Tracing](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/demo-frontend-jaeger.png) We'll use the `/echo` endpoint (same as the one the ping button calls) to generate load on both apps during a canary deployment. @@ -155,7 +155,7 @@ You can monitor the canary deployment with Grafana. Open the Flagger dashboard, select `test` from the namespace dropdown, `frontend-primary` from the primary dropdown and `frontend` from the canary dropdown. -![Flagger Grafana Dashboard](https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/screens/demo-frontend-dashboard.png) +![Flagger Grafana Dashboard](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/demo-frontend-dashboard.png) Now trigger a canary deployment for the `backend` app, but this time you'll change a value in the configmap: @@ -213,7 +213,7 @@ Copying backend.test template spec to backend-primary.test Promotion completed! Scaling down backend.test ``` -![Flagger Grafana Dashboard](https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/screens/demo-backend-dashboard.png) +![Flagger Grafana Dashboard](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/demo-backend-dashboard.png) If the number of failed checks reaches the canary analysis threshold, the traffic is routed back to the primary, the canary is scaled to zero and the rollout is marked as failed. @@ -237,7 +237,7 @@ In the [GitOps model](https://www.weave.works/technologies/gitops/), any change to production must be committed in source control prior to being applied on the cluster. This way rollback and audit logs are provided by Git. -![Helm GitOps Canary Deployment](https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/diagrams/flagger-flux-gitops.png) +![Helm GitOps Canary Deployment](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-flux-gitops.png) In order to apply the GitOps pipeline model to Flagger canary deployments you'll need a Git repository with your workloads definitions in YAML format, diff --git a/docs/gitbook/usage/ab-testing.md b/docs/gitbook/usage/ab-testing.md index 1a67ecc5..01142969 100644 --- a/docs/gitbook/usage/ab-testing.md +++ b/docs/gitbook/usage/ab-testing.md @@ -6,12 +6,12 @@ Besides weighted routing, Flagger can be configured to route traffic to the cana In an A/B testing scenario, you'll be using HTTP headers or cookies to target a certain segment of your users. This is particularly useful for frontend applications that require session affinity. -![Flagger A/B Testing Stages](https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/diagrams/flagger-abtest-steps.png) +![Flagger A/B Testing Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-abtest-steps.png) Create a test namespace with Istio sidecar injection enabled: ```bash -export REPO=https://raw.githubusercontent.com/stefanprodan/flagger/master +export REPO=https://raw.githubusercontent.com/weaveworks/flagger/master kubectl apply -f ${REPO}/artifacts/namespaces/test.yaml ``` diff --git a/docs/gitbook/usage/alerting.md b/docs/gitbook/usage/alerting.md index 27a475d3..4c13e68e 100644 --- a/docs/gitbook/usage/alerting.md +++ b/docs/gitbook/usage/alerting.md @@ -15,12 +15,12 @@ helm upgrade -i flagger flagger/flagger \ Once configured with a Slack incoming **webhook**, Flagger will post messages when a canary deployment has been initialised, when a new revision has been detected and if the canary analysis failed or succeeded. -![flagger-slack](https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/screens/slack-canary-notifications.png) +![flagger-slack](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/slack-canary-notifications.png) A canary deployment will be rolled back if the progress deadline exceeded or if the analysis reached the maximum number of failed checks: -![flagger-slack-errors](https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/screens/slack-canary-failed.png) +![flagger-slack-errors](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/slack-canary-failed.png) ### Prometheus Alert Manager diff --git a/docs/gitbook/usage/monitoring.md b/docs/gitbook/usage/monitoring.md index 03aa1663..103239dd 100644 --- a/docs/gitbook/usage/monitoring.md +++ b/docs/gitbook/usage/monitoring.md @@ -14,7 +14,7 @@ helm upgrade -i flagger-grafana flagger/grafana \ The dashboard shows the RED and USE metrics for the primary and canary workloads: -![canary dashboard](https://raw.githubusercontent.com/stefanprodan/flagger/master/docs/screens/grafana-canary-analysis.png) +![canary dashboard](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/grafana-canary-analysis.png) ### Logging diff --git a/docs/gitbook/usage/progressive-delivery.md b/docs/gitbook/usage/progressive-delivery.md index e1ebf033..9ac4e309 100644 --- a/docs/gitbook/usage/progressive-delivery.md +++ b/docs/gitbook/usage/progressive-delivery.md @@ -5,7 +5,7 @@ This guide shows you how to use Istio and Flagger to automate canary deployments Create a test namespace with Istio sidecar injection enabled: ```bash -export REPO=https://raw.githubusercontent.com/stefanprodan/flagger/master +export REPO=https://raw.githubusercontent.com/weaveworks/flagger/master kubectl apply -f ${REPO}/artifacts/namespaces/test.yaml ```