openshift / openshift/machine-config-operator
Simplify controller architecture, merge "operator" and "controller"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 269
- Forks
- 529
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 83
Description
The operator controller for deploying the core controller is an extraneous layer. The "controller" is the operator, it handles the operational logic specific to this operator (the machine configuration). Other operators exist to handle deploying the operators themselves (CVO in this case,.
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 tracing the operator controller and core controller entry points, then review how the machine configuration operational logic is separated from deployment logic. Compare the current structure with the CVO deployment role and define the resulting controller boundary before changing implementation or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100