docs(connect): how to migrate `launcher.launcherKubernetesProfilesConf` to `backends.kubernetes.defaultResourceJobBase`

Open Beginner friendly
#888 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
helm
Domain
documentation

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.

Description

team: connect

https://docs.posit.co/helm/examples/connect/upgrade-launcher-to-kubernetes/launcher-to-kubernetes.html#values-with-alternatives

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:

example of a user asking about this use case: https://rstudioide.zendesk.com/agent/tickets/130026

Dominant language
Markdown
Stars
46
Forks
40
Avg merge
4h 3m
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rstudio/helm

All issues in rstudio/helm

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.