Roadmap provides detailed description of items that project PouchContainer would decide to prioritize. This helps PouchContainer contributors understand more about the evolving direction and whether a potential contribution is off the direction.
If the feature is not listed below, it does not mean that we will never take that into consideration. We always say that all contributions are warmly welcomed. Please understand that such kind of contributions may take a little bit more time for committers to review.
We designed three parts in roadmap:
- Container Regular Management
- Strong Isolation
- Open to Ecosystem
We will polish user's experience on container management as the first important step. Moby has popularized container API standard in industry. And PouchContainer will follow this API standard to provide container service. In addition, PouchContainer will take more care of more aspects on how to run container on top of various isolation unit. Better experience on taking care of applications is in the scope as well.
A lot of work has been done to improve container's security in industry. But container technology has not reached the target yet. PouchContainer will take more effect on strong isolation, no matter on software side or hardware side. Since security is the largest obstacle for technology to apply in production environment, PouchContainer will improve isolation ability in the following areas: userspace lxcfs to isolate resource view, hypervisor based container, kvm-based container and so on.
For being open to container ecosystem, PouchContainer will be designed to be scalable. As a container engine, PouchContainer will support pod and be able to integrate upper orchestration layer with kubernetes. For fundamental infrastructure management, PouchContainer will embrace CNI and CSI. In the aspect of monitoring, logging and so on, PouchContainer takes an open role to approach cloud native.