Note that the sum of all rollout webhooks timeouts should be lower than the analysis interval.
Initialized
, Waiting
, Progressing
, Promoting
, Finalising
, Succeeded
or Failed
).http://flagger-loadtester.test/
.hey
commands in the background, if they are not already running. This will ensure that during the analysis, the podinfo-canary.test
service will receive a steady stream of GET and POST requests.hey
to the public URL and use HTTP2.ghz
uses reflection to identify which gRPC method to call. If you do not wish to enable reflection for your gRPC service you can implement a standardized health check from the grpc-proto library. To use this health check schema without reflection you can pass a parameter to ghz
like thishey
with another CLI, you can create your own Docker image:k6 webhook
. This webhook uses k6
, a very featureful load tester, to run load or smoke tests on canaries. For all features available, see the source repository.pre-rollout
step, to load test a service before any traffic is sent to it:kube-system
namespace using the tiller
service account:http://flagger-helmtester.kube-system/
.org
, project
, repo
and entrypoint
represents where your test process runs in Concord. In order to authenticate to Concord, you need to set apiKeyPath
to a path of a file containing a valid Concord API key on the flagger-helmtester
container. This can be done via mounting a Kubernetes secret in the tester's Deployment. pollInterval
represents the interval in seconds the web-hook will call Concord to see if the process has finished (Default is 5s). pollTimeout
represents the time in seconds the web-hook will try to call Concord before timing out (Default is 30s).confirm-rollout
and confirm-promotion
webhooks. The confirmation rollout hooks are executed before the pre-rollout hooks. For manually approving traffic weight increase, you can use the confirm-traffic-increase
webhook. Flagger will halt the canary traffic shifting and analysis until the confirm webhook returns HTTP status 200.rollback
webhook. The rollback hook will be called during the analysis and confirmation states. If a rollback webhook returns a successful HTTP status code, Flagger will shift all traffic back to the primary instance and fail the canary./gate/halt
returns HTTP 403 thus blocking the rollout./gate/approve
to start the canary analysis:/gate/check
:confirm-promotion
hook type can be used to manually approve the canary promotion. While the promotion is paused, Flagger will continue to run the metrics checks and load tests.rollback
hook type can be used to manually rollback the canary promotion. As with gating, rollbacks can be driven with Flagger's tester API by setting the rollback URL to /rollback/check