Skip to content

Commit

Permalink
Istio is now enabled by flagger addon
Browse files Browse the repository at this point in the history
  • Loading branch information
carlossg committed Feb 12, 2019
1 parent f8168ab commit 613ba99
Showing 1 changed file with 3 additions and 22 deletions.
25 changes: 3 additions & 22 deletions flagger/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,35 +8,16 @@ Install Istio, Prometheus and [Flagger](https://docs.flagger.app)
jx create addon prometheus
jx create addon flagger

Istio is enabled in the `jx-production` namespace for metrics gathering.

Create a Istio Gateway in istio-system namespace:

```yaml
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
name: public-gateway
namespace: istio-system
spec:
selector:
istio: ingressgateway
servers:
- port:
number: 80
name: http
protocol: HTTP
hosts:
- "*"
```
kubectl create -f ../istio/gateway.yaml

Get the ip of the Istio ingress and point your wildcard domain to it

kubectl -n istio-system get service istio-ingressgateway -o jsonpath='{.status.loadBalancer.ingress[0].ip}'

Enable Istio in the `jx-staging` and `jx-production` namespaces for metrics gathering

kubectl label namespace jx-staging istio-injection=enabled
kubectl label namespace jx-production istio-injection=enabled

## Application Configuration

Add the [canary object](../charts/croc-hunter-jenkinsx/templates/canary.yaml) that will add our deployment to Flagger. Add it to the Helm chart so it is created when promoting to `jx-production` namespace.
Expand Down

0 comments on commit 613ba99

Please sign in to comment.