Install only mode
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
No file, test, or entry point is named in the issue. Start by locating how GitHub Action inputs are declared and how cluster creation is invoked; trace the existing k3d installation path and determine where an install-only option can bypass cluster creation. Done means the action can install k3d without creating a cluster, while normal cluster creation remains unchanged.
Written by the indexing model from the issue text.
Description
It would be nice to have a way to use this action without the need of creating a cluster, only for install k3d purposes. Imagine a user who wants to start n of k8s clusters and the n is not known in advance but it's dynamically evaluated during the build or whatever.
The officially suggested way of curl -s https://raw.githubusercontent.com/k3d-io/k3d/main/install.sh | bash
isn't super secure.
Something like skipClusterCreation: true,installOnly: true, dontCreate: true or create: false.
- Dominant language
- Shell
- Stars
- 204
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AbsaOSS/k3d-action
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
AbsaOSS/k3d-action#50 · 5 comments ·
All issues in AbsaOSS/k3d-action
Similar issues
-
area: docs complexity: trivial documentation
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
accensa/x402-facilitator-stellar#733 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug internal
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
logicplanes/kaeso#1075 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
jeanibarz/knowledge-base-mcp-server#1268 ·
Maintainers usually reply within 1 day
-
area:ci area:frontend size:S
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
enorm-labs/event-junkie#4975 ·
Maintainers usually reply within 1 day