ci: use quick-k8s action for KinD cluster setup#123
Conversation
Replace manual cluster creation via hack/kind.sh (called through Makefile targets) with the quick-k8s GitHub Action for both the e2e and metallb_e2e jobs. This provides: - Standardized cluster setup with disk optimization - Worker node labeling without post-creation scripts - IP family configuration (ipv4/ipv6/dual) via action input - Consistent cluster naming and kubeconfig export The existing hack/kind.sh idempotency check detects the pre-existing cluster and skips re-creation, so no Makefile changes are needed. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: sebrandon1 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@sebrandon1: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
1 participant
Summary
hack/kind.shinsidemake deploy-*) with an explicitpalmsoftware/quick-k8saction step for both thee2eandmetallb_e2ejobshack/kind.sh, it detects the existing cluster and exits early — no Makefile changes neededExisting adoption
quick-k8s is already used across several Red Hat ecosystem projects:
redhat-best-practices-for-k8s/certsuiteredhat-best-practices-for-k8s/certsuite-qeredhat-best-practices-for-k8s/collectorredhat-best-practices-for-k8s/certsuite-operatorredhat-best-practices-for-k8s/certsuite-sample-workloadrh-ecosystem-edge/eco-goinfraTest plan
e2ematrix (ipv4/ipv6/dual x manifests/helm) passes with quick-k8s clustermetallb_e2ejob passes with quick-k8s clusternode-role.kubernetes.io/worker=worker