Is there a specific aspect of k8s that's causing friction along the learning curve? I'm assuming your referring to the developer side of the equation, not the o

Is there a specific aspect of k8s that's causing friction along the learning curve? I'm assuming your referring to the developer side of the equation, not the ops/admin workflows. Before jumping straight into production k8s, something you can mess around with is using Podman to generate[0] and run[1] Kubernetes resources that you can parse through and familiarize yourself with. Paired with Podman Desktop[2] can produce a nice graphical environment. After that you could take a look at more production-simulating environments with minikube[3], OpenShift Local[4] (very much recommend if you have the resources to run it), and the no-cost OpenShift Sandbox[5]. In general, the Red Hat Developer[6] site has a lot of good resources to learn from, both passive and interactive. I highly recommend going through the courses and tutorials available if it can help your team skill up (assuming k8s is the direction you want to go in). [0] https://docs.podman.io/en/latest/markdown/podman-generate.1.html https://docs.podman.io/en/latest/markdown/podman-generate.1.... [1] https://docs.podman.io/en/latest/markdown/podman-kube.1.html https://docs.podman.io/en/latest/markdown/podman-kube.1.html [2] https://podman.io/features https://podman.io/features | https://podman-desktop.io/ https://podman-desktop.io/ [3] https://minikube.sigs.k8s.io/docs/ https://minikube.sigs.k8s.io/docs/ [4] https://developers.redhat.com/products/openshift-local/overview https://developers.redhat.com/products/openshift-local/overv... [5] https://developers.redhat.com/developer-sandbox https://developers.redhat.com/developer-sandbox [6] https://developers.redhat.com/ https://developers.redhat.com/