You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Launcher Kubernetes Profiles need to be configurable from Site Spec #5
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.
Section order matters once there is more than one group. Launcher profiles resolve by level ([*] < [@group] < [user]), and file order breaks ties within a level, with the later section winning. LauncherKubernetesProfiles is a map, so sections render alphabetically. A user in both @alpha and @zeta always gets @zeta's settings, and the admin cannot change that. This already applies to standalone Workbench resources with overlapping groups.
The fix belongs in the Workbench type, not just Site. The site controller passes profiles through the same LauncherKubernetesProfiles map that standalone Workbench uses. Adding a Site field that fills that map would give Site group profiles with the same alphabetical tie-break. An ordered form (for example, a list of sections) on Workbench fixes both. Since LauncherKubernetesProfiles is part of v1beta1, that probably means a new field next to the existing map, with the map deprecated.
Resource profile order may be worth a look in the same pass.launcher.kubernetes.resources.conf is deliberately sorted (default first, then by CPU and memory), but the resource-profiles list in the generated [*] is sorted alphabetically. I haven't checked which one the session launch dropdown follows.
We're working through the same question for the Helm chart in rstudio/helm#944. Whatever shape we land on there could be mirrored here so the two stay consistent.
Activity
Address review findings (job 258)
khusmann commentedon Oct 2, 2026
A few notes for whoever picks this up, from looking at ordering in team-operator's renderers (context in #172):
additionalConfigsforlauncher.kubernetes.profiles.confis silently overwritten by the generated[*]section (additionalConfigs for launcher.kubernetes.profiles.conf is silently overwritten by generated profiles #173), so Site admins cannot add group or user launcher profiles at all.[*]<[@group]<[user]), and file order breaks ties within a level, with the later section winning.LauncherKubernetesProfilesis amap, so sections render alphabetically. A user in both@alphaand@zetaalways gets@zeta's settings, and the admin cannot change that. This already applies to standaloneWorkbenchresources with overlapping groups.Workbenchtype, not justSite. The site controller passes profiles through the sameLauncherKubernetesProfilesmap that standaloneWorkbenchuses. Adding a Site field that fills that map would give Site group profiles with the same alphabetical tie-break. An ordered form (for example, a list of sections) onWorkbenchfixes both. SinceLauncherKubernetesProfilesis part ofv1beta1, that probably means a new field next to the existing map, with the map deprecated.launcher.kubernetes.resources.confis deliberately sorted (defaultfirst, then by CPU and memory), but theresource-profileslist in the generated[*]is sorted alphabetically. I haven't checked which one the session launch dropdown follows.We're working through the same question for the Helm chart in rstudio/helm#944. Whatever shape we land on there could be mirrored here so the two stay consistent.