stackabletech / stackabletech/trino-operator
Migrate from StatefulSet to Deployment
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 63
- Forks
- 13
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 12
Description
The PVCs created by the StatefulSet caused problems in the past, so https://github.com/stackabletech/trino-operator/issues/768 removed them.
In case we don't need PVCs any more, the question why even use a StatefulSet? I guess a StatefulSet was only chosen because "we always did it this way", we should IMHO use a Deployment instead.
Migrating to a Deployment should have the following benefits:
- Quicker rollout times for changes
- ... Maybe some other things
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 the operator's current StatefulSet implementation and issue #768, which removed the PVCs that motivated this proposal. Determine whether a Deployment is suitable without those PVCs and identify the rollout and state-management behavior that must be preserved; done means the operator uses a Deployment without requiring the removed PVCs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100