That is not how complexity works. You might lower the difficulty in the happy path, but when something goes wrong, there is additional complexity, and that means more places to debug and understand.
This is my primary objection to 3rd party kubernetes operators. I really don't care how hard something is to setup or learn to manage. I care how hard it is to recover, tune, and scale.
> when something goes wrong
Thank for correctly stating “when,” not “if”.
Abstractions are wonderful until they aren’t, at which point you’d better know how everything underneath them works.
I thought that the point was the solution architecture also guarantees increased complexity.