3 ms·

> still not really something a junior dev or admin knows I don't think junior devs should deal with k8s but of course, it depends on how your teams are structu

> still not really something a junior dev or admin knows I don't think junior devs should deal with k8s but of course, it depends on how your teams are structured. Some people think juniors should get involved in everything to make them able to choose better what they want to specialize on and I agree partially. It's just that, before you touch k8s, you better are already involved in everything, and have good communication with bigger stakeholders.

szszrk 5y ago
It's very specific to the company/environment you are in. Plain Kubernetes can be clean and pleasure to work with until you hit level that "sascha_sl" is describing. On conferences I've met a few guys who considered themselves "junior/mid admins" and did all infra (k8s based) AND desktop support for devs in a 40-50 people software houses. Sounds crazy, but some people just don't complicate their lives, like larger companies love to. Some make it a silo and a complex, huge piece of internal IaaS, some just do "fly my dear bird" like on the popular comic [1] You can manage your cluster externally and have an k8s API ready for you with (some of...) popular clouds with barely any knowledge, including ingress on a public facing ip and a DNS pointing to it. A junior can surely do it. "Does it have backups? YES. So it's production ready". [1] https://www.bluelock.com/wp-content/uploads/2017/06/enterprise-vs-startup-journey-to-cloud.png https://www.bluelock.com/wp-content/uploads/2017/06/enterpri...