Portainer originally started as a UI tool on top of Docker, helping to keep an overview of all your Docker containers. Over time, people realized that in certain situations, you might want to manage these large numbers of Docker containers semi-automatically, and that's how Kubernetes came into play, taking care of that. Then, Portainer built a feature so you can manage/control Kubernetes with it too. However, I haven't heard of a company using Portainer to manage Kubernetes yet. Usually, they go for tools like Lens or k9s (which I just discovered and totally recommend). Previously, UMH was just a Helm Chart for Kubernetes, so it would have made sense to create a Kubernetes cluster and use Portainer to manage it. Over time, to simplify the user experience, the UMH evolved into something more and now includes creating a Kubernetes cluster via k3s, remotely managing the UMH with the Management Console, and the entire infrastructure part ensuring that you only need to whitelist one domain for all dependencies, etc. The main reason for us was to improve the user experience. Remember a year ago how tricky it was to get started with the UMH? To simplify things, we decided to stick with one Kubernetes version (k3s), which should work fine for 99% of companies. Other Kubernetes versions, like the one Portainer brings by default, might have slightly different elements running in the background and could now tell @Brian Pribe Brian Pribe that a configmap, for example, is too large.