Has anyone had a play with K3s yet?

    Posts: 12
    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

    about 1 month 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.

    about 1 month ago
    Posts: 12
    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

    about 1 month ago