The essential ideas that Kubernetes exposes concretely are invariant across cloud providers. There absolutely are nuances and quirks that are different for each

The essential ideas that Kubernetes exposes concretely are invariant across cloud providers. There absolutely are nuances and quirks that are different for each cloud provider, and unique for the workload you have. However, those same ideas also act as a kind of mental framework in which these quirks can be understood from. It isn’t as if those quirks are randomly there, unconnected to anything, and therefore not part of a coherent design. For example, the consistent use of labels as a way to identifying groups of resources that need to coordinate with each other is very useful for any distributed system. I find myself looking for them in say, CI/CD systems (in the form of agent tags), or at the application level in say, matching players to game servers.