Add support for K3d + Sysbox
Open
Nobody has claimed this yet.
Epic
New feature
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
The goal here is to allow K3d tool to be able to create K8s clusters running over Sysbox containers. Sysbox would offer the following benefits over K3d's default runtime (runc):
- Security: Sysbox would allow secure containers to be utilized as K8s-nodes -- currently K3d can only run over 'privileged' containers.
- Simplicity: K3d's Dockerfile images could be drastically simplified as Sysbox absorbs most of the complexity required to allow K8s execution.
- Flexibility: Sysbox imposes no restrictions on the docker images to utilize, so users would have more flexibility to define their own (customized) K8s-node images, including inner images corresponding to K8s components and/or applications.
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 K3d, Sysbox, Docker containers, and Kubernetes but does not identify any files, tests, or entry points. Start by locating the existing K3d runtime and Kubernetes-node image integration, then determine the required design and validation for running clusters with Sysbox; the issue is done when supported clusters can be created and the stated security, image, and flexibility goals are verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100