Closed yanehi closed 1 year ago
In the values you can set the securityContext on container level, but the corresponding key is missing in the deployment.
The setting of the securityContext for the kube-rbac-proxy container has also been added.
Optionally, the securityCotext for the manager and kube-rbac-proxy container can be set.
@yanehi Image is available for testing. docker pull stakater/ingressmonitorcontroller:SNAPSHOT-PR-504-999516eb
docker pull stakater/ingressmonitorcontroller:SNAPSHOT-PR-504-999516eb
hi @yanehi , thanks for the PR, i will test this soon and will try to resolve why tests are failing.
Problem
In the values you can set the securityContext on container level, but the corresponding key is missing in the deployment.
The setting of the securityContext for the kube-rbac-proxy container has also been added.
Solution
Optionally, the securityCotext for the manager and kube-rbac-proxy container can be set.