-
Notifications
You must be signed in to change notification settings - Fork 14
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
Documentation should describe supported/non-supported use cases #22
Comments
@tomaswarynyca @ToeiRei comments? |
Kubernetes is 'just a bunch of containers' and nothing we should really be scared of. I just wouldn't mention it as it doesn't need any special stuff (btw, I run K3s on rancherOS) |
On simple configuration yes but when it comes more complex setup there will be need to be persistent storage for /var/lib/kubelet and example Longhorn needs iscsid (look #21).
OK but notice that Rancher team made it very clear that they will not support K3s on RancherOS k3s-io/k3s#173 (comment) Obviously they did know already then that RancherOS will be discontinued.
Maybe we should then at least try explain recommend/tested use cases/configurations on documentation? Also BurmillaOS + K3s might make sense (on theory) on some specific use cases like on Raspberry Pi if k3OS will not support it but IMO we should not compete with k3OS on use cases which it can handle. |
maybe something like 'We use it for.... ' to narrow it down a bit. |
Good point but we still should take care of the fact that BurmillaOS is based on Docker and now Kubernetes team is deprecating Docker support https://www.theregister.com/AMP/2020/12/03/docker_deprecated_in_kubernetes_this/ |
It seems correct to me to define the course of BurmillaOS. For the moment you should focus on the docker environment.
At the moment I don't see the need to put support for Kubernetes so he said @olljanat will no longer support Docker as they
If you like @ToeiRei you can make a guide of how to use k3s in BurmillaOS but officially it's not a good idea to support it. |
As docker support is now obsolete in kubernetes, we'can safely ignore that :) |
As far as I understood RancherOS and therefore also BurmillaOS is built using Moby which uses containerd. You can verify this using:
I will keep an eye on this and make it work for Kubernetes if desired ? |
True so as long user Docker/Moby comes with supported containerd version it might works (on theory). sudo ctr -n moby -a /run/docker/containerd/containerd.sock version I also quickly checked that it updates if I switch to later Docker versions burmilla/os-services#7
Works for me as long it does not require big changes to BurmillaOS. |
Running K8S on RancherOS 1.5.6, installed via RKE. |
FYI. Looks that Rancher have released tool called for k3d which looks to be nice way to play with k3s on BurmillaOS: https://rancher.com/blog/2020/set-up-k3s-high-availability-using-k3d |
Closing this one now because we need figure out answer to #47 first. |
For everyone who is planning to run Kubernetes on top of BurmillaOS on longterm. Please check my new architecture proposal on #88 |
Currently it is still bit unclear that which use case will be supported by BurmillaOS and key driver to define scope is feedback given on #6
However I think that we can say for sure that:
These use cases are not supported:
These use cases are supported:
docker run
/docker create
)docker-compose
)docker stack deploy
/docker service
)Also it is worth to mention that with "not supported" I mean that users are free to use BurmillaOS for those use cases if that works but any issues related to those will be considered to be on low priority.
The text was updated successfully, but these errors were encountered: