Add support for K8s.io KinD + 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 KinD tool to be able to create K8s clusters running over Sysbox containers. Sysbox would offer the following benefits over KinD's default runtime (runc):
- Security: Sysbox would allow secure containers to be utilized as K8s-nodes -- currently KinD can only run over 'privileged' containers.
- Simplicity: KinD'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.
The following issue has been filed in KinD's project to track this effort: kubernetes-sigs/kind#1772.
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
Start by reviewing the KinD project and the linked kubernetes-sigs/kind#1772 issue, since no Sysbox files, tests, or entry points are named here. Done means KinD can create Kubernetes clusters over Sysbox containers, with the security and image-flexibility goals described in this issue.
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
- 20/100