3 ms·

K8s is very easy to keep maintained, especially because even for self hosted there are plenty of management tools around. And it allows your teams to deploy ev

K8s is very easy to keep maintained, especially because even for self hosted there are plenty of management tools around. And it allows your teams to deploy everything they need without a admin team. Even ingress you can define

iampims 4y ago
K8s on bare metal is not easy to maintain.
- Melingo 4y ago
  Have you tried using gardener or rancher or ubuntus solution on bare metal? They are very easy to use
  - prmoustache 4y ago
    I don't know when they decided to do that transition but back when I tried rancher a few years ago (when they were transitionning from rancher 1.x to 2.x) it was a real bug festival. I think the only robust solution at the time was openshift which was well, k8s without being vanilla k8s. Also most tools that were build to manage k8s cluster were nice to deploy a new cluster, not so much to upgrade a cluster so you would have to create new clusters every time you wanted an upgrade. It can scale when clusters and blast radius is small but can be complicated when it involves contributions from n teams. For this reason when we were managing our own k8s cluster on prem, we were using kubespray which worked but upgrades were a multiple hours affair.
    - Melingo 4y ago
      That's a real good point you mentioned: k8s ecosystem is super young. And so so much changed in the last 4 years. But at least for me, the 'easy to use' threshold happend somewhere like 2-3 years ago. And Gardner for example upgrades quite well. Rke2 is quite stable for me but rancher integration is still not perfect. But even doing k8s by hand with Ansible was already double 3 years ago. That's what I started and I had it up and running. I switched to rke2 because I realized that this will not be sustainable/ is not worth it to do it myself on this level.
      - deleted 4y ago
        [deleted]
      - satvikpendem 4y ago
        I haven't used k8s in quite a few years, what would you recommend I look at these days to get a good overview and understand all the different pieces in the ecosystem?
        Melingo 4y ago
        Unfortunately I don't have a good blog article about this. I actually thought it would be good to write a k8s blog article After Reading this blog. If you can, click yourself a small cluster in one of the big cloud providers. Alternativly I think Google has some k8s colabs were you can try it out. Setting up a small application yourself or looking into what helm charts exist might help . Like the helm charts for known open source projects like PostgreSQL from bitnami.
  - roncesvalles 4y ago
    That's the thing. On-prem K8s doesn't mean deploying a vanilla Kubernetes using instructions from kubernetes.io. There is an entire industry of proprietary solutions for running Kubernetes on-prem. RedHat Openshift, Rancher, Pivotal PKS, VMWare Tanzu come to mind.

iampims 4y ago

K8s on bare metal is not easy to maintain.

Melingo 4y ago
Have you tried using gardener or rancher or ubuntus solution on bare metal? They are very easy to use
- prmoustache 4y ago
  I don't know when they decided to do that transition but back when I tried rancher a few years ago (when they were transitionning from rancher 1.x to 2.x) it was a real bug festival. I think the only robust solution at the time was openshift which was well, k8s without being vanilla k8s. Also most tools that were build to manage k8s cluster were nice to deploy a new cluster, not so much to upgrade a cluster so you would have to create new clusters every time you wanted an upgrade. It can scale when clusters and blast radius is small but can be complicated when it involves contributions from n teams. For this reason when we were managing our own k8s cluster on prem, we were using kubespray which worked but upgrades were a multiple hours affair.
  - Melingo 4y ago
    That's a real good point you mentioned: k8s ecosystem is super young. And so so much changed in the last 4 years. But at least for me, the 'easy to use' threshold happend somewhere like 2-3 years ago. And Gardner for example upgrades quite well. Rke2 is quite stable for me but rancher integration is still not perfect. But even doing k8s by hand with Ansible was already double 3 years ago. That's what I started and I had it up and running. I switched to rke2 because I realized that this will not be sustainable/ is not worth it to do it myself on this level.
    - deleted 4y ago
      [deleted]
    - satvikpendem 4y ago
      I haven't used k8s in quite a few years, what would you recommend I look at these days to get a good overview and understand all the different pieces in the ecosystem?
      - Melingo 4y ago
        Unfortunately I don't have a good blog article about this. I actually thought it would be good to write a k8s blog article After Reading this blog. If you can, click yourself a small cluster in one of the big cloud providers. Alternativly I think Google has some k8s colabs were you can try it out. Setting up a small application yourself or looking into what helm charts exist might help . Like the helm charts for known open source projects like PostgreSQL from bitnami.
- roncesvalles 4y ago
  That's the thing. On-prem K8s doesn't mean deploying a vanilla Kubernetes using instructions from kubernetes.io. There is an entire industry of proprietary solutions for running Kubernetes on-prem. RedHat Openshift, Rancher, Pivotal PKS, VMWare Tanzu come to mind.