Order of resource profiles in configmap
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
When defining launcher.kubernetes.resources.conf in the helm chart like
The resulting configmap seems to "sort" the resource profiles putting the "100 %" at the start:
It would be nice to respect the order of which the resource profiles are put into values.yaml given the fact that it is the order of the profiles in launcher.kubernetes.resources.conf that determines the order the resource profiles are shown in the workbench UI.
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 locating the Helm chart template that renders launcher.kubernetes.resources.conf into the ConfigMap, then compare it with the resource profile order in values.yaml. Confirm the rendered ConfigMap preserves that order and that the workbench UI displays the profiles accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100