[WORKBENCH] Incorrect order of Launcher.profiles
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
I am using Workbench Kubernetes in AKS, where i want to use the launcher profiles to configure sessions for different users. I am using Helm chart version 0.5.26 to deploy Workbench.
I have four profiles in the following order in my helm values:
- @auto-az-workben-prod-base-r
- @auto-az-workben-prod-medium-r
- @auto-az-workben-prod-large-r
- @auto-az-workben-prod-gpu-r
When i look into the Workbench pod where it is mounted, the order is not the same. It seems to be in alphabetical order as follows:
- @auto-az-workben-prod-base-r
- @auto-az-workben-prod-gpu-r
- @auto-az-workben-prod-large-r
- @auto-az-workben-prod-medium-r
From your documentation (https://docs.posit.co/job-launcher/latest/kube.html) you write that the profiles are ordered from top to bottom, which is not the case.
See the attached images for more detail
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 by comparing the Helm values defining launcher profiles with the generated profiles mounted in the Workbench pod, then read the linked Kubernetes documentation on profile ordering. Determine where the declared order is lost; done means the mounted profiles and resulting session selection follow the values order, or the documentation clearly reflects the supported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100