Skip to content

Add Kubernetes backend examples for Connect#843

Merged
lucasrod16 merged 15 commits intomainfrom
claude-issue-837-update-connect-examples-to-include-direct-kubernetes-runner-values
Apr 22, 2026
Merged

Add Kubernetes backend examples for Connect#843
lucasrod16 merged 15 commits intomainfrom
claude-issue-837-update-connect-examples-to-include-direct-kubernetes-runner-values

Conversation

@lucasrod16
Copy link
Copy Markdown
Contributor

@lucasrod16 lucasrod16 commented Apr 15, 2026 •
edited
Loading

Documentation-only change — no chart templates, values, or version bumps.

Summary

  • Add backends.kubernetes example values alongside existing Launcher examples for Connect categories that have launcher-specific customizations: app config, container images (custom + private), and storage
  • Examples that only set launcher.enabled without other customizations (OIDC, SAML) no longer reference the launcher at all
  • Update .qmd docs to show both Kubernetes and Launcher examples as separate sections, with Kubernetes first
  • Update index.qmd to describe both backends and link to the upgrade guide
  • Remove outdated default execution environments bootstrapping text from container image docs (see Remove default for launcher.customRuntimeYaml in Connect chart #847)

Test plan

  • All 4 new YAML files pass helm template validation
  • just test rstudio-connect passes (94 tests)
  • Posit style guide review passes (active voice, Oxford commas, product names, headings)
  • Verify rendered docs site

Closes #837
Closes #849

🤖 Generated with Claude Code

@lucasrod16 lucasrod16 force-pushed the claude-issue-837-update-connect-examples-to-include-direct-kubernetes-runner-values branch 2 times, most recently from 3aeed77 to 284d3cd Compare April 21, 2026 15:11
@lucasrod16 lucasrod16 changed the title Add direct Kubernetes runner examples for Connect Add Kubernetes backend examples for Connect Apr 21, 2026
@lucasrod16 lucasrod16 marked this pull request as ready for review April 21, 2026 19:06
@lucasrod16 lucasrod16 requested a review from a team as a code owner April 21, 2026 19:06
edavidaja
edavidaja reviewed Apr 21, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

@edavidaja edavidaja left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think, consistent with other changes here in this vein, we'd prefer for the direct k8s runner references to refer to the new images.

lucasrod16 and others added 13 commits April 21, 2026 15:06
@lucasrod16 @claude
Add direct Kubernetes runner examples for Connect
b9a5bb4 
Add backends.kubernetes equivalents alongside existing Launcher examples
for all Connect example categories (app config, auth, container images,
storage). Each .qmd doc uses tabbed panels with the recommended direct
Kubernetes runner shown first and Launcher labeled as legacy.

Update index.qmd to describe both backends and link to the upgrade guide.
Update private-images.qmd prose to mention executionEnvironments.

Closes #837

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@lucasrod16 @claude
Fix style guide findings and label Launcher as deprecated
b7cbe7c 
Use sentence case for "Direct Kubernetes runner" tab headings, fix
"enviornments" typo and "content contents" phrasing on modified lines,
and change "legacy" to "deprecated" for the Launcher backend label.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@lucasrod16 @claude
Remove deprecated/legacy labels and minimize naming the Kubernetes ba…
a8c2172 
…ckend

Drop parenthetical labels from tab headings — tabs are now just
"Kubernetes" and "Launcher". Remove "direct Kubernetes runner" phrasing
in favor of referencing the `backends.kubernetes` configuration directly.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@lucasrod16 @claude
Decouple executionEnvironments from backends.kubernetes in docs
2c5ea81 
executionEnvironments is independent of backends.kubernetes — remove
the parenthetical that incorrectly associated them, and drop the
"With backends.kubernetes" lead-in from the custom images description.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@lucasrod16 @claude
Broaden Kubernetes tab description to all Connect 2026.04.0+ users
f7438aa 
The backends.kubernetes approach applies to any installation running
Connect 2026.04.0+, not just new installations.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@lucasrod16 @claude
Replace tabbed panels with separate sections for each backend
817a6db 
Show both Kubernetes and Launcher examples as regular sections on
the same page instead of using Quarto tabbed panels.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@lucasrod16 @claude
Remove launcher.enabled from auth examples that have no other launche…
6abef42 
…r config

The OIDC and SAML examples only configure authentication — they have
no launcher-specific customizations (templateValues, customRuntimeYaml,
etc.), so they don't need separate Kubernetes examples or backend
sections. Remove the Kubernetes YAML files, backend sections from the
.qmd pages, and the bare launcher.enabled setting from the Launcher
YAML files.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@lucasrod16 @claude
Clarify that executionEnvironments is the recommended approach
9ecefa4 
Mark executionEnvironments as recommended in the shared description
and add upgrade guidance in the Launcher sections of both container
image pages.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@lucasrod16 @claude
Stop recommending customRuntimeYaml in container image docs
0d3a813 
Drop customRuntimeYaml references from shared descriptions and
Kubernetes sections. Launcher examples still use it for older
versions but the docs no longer draw attention to it.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@lucasrod16 @claude
Remove outdated default execution environments bootstrapping text
86b6be3 
The default-runtime.yaml bootstrapping behavior is being removed in
an upcoming PR, so drop the paragraph referencing it from both
container image doc pages.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@lucasrod16 @claude
Use 'and later' instead of '+' for version references in docs
401038a 
Spell out '2026.04.0 and later' in prose for clarity, rather than
relying on the '+' shorthand.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@lucasrod16 @claude
Also update YAML comments to use 'and later' for version references
739ee1f 
Consistent with the .qmd prose change.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@lucasrod16 @claude
Use new posit-dev/images-connect images in Kubernetes examples
a2a7d0b 
Update the Kubernetes custom image examples to reference the new
images from posit-dev/images-connect (connect, connect-content,
connect-content-init) instead of the legacy rstudio/rstudio-docker-products
images. Update the runtime versions to match the new content image tag
format (R4.5.2-python3.14.3-ubuntu-24.04) and drop the unneeded
ubuntu2204- tagPrefix.

Launcher examples continue to reference the legacy images since they
target older Connect versions.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@lucasrod16 lucasrod16 force-pushed the claude-issue-837-update-connect-examples-to-include-direct-kubernetes-runner-values branch from d8c3b8d to a2a7d0b Compare April 21, 2026 20:09
@lucasrod16 @claude
Set tagPrefix to empty in Kubernetes examples using posit-dev images
4b97825 
The chart's default tagPrefix is ubuntu2204-, which is appended to the
auto-filled appVersion tag. The new posit-dev/images-connect images do
not use that prefix (tags are just the version, like 2026.03.1), so
explicitly clear tagPrefix to produce a valid image reference.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
edavidaja
edavidaja reviewed Apr 21, 2026
View reviewed changes
Comment thread examples/connect/index.qmd Outdated
@lucasrod16 @edavidaja
Update examples/connect/index.qmd
62e3f14 
Co-authored-by: E. David Aja <david@posit.co>
@lucasrod16 lucasrod16 merged commit 158d173 into main Apr 22, 2026
7 checks passed
@lucasrod16 lucasrod16 deleted the claude-issue-837-update-connect-examples-to-include-direct-kubernetes-runner-values branch April 22, 2026 14:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@dbkegley dbkegley dbkegley approved these changes

@edavidaja edavidaja edavidaja approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

docs(connect): Update private/custom images documentation examples Update Connect examples to include direct Kubernetes runner values

3 participants

@lucasrod16 @dbkegley @edavidaja