The name change is something of a late-in-the-game acknowledgement that Kubernetes has won in the cloud-native arena. While Mesos has capabilities that Kubernetes doesn’t (it can run non-containerized stateful workloads, for example), today’s DevOps-centered pipelines have standardized around containers and Kubernetes, making other container management tools and software deployment methods also-rans.