Doc arch eckoperator 311
Summary
(Summarize the purpose of the MR)
Relevant logs/screenshots
(Include any relevant logs/screenshots)
/cc @someoneelse
Merge request reports
Activity
added eckoperator statusreview labels
mentioned in issue #311 (closed)
When I asked Tom, he mentioned that given how trivial operators are we probably should leave out architecture docs for them (see Mattermost).
I think Ryan's MR here - https://repo1.dso.mil/platform-one/big-bang/bigbang/-/merge_requests/408 - handles the operator architecture discussion well enough.
Edited by Micah Nagelconcurring with this, going to close this in favor of !408 (merged). If we see demand for tuning the operator I think we re-evaluate this decision, but I've yet to hear of a customer wanting to configure an operator outside of the simple tuning (like replicasets)
mentioned in merge request !408 (merged)