redhat-cop / redhat-cop/gitops-catalog
sealed-secrets drops a warning
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 383
- Forks
- 184
- PR merge metrics
- No merged PRs in 30d
Description
this is just beauty/confusion... when reusing the sealed-secrets I get
W0502 18:15:57.469772 441936 warnings.go:70] would violate PodSecurity "restricted:v1.24": allowPrivilegeEscalation != false (container "sealed-secrets-controller" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "sealed-secrets-controller" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or container "sealed-secrets-controller" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container "sealed-secrets-controller" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")
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
The issue names sealed-secrets and reports a PodSecurity restricted:v1.24 warning, but provides no file, test, or explicit acceptance criterion. Start by locating the sealed-secrets manifests and determine whether the warning is expected; the desired outcome should be clarified before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100