Let's have a discussion: What would be good to have in a Sensu Go K8s operator

Operators are a relatively new concept in K8s, in order to provide stateful application deployments…which presents a very interesting opportunity to provide some opinionated defaults with regard to a Sensu deployment.

So if you were deploying a Sensu operator into a K8s cluster…what would you like pre-configured by default so you can get reasonable baseline monitoring of that K8s cluster infrastructure right out of the box when the operator deploys?

I’d like to see if we can centralize hard earned operational experience from our users running k8s now into a good baseline Sensu Go operator.

1 Like