From 8f07ba4552c062b28940bd8cb99bfc151be95346 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Corentin=20N=C3=A9au?= Date: Mon, 21 Oct 2024 11:43:02 +0200 Subject: [PATCH] Add agent check-in interval to agent install tests Omitting the agent check-in interval when patching the `fleet-controller` config map would now lead to errors when setting up agents with a check-in interval bearing the default value for a duration, ie 0s. That interval is now set with a hard-coded value, which is of no importance for such tests, for the sake of not being zero. --- e2e/multi-cluster/installation/agent_test.go | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/e2e/multi-cluster/installation/agent_test.go b/e2e/multi-cluster/installation/agent_test.go index 5bea51fdd2..d9aca41365 100644 --- a/e2e/multi-cluster/installation/agent_test.go +++ b/e2e/multi-cluster/installation/agent_test.go @@ -27,8 +27,9 @@ var _ = Describe("Fleet installation with TLS agent modes", func() { "cattle-fleet-system", "--type=merge", "-p", + // Agent check-in interval cannot be 0. Any other value will do here. fmt.Sprintf( - `{"data":{"config":"{\"apiServerURL\": \"https://google.com\", \"apiServerCA\": \"\", \"agentTLSMode\": \"%s\"}"}}`, + `{"data":{"config":"{\"apiServerURL\": \"https://google.com\", \"apiServerCA\": \"\", \"agentTLSMode\": \"%s\", \"agentCheckinInterval\": \"1m\"}"}}`, agentMode, ), )