If you can, don't try managing your own @kubernetesio clusters. It can become a huge engineering effort in itself very quickly. If the core business product is not around providing infrastructure to others, using #kubernetes solutions provided by cloud providers is not a bad idea
There are exceptions of course, but most of the times you wouldn't require switching out components in the control plane, or installing custom #CNI plugins out of the plethora, these would be taken off your plate and then you can focus on solving other things in your plate.
If someone on a small team brings #Kubernetes expertise to the table, it is worth considering. Otherwise, if you're at the stage where your team is focusing on building the product, then #k8s is probably going to end up being a distraction.
I'd put lots of disclaimers around a single person bringing any kind of specialist expertise to the average small team. I think you need to lean on that person to level the whole team up. If there is any chance of that individual leaving you risk leaving the team high and dry.
With managed #k8s. And that person with expertise would mostly influence design decisions in order to write software that is easily deployed to #k8s and orchestrated in #containers. They wouldn’t be a #devops person taking care of k8s cluster as it makes no sense for a small team
• • •
Missing some Tweet in this thread? You can try to
force a refresh
