Create operator kit for common operations?

[jamiehannaford]

I'm wondering whether there is enough overlap in different operators to warrant some kind of common library that will make the lives of those who want to write an operator easier. Have you folks thought about doing this?

I've already reached out to CoreOS's etcd-operator and rook about this, and started to write proposal for an OperatorKit here:

https://docs.google.com/document/d/1NJhFcNezJyLM952eaYVcdfIQFQYWsAx4oTaA82-Frdk

Is this something that would benefit the wider operator community? If so, would love to hear your feedback in that proposal.

[jamiehannaford]

@rossf7 @JosephSalisbury @nhlfr @asymmetric Is this something you folks are interested in?

[rossf7]

@jamiehannaford Yes, we're interested and we've started creating a library as we need it for our operators :) https://github.com/giantswarm/operatorkit

But we see it being useful to the wider operator community. The proposal looks interesting and there is some crossover with what we already have. I'll have a proper look and add feedback when I get a chance.

[puja108]

@jamiehannaford great to see even more interest in this topic, let's see if we can somehow put our efforts together and get this thing out for the wider community to use.

[jamiehannaford]

Closing as we now have a requirements doc and community interest. Next steps will be proposing it as an incubator project.