posit-dev / posit-dev/team-operator
team-operator: Improve conditional volume/mount handling
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 10
- Forks
- 1
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
Summary
Improve patterns for appending conditional volumes and volume mounts in product deployments.
Context
From README TODO:
- "A better way to append conditional volumes / volume mounts / etc. (Organize, append arrays, etc.)"
- "Related: a way to toggle some of the persistence? We depend heavily on a functional storage class...?"
Scope
- Better organization for conditional volume/mount arrays
- Ability to toggle persistence for environments without reliable storage classes
- Handle volume migration scenarios gracefully
Acceptance Criteria
- Refactor volume/mount handling to be more maintainable
- Add option to disable persistence when storage class is unavailable
- Document the pattern for conditional resource arrays
Migrated from rstudio/ptd#2666
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 with the README TODO and locate the deployment code that assembles conditional volumes and volume mounts. Review how persistence and storage-class assumptions are currently represented, then define the maintainable array pattern, persistence toggle, migration behavior, and documentation required by the acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100