Add options to setup-kubernetes#57
Merged
Merged
Conversation
Plumb two new optional inputs through to helm/kind-action so callers can set a custom cluster name or pass their own kind config. Both are backward compatible: callers that omit them get the previous behavior (cluster_name=kind, default config). For example, a job that needs a custom kind config (containerd registry mirrors, kubeadm patches) no longer has to create a default cluster with this action and then throw it away to make a second one. Signed-off-by: leigh capili <leigh@null.net>
skip-checkout gates the Checkout step; skip-tools gates the Kustomize, QEMU, Buildx, and Go setup steps, leaving only the kind cluster creation. This lets a job check out once, generate dynamic kind configs, and call the action repeatedly to spin up multiple clusters without redoing the toolchain setup each time. Both default to false, so existing callers are unaffected. Signed-off-by: leigh capili <leigh@null.net>
stefanprodan
approved these changes
Jun 15, 2026
stefanprodan
left a comment
stefanprodan
left a comment
Member
There was a problem hiding this comment.
LGTM
Thanks @stealthybox 🏅
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add four optional, backward-compatible inputs to the
setup-kubernetescomposite action:
cluster-name— name of the kind cluster (defaultkind)kind-config— path to a custom kind cluster configskip-checkout— gate the Checkout step when the caller has alreadychecked out
skip-tools— gate the Kustomize/QEMU/Buildx/Go setup steps and onlycreate the kind cluster
These are sensible options to customize kind clusters in CI to match
local make/scripts and to set up custom infra. I intend to use these to
stand up the sigstore stack, which requires configuring the kube
apiserver and containerd.
The alternative is basically copying the pieces of this action
independently, duplicating it into source-controller actions so we can
control the checkout flow and kind config. This seemed like the cleanest
way for us to keep our Dependabot updates in one place.