docs(connect): how to migrate `launcher.launcherKubernetesProfilesConf` to `backends.kubernetes.defaultResourceJobBase`
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
We currently say:
The direct Kubernetes runner does not use profiles. Similar customization can be achieved using defaultResourceJobBase.
We should show specific launcher profile fields and examples.
Launcher profile doc references:
- https://docs.posit.co/ide/server-pro/admin/job_launcher/kubernetes_plugin.html#kube-profiles
- https://docs.posit.co/ide/server-pro/admin/job_launcher/kubernetes_plugin.html#kube-resource-profiles
example of a user asking about this use case: https://rstudioide.zendesk.com/agent/tickets/130026
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 the linked launcher-to-Kubernetes migration page, especially the “Values with alternatives” section, and compare it with the linked Kubernetes profile documentation. Add specific launcher profile fields and corresponding defaultResourceJobBase examples for the migration use case. Done means the page clearly explains how to reproduce the relevant profile customizations without profiles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100