Multi cluster configuration
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
Description
Currently I am working on multicluster Posit Workbench setup.
I will have main cluster where Workbench will be installed and where people will be able to run workloads and second cluster dedicated for GPU workloads.
When trying to configure that I followed this documentation which is mentioning that I need to have two [cluster] configured in my /etc/rstudio/launcher.conf file.
Issue
Problem start when I try to implement that configuration via helm chart since current implementation of cluster is map and when I provide more cluster it is merge and only last one if present in configuration file.
When I edited ConfigMap responsible for /etc/rstudio/launcher.conf and added second cluster like it was mention in doc it is working but since this is hacky way of doing this I would like to implement it in a proper way.
Do you have any recommendations how to do that?
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 with charts/rstudio-workbench/values.yaml at the cluster configuration and trace how it renders /etc/rstudio/launcher.conf. Compare the Helm output with the linked multi-cluster documentation; done means both cluster entries are preserved in the generated configuration without editing the ConfigMap manually.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100