Could you comment more on your log aggregation tooling? Did you set up an ELK stack? Self installed or paid? That is the most frustrating part for me — why some of the tooling is not built in.
In many respects kubernetes is just a really nice piece of marble to start with, you still have to carve your statue.
If certain tooling was built-in they would be making stack-specific subjective decisions for you, which is somewhat antithetical to the kubernetes model.
They'll make critical operational decisions for you (e.g. core competencies like scheduling work across a pool of resources), but when it comes to supporting tooling, you still have to make some decisions on your own.
For a lesser burden, there are most likely helm charts or other prepackaged log aggregation tools out there.