Figure out what operators mean for ODS

[michaelsauter]

trafficstars

Operators are a new way of running more complex applications. For us, this could mean that things like SonarQube or Nexus could run as an operator. More info on operators is available here: https://coreos.com/operators/.

I googled and found at least one operator for SonarQube: https://github.com/wkulhanek/sonarqube-operator.

@clemensutschig @rattermeyer @tjaeschke @stitakis I guess we need to talk in general how operators affect us and what our strategy is going forward ...

[segator]

Operators is the future(well the present) and not only for deploy services, for example can be used to manage process like CI. In fact I supose you already know this but from my point of view is the future of Jenkins.

Jenkins Serverless using Knative Build + Prow, all of this managed as simple k8s resources.

[michaelsauter]

I think also Helm plays into this question. It seems that OpenShift now opens the door to Helm v3, as that does not need a highly privileged Tiller. The point where it all comes together is operators. See also https://www.openshift.com/blog/helm-and-operators-on-openshift-part-1 and https://www.openshift.com/blog/helm-and-operators-on-openshift-part-2.