Another example of handling crosscutting concerns at the infrastructure layer

In my last post, I was talking about the ability to make the set of compute resources dynamic.  

Solo.io is one of the most innovative companies out there.   They see the potential of Operators.  

Take a look at what they are doing: (excerpt from their site)

Introducing Autopilot: A Service Mesh Operators Framework

For this reason, we at Solo.io built the Service Mesh Autopilot, an opinionated SDK and toolkit for developing and deploying Service Mesh Operators. By treating service mesh as a first-class concept, Autopilot makes it easy to build Service Mesh Operators that automate and extend service mesh in the same way Kubernetes Operators automate and extend Kubernetes. Autopilot generates scaffolding, builds, and deploys Operators which run against a local or remote Kubernetes cluster with a service mesh installed.

https://www.solo.io/blog/introducing-autopilot-an-open-source-project-for-adaptive-service-mesh/