For the 'default' strategy - the OneAgent DaemonSet injects into your application pods, and also has access to metrics on the host. The Operator is what keeps the DaemonSet up to date. The /opt directory is on a shared volume so that each pod can use the same binaries without having to download / install them each and every time.
If you do not care about host monitoring, then the OneAgentAPM will work as you say, without the shared volume, though there is this kubectl apply my-app.yml peformance hit as described above, since the agents must be unzipped and installed for each pod.
Red Hat is one of our largest partners. We work with them, jointly, on both technical and sales opportunities, and collaborate closely with their engineering teams. Their stance is that monitoring is critical and there are always trade-offs. If you want host metrics, you need access to the host.
We are exploring alternative ways of mounting volumes across pods. We are also aware of some custom configurations at a few of our larger customers who are isolating these mounts by namespace using either their own, or some third-party solutions.
Kubernetes beatings will continue until morale improves
