If you want your Devs to learn kubernetes you should pay them for doing it.
If you can't, hire a contractor with the expertise you need.
If you want your Devs to learn kubernetes you should pay them for doing it.
If you can't, hire a contractor with the expertise you need.
It is difficult to tell at a glance whether an engineer is qualified to effectively use a tool. Letting them self-train by working on self-projects in isolation compounds this effect.
The goal of this exercise is to give time and space to your devs to practice in a safe environment, while allowing them to push, deploy and review projects internally as if they were core products, so that other SMEs are allowed to spend some time every week reviewing those projects for smells and issues before those ideas make it into a core product.
Fortunately, k8s can act as a very secure sandbox when it's configured properly, so you'll know how to mitigate such a disaster once your company has trained its engineers on how to use the tool effectively.
It's not as common as some would have you believe but it is real. A teammate spent his 20% on underwater topography on Google Earth and another spent his on the glider thing.
Having an employee turn up a popular side projects while being vendor-locked onto your platform sounds like it should be more popular among rich people.
The way it is should actually be sold to the average entry-level fresh-out-of-college Google hire is probably closer to the way I framed it, though, than the examples of Gmail and Google Calendar which are pretty much two unicorns.