Open himanshu-kun opened 1 year ago
How to categorize this issue?
/area quality /kind bug /priority 3
What happened: The creationTimeout / healthTimeout is not respected in the following cases , as per code analysis :
creationTimeout
healthTimeout
Case 1:
Case 2:
node.gardener.cloud/critical-components-not-ready
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
If node conditions keep flapping , then cloneDirty will become true in every reconcile, so timeout checking is always skipped.
should be dealt in controller runtime refactor.
How to categorize this issue?
/area quality /kind bug /priority 3
What happened: The
creationTimeout
/healthTimeout
is not respected in the following cases , as per code analysis :Case 1:
Case 2:
node.gardener.cloud/critical-components-not-ready
taint present on node, node conditions changedWhat you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
):