run-check container should not run as root
Summary
The run-check container in the upgrade-check pod wants to run as root.
For users who don't allow root containers in their clusters, the pod never starts and an upgrade is unable to proceed.
Reported (Zendesk, internal use) by a 750-seat premium customer.
Steps to reproduce
N/A
Configuration used
N/A
Current behavior
run-check container runs as root
Expected behavior
run-check container should not run as root
Versions
- Chart: v2.1.7
- Platform:
- Oracle Cloud Infrastructure (OCI)
- Kubernetes: (
kubectl version
)- Client: 1.14
- Server: 1.14
- Helm: (
helm version
)- Client: 2.14.2
- Server: 2.14.3
Relevant logs
(Please provide any relevate log snippets you have collected, using code blocks (```) to format)
Edited by Wei-Meng Lee