Add support for nginx ingress controller #170
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for nginx ingress controller canary deployments.
How to test this:
Clone this repo and checkout the
nginx
branch:git clone https://github.com/weaveworks/flagger cd flagger git checkout nginx
Install the nginx ingress controller with Helm:
Install Prometheus:
Install Flagger with nginx support:
Install the load tester:
helm upgrade -i flagger-loadtester flagger/loadtester \ --namespace test
Edit
./artifacts/nginx/ingress
and./artifacts/nginx/canary
and replaceapp.example.com
with your own domain.Deploy the podinfo in the test namespace:
Check initialisation:
Trigger canary deployment:
Check deployment:
watch kubectl -n test describe canary/podinfo
Generate 500 errors:
Trigger canary deployment:
Verify rollback:
kubectl -n ingress-nginx logs deploy/flagger -f | jq .msg
Fix: #169