Dialer pod does not conform to restricted pod security profile
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 365
- Forks
- 223
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 25
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the in-cluster dialer pod definition in the repository and inspect how its security context is configured. Compare the pod against the restricted pod security profile requirements named in the issue, then verify that the resulting deployment no longer produces warnings or fails under enforcement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100