Cap of Go auto-instrumentation

[dzy176]

https://github.com/open-telemetry/opentelemetry.io/blob/main/content/en/docs/kubernetes/operator/automatic.md?plain=1#L532C1-L539C4

securityContext:
  capabilities:
    add:
    - SYS_PTRACE
  privileged: true
  runAsUser: 0

If a container is already privileged, what is the purpose of explicitly adding SYS_PTRACE?

[svrnm]

@open-telemetry/operator-approvers @open-telemetry/go-instrumentation-approvers PTAL!

[swiatekm]

The operator does not set that capability, nor do we mention it in our documentation, so it looks like it should be removed. @TylerHelmuth is that correct?

[dzy176]

I have submitted a PR. #5890

refer to open-telemetry/opentelemetry-go-instrumentation#388

[grcevski]

I agree, with privileged:true we don't need to additionally specify the PTRACE capability.

[cartermp]

Oh that's great that it's not needed anymore! I recall in the early days of this instrumentation it was, or at least it was assumed to be needed. Opened PR here: #5895

[cartermp]

Fixed, thanks @dzy176