We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, the target allocator is run as root. This prevents the target allocator from being run in OpenShift without special capabilities.
When the target allocator pod is created, the following error can be seen in the kubectl describe <pod name> command output:
kubectl describe <pod name>
Warning Failed 12s (x2 over 12s) kubelet Error: container create failed: time="2023-01-03T15:56:58Z" level=error msg="runc create failed: unable to start container process: exec: \"./main\": stat ./main: permission denied"
$ kubectl create namespace oteltest
$ kubectl -n oteltest create rolebinding default-view-oteltest --role=pod-view --serviceaccount=oteltest:ta
$ kubectl create -f tests/e2e/targetallocator-features/00-install.yaml -n oteltest:ta
$ kubectl get pods -n oteltest
Note The step 4 is executed manually because, when applying the manifest, it will fail because the TestStep kind is part of KUTTL.
4
TestStep
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Currently, the target allocator is run as root. This prevents the target allocator from being run in OpenShift without special capabilities.
When the target allocator pod is created, the following error can be seen in the
kubectl describe <pod name>
command output:How to reproduce
$ kubectl create namespace oteltest
$ kubectl -n oteltest create rolebinding default-view-oteltest --role=pod-view --serviceaccount=oteltest:ta
$ kubectl create -f tests/e2e/targetallocator-features/00-install.yaml -n oteltest:ta
$ kubectl get pods -n oteltest
)The text was updated successfully, but these errors were encountered: