flagger/test
Sanskar Jaiswal 4015103815
kuma: disable daemonset for e2e
Signed-off-by: Sanskar Jaiswal <jaiswalsanskar078@gmail.com>
2024-07-26 15:27:48 +05:30
..
apisix add apisix docs 2022-12-07 11:57:21 +08:00
contour Added support for Gateway API v1beta1 2022-11-22 15:51:16 +01:00
gatewayapi gatewayapi: bump e2e tests to v1 2023-11-29 20:56:33 +05:30
gloo switch to use patch 2024-03-18 19:37:08 -07:00
istio make flagger use apiversion v1beta1 for istio VirtualService and DestinationRule instead of v1alpha1 2024-02-28 15:09:40 +01:00
keda Update ScaledObject API to KEDA 2.7.1 2022-07-29 14:50:29 +05:30
kubernetes disable flux helm drift detection for managed resources 2023-04-10 17:28:39 +05:30
kuma kuma: disable daemonset for e2e 2024-07-26 15:27:48 +05:30
linkerd Fix threshold ranges 2023-09-15 15:36:19 -07:00
nginx metric variables documentation and e2e tests 2023-02-08 19:49:22 +10:00
skipper bump provider versions in e2e tests 2022-06-07 12:09:19 +05:30
traefik update traefik version to 24.0.0 in e2e tests 2023-08-28 20:21:17 +05:30
workloads kuma: bump e2e version to 2.7.5 2024-07-26 15:27:46 +05:30
README.md Fix rebase 2020-12-22 10:09:20 -05:00

README.md

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)