I am not sure if anything can be improved in Spinnaker because it was written and designed before Kubernetes was around. All of its authentication, role-based access control, application definition, and other stuff happen outside of Kubernetes, so Spinnaker is not a Kubernetes-native tool. You have to mimic a lot of the stuff you already have the provisions for in Kubernetes. Kubernetes also has parallels to what it is in Spinnaker. If your deployment infrastructure is Kubernetes, to get it running on Kubernetes takes a lot of customizations that you have to do, and it is something that the company has done. One of the downsides of Spinnaker is its scalability. The amount of data that it stores in each pipeline or from a pipeline context is huge. Every time it goes to run a pipeline, it just generates a lot of data, and its database is not exactly tuned out of the box, meaning it is not tuned for high scalability. You start to run a bunch of pipelines in parallel, and very quickly, within a couple of hundred pipeline runs, you start to run into scalability and performance issues.
