openshift / openshift/oadp-operator
Move NS priv label to OLM annotations
Open
Nobody has claimed this yet.
lifecycle/frozen
- Dominant language
- Go
- Stars
- 92
- Forks
- 93
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 43
Description
We would want to move this work to OLM annotation ([example](https://github.com/search?q=operatorframework.io%2Fsuggested-namespace-template+AND+pod-security.kubernetes.io%2Fenforce&ref=opensearch&type=code)) so we can delete this code.
Originally posted by @kaovilai in https://github.com/openshift/oadp-operator/pull/763#discussion_r1819659155
OLM will label on NS creation for us. We will be able to delete our code for this.
This should not break anything or require new changelog.
Just the ns will be labled before oadp-operator starts running.
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
Start by locating the code that applies the namespace security label and review the linked OLM annotation examples. Done means OLM owns the label on namespace creation, the operator-side code is removed, and existing behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100