docs(self-hosted): Clarify Kubernetes support boundary - #18987
Open
ENCHIGO wants to merge 2 commits into
Open
Conversation
State that the maintained deployment uses Docker Compose and direct questions about the community Helm chart to its own tracker.
|
@ENCHIGO is attempting to deploy a commit to the Sentry Team on Vercel. A member of the Team first needs to authorize it. |
ENCHIGO
marked this pull request as ready for review
August 10, 2026 02:44
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DESCRIBE YOUR PR
Clarifies that the maintained self-hosted deployment uses Docker Compose and that Sentry does not publish or support Kubernetes manifests or Helm charts. The page now directs questions about the unaffiliated community Helm chart to that project's issue tracker.
This keeps the documentation aligned with maintainer responses in getsentry/self-hosted#2607, getsentry/self-hosted#3280, getsentry/self-hosted#4006, and getsentry/self-hosted#4212 without presenting the third-party chart as an official deployment method.
IS YOUR CHANGE URGENT?
PRE-MERGE CHECKLIST
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.