trigger.dev icon indicating copy to clipboard operation
trigger.dev copied to clipboard
Published 2 weeks ago • verified publisher icon triggerdotdev

docs(kubernetes): use v4 helm chart instead of beta

Open mstruebing opened this issue 2 months ago • 2 comments

✅ Checklist

  • [x] I have followed every step in the contributing guide
  • [x] The PR title follows the convention.
  • [x] I ran and tested the code works

Testing

[Describe the steps you took to test this change]

I've executed the commands on my own Kubernetes cluster and it works.

Changelog

[Short description of what has changed]

Updated the documentation to use the latest helm chart (v4) instead of beta.

Screenshots

[Screenshots]

Screenshot 2025-11-12 at 14 26 30

💯

mstruebing avatar Nov 12 '25 13:11 mstruebing

⚠️ No Changeset found

Latest commit: 2a9b9eafb950b9bb6bd1d7ab813da0482e01dd17

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

changeset-bot[bot] avatar Nov 12 '25 13:11 changeset-bot[bot]

Walkthrough

This pull request updates version identifiers in the Kubernetes self-hosting documentation from beta versions to stable releases. The changes replace version references (4.0.0-beta, 4.0.0-beta.5, ~4.0.0-beta) with their stable equivalents (4.0.0, 4.0.5, ~4.0.0) across multiple helm commands and configuration examples within the documentation file.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Single file modified with homogeneous changes (repetitive version string replacements)
  • Documentation-only updates with no functional code logic
  • Low cognitive load required to verify consistency of version updates

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately reflects the main change: updating Kubernetes documentation to use the stable v4 Helm chart instead of beta versions.
Description check ✅ Passed The PR description follows the template structure and includes all required sections with substantive content: checklist completed, testing details provided, changelog entry added, and screenshot included.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • [ ] Create PR with unit tests
  • [ ] Post copyable unit tests in a comment
📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f7cb637b3219fadb1c460a9207c8979f756f21c7 and 2a9b9eafb950b9bb6bd1d7ab813da0482e01dd17.

📒 Files selected for processing (1)
  • docs/self-hosting/kubernetes.mdx (4 hunks)
🧰 Additional context used
🧠 Learnings (5)
📓 Common learnings 
Learnt from: nicktrn
Repo: triggerdotdev/trigger.dev PR: 2195
File: hosting/k8s/helm/Chart.yaml:1-18
Timestamp: 2025-06-25T13:18:44.103Z
Learning: For the Trigger.dev Helm chart, the chart name should be "trigger" (not "trigger-v4") since this is the first official chart release. Helper templates should use the actual chart name from .Chart.Name rather than hardcoded prefixes.

Learnt from: nicktrn
Repo: triggerdotdev/trigger.dev PR: 2195
File: hosting/k8s/helm/templates/extra-manifests.yaml:1-4
Timestamp: 2025-06-25T13:18:04.827Z
Learning: In the Trigger.dev v4 Helm chart, the user prefers to rely on documentation and examples in values files rather than implementing defensive coding in templates, particularly for features like extraManifests where proper usage is documented.

Learnt from: nicktrn
Repo: triggerdotdev/trigger.dev PR: 2195
File: hosting/k8s/helm/values.yaml:22-51
Timestamp: 2025-06-25T13:20:17.174Z
Learning: In the Trigger.dev Helm chart values.yaml, the maintainer prefers to use explicit comprehensive warnings for security-sensitive default values rather than implementing secure-by-default behavior that would fail installation. The project uses deterministic default secrets with clear "TESTING ONLY" warnings and instructions for production deployment.
📚 Learning: 2025-06-25T13:18:44.103Z 
Learnt from: nicktrn
Repo: triggerdotdev/trigger.dev PR: 2195
File: hosting/k8s/helm/Chart.yaml:1-18
Timestamp: 2025-06-25T13:18:44.103Z
Learning: For the Trigger.dev Helm chart, the chart name should be "trigger" (not "trigger-v4") since this is the first official chart release. Helper templates should use the actual chart name from .Chart.Name rather than hardcoded prefixes.

Applied to files:

  • docs/self-hosting/kubernetes.mdx
📚 Learning: 2025-06-25T13:20:17.174Z 
Learnt from: nicktrn
Repo: triggerdotdev/trigger.dev PR: 2195
File: hosting/k8s/helm/values.yaml:22-51
Timestamp: 2025-06-25T13:20:17.174Z
Learning: In the Trigger.dev Helm chart values.yaml, the maintainer prefers to use explicit comprehensive warnings for security-sensitive default values rather than implementing secure-by-default behavior that would fail installation. The project uses deterministic default secrets with clear "TESTING ONLY" warnings and instructions for production deployment.

Applied to files:

  • docs/self-hosting/kubernetes.mdx
📚 Learning: 2025-06-25T13:18:04.827Z 
Learnt from: nicktrn
Repo: triggerdotdev/trigger.dev PR: 2195
File: hosting/k8s/helm/templates/extra-manifests.yaml:1-4
Timestamp: 2025-06-25T13:18:04.827Z
Learning: In the Trigger.dev v4 Helm chart, the user prefers to rely on documentation and examples in values files rather than implementing defensive coding in templates, particularly for features like extraManifests where proper usage is documented.

Applied to files:

  • docs/self-hosting/kubernetes.mdx
📚 Learning: 2025-02-10T10:54:17.345Z 
Learnt from: zvictor
Repo: triggerdotdev/trigger.dev PR: 1686
File: packages/build/src/extensions/python.ts:85-87
Timestamp: 2025-02-10T10:54:17.345Z
Learning: In Python-related Dockerfiles for trigger.dev, avoid adding explicit Python version pinning as the base image already provides conservative version management. Additional pinning would unnecessarily slow down builds.

Applied to files:

  • docs/self-hosting/kubernetes.mdx
🔇 Additional comments (2)
docs/self-hosting/kubernetes.mdx (2)

64-64: Version updates are consistent and well-tested. ✓

All beta version references have been updated to stable releases with a consistent strategy:

  • Flexible minor-version ranges (~4.0.0) for testing/standard deployments
  • Pinned versions (4.0.5) for production stability

The changes align with the stable v4 Helm chart release and have been validated on a live cluster per the PR description.

Also applies to: 110-110, 114-114, 174-174, 492-492, 499-499

112-114: Comment clarifies the version strategy well.

The "# Latest v4" comment helps users understand the difference between the two version commands above it (specific version vs. latest stable).

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

coderabbitai[bot] avatar Nov 12 '25 13:11 coderabbitai[bot]