Markus Rudy 85b44f7f57 ci: make waiting for nodes more robust (#2981) ... * ci: make waiting for nodes more robust After initializing the cluster, a lot of things happen in parallel and are potentially getting in each others' way: nodes are joining, daemonsets are proliferating, the network is being set up. During this period, it's not unusual that the Kubernetes API server is unavailable for a short time, e.g. due to etcd loosing quorum or load balancing changes. This period of instability has the potential to affect all kubectl commands negatively, leading to problems especially for tests, where command failures often lead to test failures. On the other hand, we'd expect everything to be quite stable after the initial dust settles. Therefore, this commit changes how we wait after initializing a cluster. Until we have a reasonable expectation of readiness, we ignore command failures and wait for things to stabilize. The cluster is considered stable once all configured nodes and all API servers report ready.		2024-03-13 09:42:18 +01:00
..
action.yml	ci: make waiting for nodes more robust (#2981)	2024-03-13 09:42:18 +01:00
aws-logs.sh	ci: fetch latest console logs on aws (#2926)	2024-02-21 13:46:25 +01:00
az-logs.sh	ci: fix resource selection for serial log downloading (#2101)	2023-07-13 16:28:33 +02:00
gcp-logs.sh	ci: fix resource selection for serial log downloading (#2101)	2023-07-13 16:28:33 +02:00
wait-for-nodes.sh	ci: make waiting for nodes more robust (#2981)	2024-03-13 09:42:18 +01:00