chart/redpanda: Set securityContext.runAsNonRoot to false for tuning container #1165
Conversation
RafalKorepta
requested review from
andrewstucki,
chrisseto and
gene-redpanda
as code owners
RafalKorepta
force-pushed
the
rk/gh-1162/security-context-set-to-false
branch
from
b6dc34d to
6eea667
Compare
chrisseto
left a comment
chrisseto
left a comment
There was a problem hiding this comment.
Can we backport this to at least v2.4.x?
And just to check, did we verify that this works as expected? There are no test cases where statefulset.podTemplate.spec.securityContext.runAsNonRoot is set to true.
|
This PR is stale because it has been open 5 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
This PR is stale because it has been open 5 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
This PR was closed because it has been stalled for 5 days with no activity. |
|
This PR is stale because it has been open 5 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
This PR is stale because it has been open 5 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
This PR is stale because it has been open 5 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
I can confirm that running the following command: where the test.yaml file contains: statefulset:
podTemplate:
spec:
initContainers:
- name: tuning
securityContext:
runAsNonRoot: trueresults with the following error: |
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
|
@RafalKorepta I think you forgot 25.3, I think 2.4.x and 2.3.x are optional to backport. |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
All credits goes to @maksym-iv.
Fixes #1162