Has anyone had a play with K3s yet?

    Posts: 20
    Member since: Dec 16
    Contact:  

    Been seeing a lot of rumblings about https://k3s.io/ recently - a lightweight cutdown version of Kubernetes (but still completely compatible).

    I've had a play and it seemed REALLY good, but I'm not sure if it's production ready (couldn't find a way of reconfiguring the services to rejoin the cluster on reboot - at least at a cursory glance).

    Anyone else had a go with it (or planning to)? Is anyone currently using it on Civo?

    Post liked by PaulCaine

    CTO, Civo

    3 months ago
    Posts: 8
    Member since: Apr 17
    Contact:  

    Im still trying to get to grips with docker. k3s would be good to have a play with on my Pi.

    I have a question while on the subject, i sould post it in another forum but. Do you/all build on a local machaine first then deploy to maybe docker hub or maybe even build a Dockerfile and copy it to your server.

    Also, last one. If building LEMP/LAMP stack would place each in its own container or run them all in the same?

    Forgive me if im not making much sence for the tech pros out there, i am still learning.

    3 months ago
    Posts: 20
    Member since: Dec 16
    Contact:  

    PaulCaine wrote on 18 March 2019 at 22:15:35
    I have a question while on the subject, i sould post it in another forum but. Do you/all build on a local machaine first then deploy to maybe docker hub or maybe even build a Dockerfile and copy it to your server.

    I would definitely advocate the build first route. We have a GitLab instance (running in Civo) that we push our source code to, it builds a docker image and hosts it. GitLab has a built in private registry, so you don't need a paid account on DockerHub. You could easily push to DockerHub if you wanted to from there though.

    PaulCaine wrote on 18 March 2019 at 22:15:35
    Also, last one. If building LEMP/LAMP stack would place each in its own container or run them all in the same?

    Personally I would keep them all in separate containers, but I've used containers far more in Kubernetes than in raw Docker. So I tend to always think about having each container connect to services (which may have one or more containers behind it) rather than directly to containers. That way you could scale the MySQL horizontally without scaling the PHP to the same level, depending on which needs more resource.

    If you're using Kubernetes there are also easy AutoScalers to handle that for you - scale up the items being hit the hardest automatically.

    PaulCaine wrote on 18 March 2019 at 22:15:35
    Forgive me if im not making much sence for the tech pros out there, i am still learning.

    Hey my friend, don't worry about that - I'm always still learning and think it would be a boring life if I ever stopped learning. Pop a reply back here if you have any more questions about this stuff.

    Post liked by Kvark

    CTO, Civo

    3 months ago
    Posts: 4
    Member since: May 17
    Contact:  

    I'm slowly transitioning from a traditional sysadmin to DevOps. It just makes a lot more sense nowadays.. I'm still reading up on k8s but k3s looks really cool. I might try k3s on Civo because it's so lightweight and I could use the smallest instances. Other than being more lightweight, is it worth switching if you're not running on small devices like a Raspberry Pi?

    23 days ago
    Posts: 20
    Member since: Dec 16
    Contact:  

    zacharym wrote on 24 May 2019 at 18:25:32
    Other than being more lightweight, is it worth switching if you're not running on small devices like a Raspberry Pi?

    It's definitely lower resource using than a traditional Kubernetes cluster. So it depends if you're dipping your toe in the water to have a play, running some small fun sites or looking to run it professionally.

    For the first case where it's a single, XS/S/M node just to get used to pods, services, etc I'd say run k3s (on a single node).

    For the third case, I definitely would run the full k8s for now. I just haven't run k3s properly enough to know how well it works in a production environment.

    For the middle case (k3s on more than one node), I'd be tempted to have a play with running k3s. I think there'll be a learning curve (when I last tried it, they didn't come with services to bring k3s back up seamlessly after a reboot - that may have been fixed now, but it feels like there may be a bit of tweaking required.

    Post liked by zacharym

    CTO, Civo

    19 days ago
    Posts: 3
    Member since: Jun 17
    Contact:  

    Yes I've played with it a lot - on Linux / cloud and on ARM (Raspberry Pi)

    Will it cluster? k3s on your Raspberry Pi -> https://blog.alexellis.io/test-drive-k3s-on-raspberry-pi/

    I'm yet to try it on Civo, but fairly sure it would work. Just make sure there is a firewall set up to prevent people getting old of the flannel port.

    https://twitter.com/alexellisuk/status/1137075794579263491

    Post liked by markb
    6 days ago
    Posts: 3
    Member since: Jun 17
    Contact:  

    Seems to work nicely, at least with a single node.

    https://twitter.com/alexellisuk/status/1138101825817776128

    Pics in thread ^

    (As stated, I don't think k3s is GA yet)

    Post liked by barryf
    6 days ago