You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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):
The following issue has been filed in KinD's project to track this effort: kubernetes-sigs/kind#1772.
The text was updated successfully, but these errors were encountered: