-
Notifications
You must be signed in to change notification settings - Fork 49
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I have noticed that 6minutes looks like a good time for the nodes to join. So we should timeout after 6minutes. See #940 (comment) for more details. |
b168164
to
5cf18ec
Compare
Right, let me check it. What about some nice number like 5 minutes for API and 10 minutes for nodes? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
AKS didn't start on this :-\ |
That's weird because no other process is running. |
As this is the only place which use those functions. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
As it is not used anywhere. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
As they provide the same functionality, but PollImmediate has more obvious interface (as you don't mix duration with number of retries). Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
This code is no loger used so can be removed. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
3 minutes seems like an arbitrary time to wait for cluster to become ready, so let's make it at least round to 5 minutes. As currently we have issues, that nodes do not become ready within 3 minutes timeframe, let's give them max 10 minutes to converge, which should be sufficient in most cases, as sometimes it may take up to 5 minutes for node to become ready. Closes #940. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
9a81e25
to
5ca727b
Compare
Rebased and push again to poke CI. |
Includes commits from #951
Part of #290