-
Notifications
You must be signed in to change notification settings - Fork 949
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[enhancement request] CRI manager to integrate pouch with kubernetes #420
Comments
Let me take a closer look at it |
lgtm |
Hi, @xiang90 , |
Have we finished the final one |
All tasks have been finished, close now. |
What is the scope of CRI manager
GRPC server : connect to kubelet and receive CRI requests
API transform : use pouch's container & image manager to handle all kinds of CRI requests
Pod support : pod's lifecycle and metadata store
CNI integration: the network of containers which belong to kubernetes should be managed by CNI other than the pouch's network manager
What is not in the scope of CRI manager
CRI manager should never interact directly with containerd. It is the job of pouch's container & image manager to implement all the details of containers & images processing
All metadata, except for the sandbox should not be managed by CRI manager
The above is the coarse-grained division of CRI manager's scope, we may have to refine it in the future. And the next part of this issue is used to track the progress of CRI manager.
Task tracking
Basic framework
Lifecycle
Sandbox Management
Container Management
Image Management
Others
Network
Streaming
[P2] Logging feature: cri manager could get the log of container #928
cc @skoo87 @allencloud
The text was updated successfully, but these errors were encountered: