[Otel-Operator] Target Allocator is not running as nonroot

[toporek3112]

Component(s)

target allocator

Describe the issue you're reporting

When testing the otel-operator setup on an RKE cluster I stumbled upon Error: container has runAsNonRoot and image will run as root (pod: "otel-targetallocator-78cd5444fc-f5fqh_monitoring(1207-4994-9ce5-fb97246690a4)", container: ta-container)

otel-operator helm chart values snipped:

                    image:
                      repository: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator
                      tag: 0.108.0
                    collectorImage:
                      repository: "otel/opentelemetry-collector-contrib"
                      tag: 0.108.0
                    targetAllocatorImage:
                      repository: ghcr.io/open-telemetry/opentelemetry-operator/target-allocator
                      tag: 0.108.0

If this is intended I will use a custom image. Please let me know.

[swiatekm]

The target allocator docker image does indeed run it as root, but I don't think that's actually necessary. @jaronoff97 @pavolloffay do you know why this is? Looks like it was set in #354, where the target allocator was originally added, and I don't see any comments about it there. The operator image uses a non-root user.

[jaronoff97]

i think this can probably be changed safely, im not sure why this was the case.