Why we need it?
We have lot of protect which uses CI action which creates kind cluster for its CI. I want to add a reusable composite action (.github/actions/create-cluster) that spins up a local Kubernetes cluster (Kind) so CI jobs can run against a real cluster instead of each workflow re-implementing the setup inline.
The same action already exists and is in use in the
Requirement
- Adds common action for cluster creation with inputs for Kubernetes version and the Kind node image.
- Exports
KUBECONFIG so subsequent steps can talk to the cluster directly.
Why we need it?
We have lot of protect which uses CI action which creates kind cluster for its CI. I want to add a reusable composite action (
.github/actions/create-cluster) that spins up a local Kubernetes cluster (Kind) so CI jobs can run against a real cluster instead of each workflow re-implementing the setup inline.The same action already exists and is in use in the
sdkhttps://github.com/kubeflow/sdk/blob/main/.github/workflows/test-e2e.yamltrainerhttps://github.com/kubeflow/trainer/blob/master/.github/workflows/test-e2e.yamlmcp-serveras part of this feat(ci): add Kubernetes E2E tests against live cluster mcp-server#109Requirement
KUBECONFIGso subsequent steps can talk to the cluster directly.