Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detect offline clusters #2933

Open
wants to merge 14 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
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.
weyfonk committed Dec 18, 2024
commit 9f8db1c9df5bcf40ba3c8033dae2ac48da6257b2
3 changes: 2 additions & 1 deletion e2e/multi-cluster/installation/agent_test.go
Original file line number Diff line number Diff line change
@@ -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,
),
)