3 ms·
> If someone on a small team brings K8S expertise to the table, it is worth considering. Perhaps you have some unstated assumptions here like a small team mana
by zerkten 8y ago
> If someone on a small team brings K8S expertise to the table, it is worth considering.
Perhaps you have some unstated assumptions here like a small team managing a relatively large infrastructure for their team size? Or, a small team in a much larger infrastructure department.
If it was me, 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.
- richardknop 8y agoYou can use managed Kubernetes. And that person with expertise would mostly influence design decisions in order to write software that is easily deployed to kubernetes and orchestrated in containers. They wouldn’t be a dev ops person taking care of k8s cluster obviously that makes no sense for a small team.
- hosh 8y agoIt is what I am doing for my team. And yes, if I leave, it would leave the team in a bad state. I have been incrementally cross-training two of the other engineers on this. We’re not managing our own K8S cluster. I did that once by hand at another place (before kubeadm), enough to know that managed GKE on GCP is a great thing. Also did my own single-node K8S for dev work. Nanokube and later, minikube later mare that much easier. I used to do stuff with Capistrano and Chef. Enough to know that once you know the core primitives, it is easier just to use K8S.