as discussed in the meeting, we did some work on the Operator Document and are trying to make some progress. At the moment we focus on the essential things of the document (so what an operator is, but not what it not is), so we're keeping things as similar technologies out of the discussion at the moment.
Call to action:
- Please review the current document (https://docs.google.com/document/d/1daXHyR2yG5ArjO1PO83v4a0fmLCLo2kYNT3TwGZksng/edit#heading=h.nnnd3pbrryjy)) and make comments and proposals (especially to the Operator Definition and the Use-Case Section, which is very rudimentary at the moment). If something is really missing in your opinion, feel free to add it.
- I think it would be nice to meet weekly to walk through the document step by step and build proposals for the sections. Next, we we would like to discuss capabilities of an operator (install, upgrade, backup, restore, reconfigure, ...), and what typically should be integrated on each one. If you are interested in contributing, please let me know (i will send you an invitation).
- Afterwards, I think it would be really nice to build examples for these capabilities for the podtato-head app (https://github.com/cncf/podtato-head) to show how the implementation of such capabilities could look like. But let's discuss this, and how such sample-implementations could look like