Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
rkt container engine support #58
There is ongoing work for Kubernetes' support of rkt as a production-ready, generally usable container runtime option. This project is sometimes called rktnetes.
There has already been significant work to implement this feature, and as of v1.3 it's already a supported option. However, it does not yet have full feature parity with the default Docker runtime, and I would be wary of calling it "production ready".
In order to have a sane scope for this feature, I'd like for it to track the rkt container runtime having full support for all Kubernetes features, support in Kubernetes deployment, well documented, and a great production choice.
FEATURE_STATUS: IN_DEVELOPMENT (I'm not sure the right status; this has had an initial release suitable for use; development is being done to improve the integration and address known issues / caveats).
Short meta-note: This feature might or might not actually fit here since it's something that is and has been in progress for quite a while. Many of the bullet points don't work well for it because of its circumstances, and I'm hopeful that it can help refine this process a bit; I've taken some liberties with formatting.
I also updated the checkpoints a little, specifically I broke out features a bit more and testing a bit more.
I'll also make a little set of "work done for v1.4" at some point (right now it's subPath, improved privilege, and a couple other bits). The mile-stoning thing makes sense because we're dependent on #54, which is not 1.4.
This feature is straddling two different implementations. I don't think either of them should be marked stable in 1.5 and this feature should be focused on the new integration (dependent on the CRI feature) going forwards to end up stable.
I think updating to reflect that makes sense.
@idvoretskyi, I will update this issue. This feature covers the work to make rkt a first class container runtime for Kubernetes there is an existing implementation currently in tree that is mostly but not entirely feature complete with respect to the docker runtime, however, this is an implementation detail of the feature. Currently there are CoreOS developers working on a CRI conformant rkt integration, tracked here, which is related to #54. Our CRI work is targeting the 1.6 release of Kubernetes and I will move this issue into the 1.6 milestone for tracking. Finally, regarding the existing rkt integration as only small changes have been made during this release cycle we do not believe it makes sense to change the status of that implementation to stable; the CRI work can be considered an iteration on the existing implementation which is currently in tree.