Skip to content
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

Support cri-o or any arbitrary CRI implementation #107

Closed
ibuildthecloud opened this Issue Mar 1, 2019 · 5 comments

Comments

3 participants
@ibuildthecloud
Copy link
Member

ibuildthecloud commented Mar 1, 2019

Right now the only options are to run the embedded containerd or run with Docker as the container runtime. Support should be added such that in arbitrary CRI implementation can be used.

@Prodian0013

This comment has been minimized.

Copy link

Prodian0013 commented Mar 2, 2019

@ibuildthecloud this is a big one for us!

@ibuildthecloud

This comment has been minimized.

Copy link
Member Author

ibuildthecloud commented Mar 3, 2019

@Prodian0013 I should have a RC build next week to test this. But just to clarify, if you want to use a different CRI you will have to install and manage it yourself.

@Prodian0013

This comment has been minimized.

Copy link

Prodian0013 commented Mar 3, 2019

@Prodian0013 I should have a RC build next week to test this. But just to clarify, if you want to use a different CRI you will have to install and manage it yourself.

@ibuildthecloud sounds good, I can test this with cri-o when rc is out.

@ibuildthecloud

This comment has been minimized.

Copy link
Member Author

ibuildthecloud commented Mar 4, 2019

@Prodian0013 This should be working in v0.2.0-rc3. I tested crio with cgroups manager set to "cgroupfs". Right now the external CRI will not work with our included flannel. So you have to run with --container-runtime-endpoint=/var/run/crio/crio.sock --no-flannel. I'm still working on getting an external CRI work with the embedded flannel.

@ibuildthecloud ibuildthecloud added this to In progress in K3S Development Mar 4, 2019

@ibuildthecloud

This comment has been minimized.

Copy link
Member Author

ibuildthecloud commented Mar 6, 2019

I think for the time being I'm going to have to make it such that if you use an external CRI you must also bring your own CNI. This is because both k3s and the CRI interact with CNI and the configuration must match. That makes things hard so I'm just going to punt and say if you want your own CRI do CNI also. :/

@cjellick cjellick added this to the v0.2.0 milestone Mar 8, 2019

K3S Development automation moved this from In progress to Done Mar 9, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.