Files
flagger/test
Sanskar Jaiswal 7a438ad323 fix failing kuma e2e tests
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>
2022-01-20 08:20:16 +00:00
..
2021-08-23 12:34:32 +03:00
2021-09-30 11:39:59 +03:00
2022-01-20 08:20:16 +00:00
2021-08-20 17:17:59 +03:00
2021-09-30 11:12:37 +02:00
2021-05-26 10:44:06 +03:00
2021-07-27 12:17:40 +03:00
2021-12-18 14:09:39 -08:00
2020-12-22 10:09:20 -05:00

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)