posit-dev / posit-dev/team-operator
Launcher Kubernetes Profiles need to be configurable from Site Spec
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10
- Forks
- 1
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
Currently the Launcher Kubernetes Profiles are hardcoded to use all of the resource profiles under the wildcard header https://github.com/rstudio/ptd/blob/1fc957cb40a0ae34bb23b4e1a26a00864ae61ad5/team-operator/internal/controller/core/site_controller_workbench.go#L179-L190
This needs to change to support using multiple profiles. Currently not a pressing need but will come up with enterprise clients that want to specifically control access to resources.
Migrated from rstudio/ptd#2149
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 in team-operator/internal/controller/core/site_controller_workbench.go at the linked resource-profile handling, then trace how Site Spec values are represented and consumed. Determine the configuration shape needed to select multiple Launcher Kubernetes profiles instead of the wildcard set; done means profiles are controlled through Site Spec without relying on the hardcoded wildcard behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100