Unable to run a sidecar dotnet monitor container in replica

Please provide us with the following information:

This issue is a: (mark with an x)

• bug report -> please search issues before submitting
• documentation issue or request
• regression (a behavior that used to work and stopped in a new release)

Issue description

We are currently having problems with constant CPU consumption by replicas (issue #620 ) and we are unable to run any of the diagnostic tools which dotnet provides (e.g. dotnet-trace), because they hang when ran inside the problematic replica. We figured that running a sidecar container with dotnet diagnostic tools next to our main container might solve this problem. The problem is, there is absolutely no documentation on how this can be done. I've tried looking through the tutorials for K8S, but they are of little help as we have no access to the AKS which underlies the ContainerApp. I also get the impression that in order for a sidecar diagnostic container to work, it has to share the process namespace of the main container. Is that achievable? I would be very thankful if someone can point me to some documentation on the topic.