posit-dev / posit-dev/team-operator
Launcher config gaps break Workbench features that read launcher settings from rserver.conf (AgentsView)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10
- Forks
- 1
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
Workbench reads some launcher settings from rserver.conf rather than the launcher's own config files. The operator renders some of those and not others, which makes features depending on them unreachable even though the launcher is configured correctly. Found while enabling AgentsView (rstudio-pro#12532).
Environment: team-operator v1.31.0, Workbench 2026.09.0-daily-165.pro1, single Kubernetes cluster, kubernetes-namespace=posit-team, use-templating=1.
launcher-sessions-container-image is not rendered into rserver.conf
The operator renders the session init container image but not the session image. From the rendered rserver.conf (ConfigMap <site>-workbench):
launcher-sessions-auto-update=1
launcher-sessions-init-container-image-name=ghcr.io/posit-dev/workbench-session-init-preview
launcher-sessions-init-container-image-tag=2026.09.0-daily-165.pro1
spec.workbench.defaultSessionImage reaches only launcher.kubernetes.profiles.conf, as default-container-image and container-images. That is correct for launching sessions, but Workbench also needs a server-level default: serviceJobImage() (rstudio-pro#12532) resolves AgentsView's service job image from agentsview-container-image, falling back to launcher-sessions-container-image — both rserver options. With neither set it returns empty, cluster selection skips container-capable clusters, and AgentsView cannot be scheduled at all.
Verified fix — adding this via workbench.additionalConfigs, same value as spec.workbench.defaultSessionImage, scheduled the service job immediately and the homepage Agents tab appeared:
launcher-sessions-container-image=<ecr>/agave-session-images:ubuntu2204-r4.5.2_...
Request: render launcher-sessions-container-image from spec.workbench.defaultSessionImage, alongside the init-container options already emitted.
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
Find the rendering path for rserver.conf and the existing launcher-sessions-init-container-image settings, then trace spec.workbench.defaultSessionImage. Render launcher-sessions-container-image alongside the init-container options and verify that the generated ConfigMap contains the expected value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100