Setting a higher ConnectTimeout for ssh #482
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#482
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When I generate all the secrets for authentik (about 15) it takes so long that I hit the connection timeout of 5 seconds.
Would it cause any problems if we simply set the connection timeout to a fixed value of 30s? Or would a parameterized connection timeout be better?
0c6a7cc0b8/pkg/upstream/commandconn/connection.go (L21)
Ah yeh, that is quite low. I think it is set like this so that failed SSH connections get faster feedback, e.g. if you don't have your keys configured correctly, you only wait 5 seconds to hear about it. I don't know how hard it would be to pass down a parametrized value for specific cases but perhaps this could be something that could go in https://git.coopcloud.tech/coop-cloud/abra/src/branch/main/pkg/runtime/config.go
So, the "cleanup when cannot add server" is now taking +1 minute to run because the timeout is so large. @moritz do you have any proposals on how to make this value configurable? Could this value also be read from the
~/.ssh/config
as a global configuration? Then we could revert to the small default.decentral1se referenced this issue from coop-cloud/abra2024-03-03 16:01:00 +00:00
p4u1 referenced this issue2024-03-11 12:57:14 +00:00
decentral1se referenced this issue2024-03-27 06:27:25 +00:00