ci: Check for gke nodepool before locking cluster#12301
Conversation
|
Please set the appropriate release note label. |
|
test-gke K8sDemos |
|
test-gke K8sDemos |
|
Coverage increased (+0.02%) to 36.949% when pulling 37dde93d2ad9f46dd79c582b512668da96ccb5c6 on pr/gke-check-nodepools into 589b56f on master. |
|
test-gke K8sDemos |
|
The error looks odd: |
|
test-gke K8sDemos |
|
Seems like this is caused by setting DOCKER_BUILDKIT to 1 |
337558a to
37dde93
Compare
|
test-gke K8sDemos |
|
test-4.9 |
|
gke error happens after what this PR fixes, so all good from this side. running 4.9 build to make sure nothing else break, after that it's good to merge |
|
On GKE test cilium-node-init is in ImagePullBackOff because startup-script is not available from the same hub as the cilium itself: This error is unrelated to this PR. |
jrajahalme
left a comment
There was a problem hiding this comment.
GKE test successfully passed cluster selection, so this is good to merge.
If the cluster has just been recreated, it can have no nodepool yet. Don't choose such clusters because scaling it will fail. Signed-off-by: Maciej Kwiek <maciej@isovalent.com>
37dde93 to
07b1cde
Compare
|
test-gke K8sDemos |
If the cluster has just been recreated, it can have no nodepool yet.
Don't choose such clusters because scaling it will fail.