The solution is to force yourself not to use the CI/container system at all during debugging, and instead to build the binary (or whatever) standalone. That's hard because you invariably aren't tooled up to run the component outside its deployment system so you have to do some extra tricks, but in the long tun it seems to be the way to go.

Maybe your current strategy isn't working?

There are more sane ways to do this than through raw kubectl access, of course: see e.g. telepresence (https://www.telepresence.io/)

- How do you provide easy visibility into running applications?

- How do you prevent inspecting an application from affecting the behavior of an application?

I think of the phrase “adding epicycles” when this kind of stuff starts happening.