rhobs / rhobs/observability-operator
set SecurityContext for operator pods
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 51
- Forks
- 90
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 22
Description
Our operator pods don't need any privileges, we should set the right security context so that we can run in namespaces that enforce the PodSecurityStandards.
https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
Our bundle and catalog resources might benefit as well.
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the operator pod definitions and the bundle and catalog resources mentioned in the issue. Read the linked Kubernetes security-context guidance and compare the resources with PodSecurityStandards requirements. Done means the applicable resources set non-privileged security contexts and can run in namespaces enforcing those standards.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100