3 ms·
> It takes a fair amount of time and energy to stay up-to-date with the best practices and latest tooling. Kubectl, minikube, kubeadm, helm, tiller, kops, oc -
by kissgyorgy 8y ago
> It takes a fair amount of time and energy to stay up-to-date with the best practices and latest tooling. Kubectl, minikube, kubeadm, helm, tiller, kops, oc - the list goes on and on.
When you start with a technology, you need to have a solid basis. You need to fully grasp the given technology in it's most basic forms, stuck with the problems for days so you can fully grasp what any of these can solve what problem. If you know "naked" Kubernetes inside and out, then you can add other things to your toolset. Until then, you don't need no helm, tiller, kops, Knative or any of those distractions.
- tarikjn 8y agoIsn't knative exactly supposed to solve this problem by giving a portable Heroku-like dev experience?
- kissgyorgy 8y agoDoesn't matter. I talked about the initial learning about Kubernetes. It's just too much to learn everything at once.
- jacques_chester 8y agoRestating: the point is to not have to "learn everything". If your platform makes you do hours of homework, then it's not a platform, it's a pallet of bricks. Heroku got this right with `git push heroku master`. IMO Cloud Foundry got it even more right with `cf push`. Knative is likely to get to that point, probably with the same means as Heroku and Cloud Foundry: Buildpacks. I'm wildly biased of course, having worked on Cloud Foundry, Buildpacks and Knative.