We don't have the most sophisticated setup, we're on AWS so we use a fluentd daemonset to ship logs to cloudWatch. In many respects kubernetes is just a really

We don't have the most sophisticated setup, we're on AWS so we use a fluentd daemonset to ship logs to cloudWatch. 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.