Update site

README.md

@@ -37,7 +37,7 @@ one for the version you want to upgrade called _primary_ and one for the _canary
 Each deployment must have a corresponding ClusterIP [service](https://kubernetes.io/docs/concepts/services-networking/service/) 
 that exposes a port named http or https. These services are used as destinations in a Istio [virtual service](https://istio.io/docs/reference/config/istio.networking.v1alpha3/#VirtualService).
 
-![steerer-overview](https://github.com/stefanprodan/steerer/blob/master/docs/diagrams/steerer-overview.png)
+![steerer-overview](https://raw.githubusercontent.com/stefanprodan/steerer/master/docs/diagrams/steerer-overview.png)
 
 Gated canary promotion stages:
 
@@ -198,7 +198,7 @@ histogram_quantile(0.99,
 
 ### Automated canary analysis, promotions and rollbacks
 
-![steerer-canary](https://github.com/stefanprodan/steerer/blob/master/docs/diagrams/steerer-canary-hpa.png)
+![steerer-canary](https://raw.githubusercontent.com/stefanprodan/steerer/master/docs/diagrams/steerer-canary-hpa.png)
 
 Create a test namespace with Istio sidecar injection enabled:
 
@@ -368,7 +368,7 @@ helm upgrade -i steerer-grafana steerer/grafana \
 
 The dashboard shows the RED and USE metrics for the primary and canary workloads:
 
-![steerer-grafana](https://github.com/stefanprodan/steerer/blob/master/docs/screens/grafana-canary-analysis.png)
+![steerer-grafana](https://raw.githubusercontent.com/stefanprodan/steerer/master/docs/screens/grafana-canary-analysis.png)
 
 The canary errors and latency spikes have been recorded as Kubernetes events and logged by Steerer in json format:
 

docs/README.md

@@ -37,7 +37,7 @@ one for the version you want to upgrade called _primary_ and one for the _canary
 Each deployment must have a corresponding ClusterIP [service](https://kubernetes.io/docs/concepts/services-networking/service/) 
 that exposes a port named http or https. These services are used as destinations in a Istio [virtual service](https://istio.io/docs/reference/config/istio.networking.v1alpha3/#VirtualService).
 
-![steerer-overview](https://github.com/stefanprodan/steerer/blob/master/docs/diagrams/steerer-overview.png)
+![steerer-overview](https://raw.githubusercontent.com/stefanprodan/steerer/master/docs/diagrams/steerer-overview.png)
 
 Gated canary promotion stages:
 
@@ -157,7 +157,7 @@ The canary analysis is using the following promql queries:
  
 _HTTP requests success rate percentage_
 
-```sql
+```promql
 sum(
     rate(
         istio_requests_total{
@@ -182,7 +182,7 @@ sum(
 
 _HTTP requests milliseconds duration P99_
 
-```sql
+```promql
 histogram_quantile(0.99, 
   sum(
     irate(
@@ -198,7 +198,7 @@ histogram_quantile(0.99,
 
 ### Automated canary analysis, promotions and rollbacks
 
-![steerer-canary](https://github.com/stefanprodan/steerer/blob/master/docs/diagrams/steerer-canary-hpa.png)
+![steerer-canary](https://raw.githubusercontent.com/stefanprodan/steerer/master/docs/diagrams/steerer-canary-hpa.png)
 
 Create a test namespace with Istio sidecar injection enabled:
 
@@ -368,7 +368,7 @@ helm upgrade -i steerer-grafana steerer/grafana \
 
 The dashboard shows the RED and USE metrics for the primary and canary workloads:
 
-![steerer-grafana](https://github.com/stefanprodan/steerer/blob/master/docs/screens/grafana-canary-analysis.png)
+![steerer-grafana](https://raw.githubusercontent.com/stefanprodan/steerer/master/docs/screens/grafana-canary-analysis.png)
 
 The canary errors and latency spikes have been recorded as Kubernetes events and logged by Steerer in json format:
 

docs/_config.yaml

@@ -2,7 +2,7 @@ title: Steerer - Istio Progressive Delivery Kubernetes Operator
 
 remote_theme: errordeveloper/simple-project-homepage
 repository: stefanprodan/steerer
-by_weaveworks: false
+by_weaveworks: true
 
 url: "https://stefanprodan.github.io/steerer"
 baseurl: "/"