stackabletech / stackabletech/secret-operator
Split controller into a separate deployment
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13
- Forks
- 8
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 10
Description
Currently the DaemonSet owns responsibility for both controller and node-driver duties. We should split that up, and deploy the controller duties (both CSI and kube-rs controllers) as a separate Deployment.
listener-operator has done this all the way since https://github.com/stackabletech/listener-operator/pull/1, but we never got around to porting that back to secret-operator.
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 inspecting how secret-operator currently combines controller and node-driver duties in its DaemonSet. Compare that structure with listener-operator and the referenced pull request. Done means CSI and kube-rs controller duties run in a separate Deployment while node-driver duties remain in the DaemonSet.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100