mirror of
https://github.com/fluxcd/flagger.git
synced 2026-04-15 06:57:34 +00:00
Kuma e2e tests were failing in CI(https://github.com/fluxcd/flagger/runs/4826617915?check_suite_focus=true) due to prom server installed in the kuma-metrics ns not being able to contact the kubernetes api server. Fixed by switching to flagger prometheus and a custom kustomize build for kuma tests. Signed-off-by: Sanskar Jaiswal <jaiswalsanskar078@gmail.com>
Flagger end-to-end testing
The e2e testing infrastructure is powered by GitHub Actions and Kubernetes Kind.
e2e workflow
- create local Kubernetes cluster with KinD
- build Flagger container and load the image in KinD
- install the service mesh or ingress provider
- deploy Flagger
- create test namespace, workloads and load tester
- test the canary initialization (port discovery and metadata)
- test the canary release (progressive traffic shifting, headers routing, mirroring, analysis, promotion, rollback)
- test webhooks (conformance, load testing, pre/post rollout)