“ But what I’ve also seen is that if you are using a managed Kubernetes service, your users and permissions handling is perhaps tied not to Kubernetes role-base

“ But what I’ve also seen is that if you are using a managed Kubernetes service, your users and permissions handling is perhaps tied not to Kubernetes role-based access control (RBAC) features, but rather, to cloud-specific offerings. Like AWS Identity and Access Management (IAM). Great service, but ties you to the AWS platform. “ - precisely why Kubernetes as a proxy for “if we build on K8s, we can easily move across clouds” from an infrastructure point of view is not true. If you develop your application for K8S, then yeah, by all means good for you. But, don’t say your reason for taking on the complexity of Kubernetes as a platform is the ability to become multi-cloud easily.