Repository navigation
Dialer pod does not conform to restricted pod security profile #3517
Description
The in-cluster dialer pod used during deployment does not set the
security context fields required by the "restricted" pod security
profile: allowPrivilegeEscalation, capabilities drop, runAsNonRoot,
and seccompProfile.
This produces warnings on clusters enforcing pod security admission
and will fail on clusters that enforce (rather than warn) the
restricted profile.
Related: SRVOCF-445
Activity
Ankitsinghsisodya commentedon Apr 16, 2026
/assign
fix: conform dialer and volume-uploader pods to restricted pod securi…
Itx-Psycho0 commentedon May 6, 2026
Hi @lkingland , @matejvasek , I noticed this was reopened after #3614 was merged, which means the previous fix didn't fully address the issue. I'd like to take this on. I've been going through the codebase and understand the problem. The dialer pod is missing the required restricted security context fields like allowPrivilegeEscalation, capabilities drop, runAsNonRoot, and seccompProfile. I'll start by reviewing what #3614 did and identifying what was missed. Could you assign this to me?
matejvasek commentedon May 7, 2026
@Itx-Psycho0 has not this been fixed by @Ankitsinghsisodya ?
matejvasek commentedon May 7, 2026
If not you can work on it.
Itx-Psycho0 commentedon May 7, 2026
Thank you, @matejvasek. The fix in #3614 was partial, which is why @lkingland reopened it and unassigned @Ankitsinghsisodya last week. I'll take it from here and make sure all the missing fields are properly addressed.
/assign
github-actions commentedon Oct 31, 2026
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with
/reopen. Mark the issue asfresh by adding the comment
/remove-lifecycle stale.