Closed mack314 closed 3 years ago
node-cert-exporter requires hostPath
privileges and it might be that the Pod is assigned with a SecurityContextContraint that doesn't allow it. Can you verify that this i the case?
node-cert-exporter requires
hostPath
privileges and it might be that the Pod is assigned with a SecurityContextContraint that doesn't allow it. Can you verify that this i the case?
well for the error that caused my issue somehow I was using other cert image . Hence when I use the correct image I was able to resolve the issue.
Description I am deploying this as daemonset in openshift cluster . DS is unable to create containers & failing with below errors in event logs
Error: failed to start container "node-cert-exporter": Error response from daemon: oci runtime error: container_linux.go:235: starting container process caused "exec: \"--v=2\": executable file not found in $PATH"
Steps to reproduce the issue:
Describe the results you received: Error: failed to start container "node-cert-exporter": Error response from daemon: oci runtime error: container_linux.go:235: starting container process caused "exec: \"--v=2\": executable file not found in $PATH"
Describe the results you expected: no errors and containers should start successfully;
Additional information:
Output of
node-cert-exporter --version
:Additional environment details: