From 8a922b34648296ee7f622a119b78d89b59caea03 Mon Sep 17 00:00:00 2001 From: sadokmtir Date: Thu, 16 May 2024 14:35:36 +0200 Subject: [PATCH] Update kubectl webhook documentation The old documentation did not make it clear that it is still the same chart that was used for integration testing section. The `flagger-kubectltester` gave the impression that it is a different chart. Signed-off-by: sadokmtir --- docs/gitbook/usage/webhooks.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/gitbook/usage/webhooks.md b/docs/gitbook/usage/webhooks.md index 994885b67..e68fa2f97 100644 --- a/docs/gitbook/usage/webhooks.md +++ b/docs/gitbook/usage/webhooks.md @@ -395,14 +395,14 @@ This can be done via mounting a Kubernetes secret in the tester's Deployment. 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). -If you need to start a Pod/Job to run tests, you can do so using `kubectl`. +If you need to start a Pod/Job to run tests, you can do so using `kubectl`. This is available in the same Helm test runner chart as specified in the Integration Testing section. ```yaml analysis: webhooks: - name: "smoke test" type: pre-rollout - url: http://flagger-kubectltester.kube-system/ + url: http://flagger-helmtester.kube-system/ timeout: 3m metadata: type: "kubectl"