Increase timeout for gardenadm init
to 10m
#12346
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
How to categorize this PR?
/area dev-productivity
/kind flake
What this PR does / why we need it:
After #12169, there is another restart of the control plane to activate the NodeAgentAuthorizer webhook (this changes configuration in
kube-apiserver
). Additionally, we have to ensure thatgardener-node-agent
is still running afterwards, and this can take some additional time.In some e2e runs, the current
5m
timeout is simply too short, see for example:or generally
https://prow.gardener.cloud/?repo=gardener%2Fgardener&job=pull-gardener-e2e-kind-gardenadm&state=failure, if you are fast enough
Special notes for your reviewer:
found w/ @oliver-goetz
Release note: