As someone who made the jarring leap, I'll say it isn't as daunting as it seems on the surface.
The core concepts driving all these technologies are fairly easy to wrap your head around once you make some initial inroads, and the tooling has become very intuitive. The driving factor in a lot of these recent trends has been simplification and re-use, with the goal being to let you focus on the part you actually need to and have the rest more or less just work.
Personally, I went (at a very high level), docker -> podman -> k8s -> istio. This still seems like a common progression. Docker is falling out of fashion, but it is very intuitive and user friendly. I view it as kind of the MySQL of the container world. Not as powerful, but you can get going with it really quickly and it is a good way (imo) to learn the basic principles. Podman and k8s are built on the same ideas (and use a lot of the same underlying tools), but are more flexible. Istio looks really daunting at first, but it is actually pretty straight forward once you dive into it.
There is a tonne of terminology around this stuff too, which I think also can make it seem like a huge barrier if you've been hacking away on a c++ monolith for the last 10 years, but once you start using it, it kinda just clicks (or at least that was my experience).
I actually think that is the problem stuff like this tool is trying to solve. Get users up and doing something so they don't feel like they are staring at a wall with no clue where to even start. "Hey, download this, run this, congratulations you have a service mesh!"