replicatedhq / replicatedhq/kURL
Add support for k3s installer instead of kubeadm
Open
Nobody has claimed this yet.
type::feature
- Dominant language
- Shell
- Stars
- 809
- Forks
- 81
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 20
Description
For some installations (single node, smaller footprint) can kURL support provisioning using k3s instead of kubeadm?
This would be a decision made in the spec, not a runtime option.
Contributor guide
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.
Research direction
The issue names no files or tests. Start by locating how the installation spec selects the kubeadm provisioning path and where installer choices are handled; done would mean a spec-selected k3s installation works for the described single-node or smaller-footprint use case without a runtime option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100