https://github.com/linjmeyer/istio-demo
Demo app deployed in Istio servicemesh/k8s for GDG Chicago Istio and Spinnaker talk
https://github.com/linjmeyer/istio-demo
Last synced: about 1 year ago
JSON representation
Demo app deployed in Istio servicemesh/k8s for GDG Chicago Istio and Spinnaker talk
- Host: GitHub
- URL: https://github.com/linjmeyer/istio-demo
- Owner: linjmeyer
- Created: 2020-04-27T20:21:42.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2021-08-18T16:22:35.000Z (almost 5 years ago)
- Last Synced: 2025-01-29T05:18:10.721Z (over 1 year ago)
- Language: C#
- Size: 462 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Demo for Istio Canaries
This project is a demo for Istio canaries and Istio pipelines using Spinnaker. ([Youtube](https://www.youtube.com/watch?v=kd-L0DYfZjk)).
## Source
* `istio` folder contains the Istio operator, namespace and gateway. (Install Istio operator via `istioctl` first)
* `scripts` contains a deployment and configmap with scripts for demo
* `spinnaker` contains Spinnaker pipeline definition in JSON
* `spinnaker-config` contains the Spinnaker CRDs, Operator and Spinnaker configuration used to install Spinnaker
* `src` .NET Core projects used during the demo
* `Dockerfile` and `tests.Dockerfile` ASP.NET Core app and .NET Core integration test dockerfiles
## Demo Setup Instructions
### 1. Port forward Spinnaker
Port forward Spinnaker's `spin-gate` on `8084` and `spin-deck` on `9000`. I use [derailed/k9s](https://github.com/derailed/k9s) for this. Open [http://localhost:9000](http://localhost:9000) to view Spinnaker.
### 2. Create App and Pipeline
Create a new application in Spinnaker, and a new pipeline. Edit the pipeline as Json (top right drop down) and paste in [spinnaker/pipeline.json](spinnaker/pipeline.json). Save.
## Demo Instructions
(Port forward Spinnaker if not already done)
### Trigger canary pipeline
Monitor output of integration tests, ensure "canary" is the response
Optionally, run scripts in scripts/script-deployment.yaml manually to verify.
### Continue to Prod
Once you have verified canary is working, continue to the prod portion of thep pipeline. You should only see "prod" responses from integration tests and CURL output in scripts.