rhobs / rhobs/observability-operator
Monitor Pod Security Amission on OpenShift 4.12
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 51
- Forks
- 90
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 22
Description
Authz team has delayed restricted-by-default pod security admission until 4.12, however on 4.12 we will have to comply with it. This is problematic because this requires us to set SeccompProfiles, however we cannot simply set the profile since this will break releases > 4.12 since in those the SCC nonroot does not allow us to set SeccompProfiles see https://github.com/rhobs/observability-operator/pull/164.
There a document for the plans for operators installed with OLM and Pod Security Amission.
For this issue to be solved we have to:
- Run ObO on 4.12 without problems
- Run ObO on 4.10 without problems (4.10 is not a typo as that was the latest release without the
nonroot-v2SCC which allows us to setSeccompProfiles)
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 reviewing the linked PR #164 and the Pod Security Admission plan for operators installed with OLM. Identify the operator configuration and release paths affected, then verify completion by running ObO on OpenShift 4.12 and 4.10 without problems.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100