Skip to content

Commit

Permalink
Add agent check-in interval to agent install tests
Browse files Browse the repository at this point in the history
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.
  • Loading branch information
weyfonk committed Dec 18, 2024
1 parent 2aaefd8 commit 9f8db1c
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion e2e/multi-cluster/installation/agent_test.go
Original file line number Diff line number Diff line change
Expand Up @@ -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,
),
)
Expand Down

0 comments on commit 9f8db1c

Please sign in to comment.