chore(deps): update helm release sentry to v34 #163
Open
renovate-bot
wants to merge 1 commit from
renovate/sentry-34.x into main
pull from: renovate/sentry-34.x
merge into: ops:main
ops:main
ops:renovate/node-feature-discovery-0.x
ops:renovate/ghcr.io-mogenius-helm-charts-renovate-operator-5.x
ops:renovate/docker.io-binwiederhier-ntfy-2.x
ops:renovate/ghcr.io-scanopy-scanopy-server-0.x
ops:renovate/ghcr.io-diced-zipline-4.x
ops:renovate/ghcr.io-prometheus-community-charts-prometheus-operator-crds-32.x
ops:renovate/ghcr.io-rommapp-romm-5.x
ops:renovate/ghcr.io-paperless-ngx-paperless-ngx-3.x
ops:renovate/admonstrator-paperless-ai-next-2026.x
ops:renovate/ghcr.io-perfectra1n-kubesearch-mcp-1.x
ops:renovate/registry.erwanleboucher.dev-eleboucher-charts-memini-0.x
ops:renovate/ghcr.io-prymitive-karma-0.x
ops:renovate/loki-7.x
ops:renovate/ghcr.io-stacklok-toolhive-toolhive-operator-crds-0.x
ops:renovate/ghcr.io-stacklok-toolhive-toolhive-operator-0.x
ops:renovate/ghcr.io-mogenius-helm-charts-renovate-operator-6.x
ops:renovate/docker.io-healthchecks-healthchecks-5.x
ops:renovate/ghcr.io-atuinsh-atuin-18.x
ops:renovate/uv_build-0.x
ops:renovate/ghcr.io-home-operations-kromgo-0.x
ops:renovate/ghcr.io-home-operations-charts-echo-0.x
ops:renovate/ghcr.io-siderolabs-installer-1.13.x
ops:renovate/gitlab-9.x
ops:renovate/ghcr.io-ellite-wallos-5.x
ops:renovate/gitlab-10.x
ops:renovate/tailscale-operator-1.x
ops:renovate/ghcr.io-goauthentik-server-2026.x
ops:renovate/kube-prometheus-stack-92.x
ops:renovate/containers.podman-1.x
ops:renovate/ghcr.io-helmforgedev-helm-kubernetes-mcp-server-1.x
ops:renovate/ghcr.io-gethomepage-homepage-2.x
ops:renovate/ghcr.io-sysadminsmedia-homebox-0.x
ops:renovate/codefloe.com-crowci-crow-2.x
ops:renovate/ghcr.io-spegel-org-helm-charts-spegel-0.x
ops:renovate/external-secrets-2.x
ops:renovate/kube-prometheus-stack-87.x
ops:renovate/code.forgejo.org-forgejo-helm-forgejo-17.x
ops:renovate/forgejo-1.x
ops:renovate/cilium-1.x
ops:renovate/gitlab-agent-2.x
ops:renovate/python-3.x
ops:renovate/registry.gitlab.com-fmd-foss-fmd-server-0.x
ops:renovate/ghcr.io-gotson-komga-1.x
ops:renovate/open-webui-17.x
ops:renovate/ghcr.io-archivebox-archivebox-0.x
ops:renovate/ghcr.io-muety-wakapi-2.x
ops:renovate/ghcr.io-controlplaneio-fluxcd-charts-flux-operator-0.x
ops:renovate/quay.io-oauth2-proxy-oauth2-proxy-7.x
ops:renovate/external-dns-1.x
ops:renovate/plugin-barman-cloud-0.x
ops:renovate/reloader-2.x
ops:renovate/longhorn-1.x
ops:renovate/cloudnative-pg-0.x
ops:renovate/nvidia-device-plugin-0.x
ops:renovate/goldilocks-11.x
ops:renovate/quay.io-jetstack-charts-trust-manager-0.x
ops:renovate/lscr.io-linuxserver-faster-whisper-3.x
ops:renovate/goldilocks-10.x
ops:renovate/ghcr.io-sissbruecker-linkding-1.x
ops:renovate/ghcr.io-navidrome-navidrome-0.x
ops:renovate/authentik-2026.x
ops:renovate/random-3.x
ops:renovate/mirror.gcr.io-envoyproxy-gateway-helm-1.x
ops:renovate/johly-airtrail-3.x
ops:renovate/nvidia-gpu-exporter-2.x
ops:renovate/metrics-server-3.x
ops:renovate/altinity-clickhouse-operator-0.x
ops:renovate/ghcr.io-usememos-memos-0.x
ops:renovate/ghcr.io-siderolabs-kubelet-1.x
ops:renovate/ghcr.io-remsky-kokoro-fastapi-gpu-0.x
ops:renovate/kubernetes.core-6.x
ops:renovate/quay.io-jetstack-charts-cert-manager-1.x
ops:renovate/ghcr.io-siderolabs-kubelet-1.34.x
ops:renovate/ghcr.io-siderolabs-charts-talos-cloud-controller-manager-0.x
ops:renovate/crowci-0.x-lockfile
ops:renovate/quay.io-thanos-thanos-0.x
ops:renovate/open-webui-15.x
ops:renovate/mail-5.x
ops:renovate/cert-manager-webhook-pdns-3.x
ops:renovate/bluesky-pds-0.x
ops:renovate/promtail-6.x
ops:renovate/loki-6.x
ops:renovate/github.com-imusmanmalik-cert-manager-mixin-1.x
ops:renovate/lock-file-maintenance
ops:renovate/bitwarden-secrets-1.x
ops:renovate/gitlab-19.x
ops:renovate/ruby-4.x
ops:renovate/plausible-analytics-3.x
ops:renovate/sops-1.x
ops:renovate/plausible-analytics-2.x
ops:renovate/ghcr.io-gethomepage-homepage-1.x
ops:renovate/ingress-nginx-4.x
ops:renovate/ghcr.io-rommapp-romm-4.x
ops:renovate/gabehf-koito-0.x
ops:renovate/willshersystems.sshd-0.x
ops:renovate/ghcr.io-prometheus-community-charts-prometheus-operator-crds-30.x
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".
No due date set.
Dependencies
No dependencies set.
Reference
ops/homelab!163
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/sentry-34.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
28.1.0→34.0.0Release Notes
sentry-kubernetes/charts (sentry)
v34.0.0Compare Source
Chart
34.0.0targets Sentry 26.10.0 and includes 26.9.0. No self-hosted hard stop lies between 26.8.0 and 26.10.0.Breaking: ClickHouse 25.8 required
Snuba 26.10.0 refuses to run migrations against ClickHouse older than
25.8.16. Upgrade your ClickHouse before upgrading the chart. Self-hosted and this chart's CI usealtinity/clickhouse-server:25.8.28.10001.altinitystable. Snuba now talks to ClickHouse over HTTP only, soexternalClickhouse.httpPort(default8123) must be reachable.Breaking: Sentry runs as non-root (uid/gid 999)
The sentry image no longer runs as root. Pods running it get a new default pod securityContext,
sentry.podSecurityContext(fsGroup: 999,fsGroupChangePolicy: OnRootMismatch), so Kubernetes makes the filestore and replay PVCs writable for uid 999. Each component's ownsecurityContextis merged over it.fsGroup(many NFS/RWX setups),chown -R 999:999the filestore volume once before upgrading. This matches self-hosted'sensure-sentry-data-ownership.sh.fsGroup: 999(e.g. OpenShift restricted SCC), setsentry.podSecurityContext.fsGroupand.fsGroupChangePolicytonulland give the volume an ownership that uid 999 can write.Breaking: vroom S3 bucket URL parameters
vroom's storage library renamed the S3 URL query parameters. If
vroom.persistence.bucketStringpoints at an S3-compatible store, replaces3ForcePathStyle=truewithuse_path_style=trueanddisableSSL=truewithdisable_https=true. Thefile://default and plains3://bucket/gs://bucketURLs are unaffected.Removed components
Remove any overrides for these keys from your values:
sentry.processSegments: segments are processed by thesentry.spans.process_segments.process_segmenttask on the default TaskBroker (theprocess-segmentsconsumer no longer exists in Sentry).sentry.genericMetricsConsumer,snuba.genericMetricsCountersConsumer,snuba.subscriptionConsumerGenericMetricsCounters, and thegeneric-metrics-subscription-resultstopic on theproductsTaskBroker: Sentry, Snuba and Relay no longer produce or consume generic metrics. If you fully overridesentry.taskBroker.brokers, drop that topic yourself.Other
python3instead ofsh, because the snuba image no longer ships a shell.buffered-segments-dlqtopics fromkafka.provisioning.topics. Existing topics are not deleted. Optionally delete these leftover consumer groups as self-hosted does:billing-metrics-consumer,snuba-gen-metrics-distributions-consumers,snuba-gen-metrics-gauges-consumers,snuba-gen-metrics-sets-consumers.organizations:incidentsfeature flag, thegeneric_metrics_*Snuba storage sets, and Relay'smetrics_generictopic mapping.v33.8.0: sentry: v33.8.0Compare Source
Features
v33.7.0: sentry: v33.7.0Compare Source
Features
v33.6.0: sentry: v33.6.0Compare Source
Features
v33.5.0: sentry: v33.5.0Compare Source
Features
v33.4.0Compare Source
Chart
33.4.0targets Sentry 26.8.0.ingest-replay-recordingsrawtopic,sentry.replays.tasks.process_replay_recording). Leftoversentry.ingestReplayRecordingsoverrides are ignored. If you fully overridesentry.taskBroker.brokers, add that topic yourself (same pattern asprofiles).sentry.billingMetricsConsumer, Snuba generic-metrics gauges/sets/distributions (consumers and subscription schedulers). Counters stay (snuba.genericMetricsCountersConsumer,snuba.subscriptionConsumerGenericMetricsCounters).kafkaSessionTimeoutMsdefaults to60000(self-hostedkafka_session_timeout_ms).autoOffsetReset: earliestandnoStrictOffsetReset: true(self-hosted--auto-offset-reset=earliest --no-strict-offset-reset).weed miniKEK migration. Those do not apply to this chart (Bitnami Redis / external Kafka / noweed mini).v33.3.1: sentry: v33.3.1Compare Source
Bug Fixes
v33.3.0: sentry: v33.3.0Compare Source
Features
Bug Fixes
v33.2.0: sentry: v33.2.0Compare Source
Features
Bug Fixes
v33.1.0: sentry: v33.1.0Compare Source
Features
Bug Fixes
v33.0.0Compare Source
Chart
33.0.0targets Sentry 26.7.0.Breaking: TaskBroker Kafka config
TaskBroker no longer uses legacy
TASKBROKER_KAFKA_TOPIC/TASKBROKER_KAFKA_CONSUMER_GROUPenv vars. Eachsentry.taskBroker.brokers[]entry must providekafkaDeadletterTopic,kafkaRetryTopic, andkafkaTopics(YAML config mounted into the broker). Cluster address/auth useTASKBROKER_KAFKA_CLUSTERS__DEFAULT__*.Before:
After: see default
values.yaml(kafkaTopics, including optionalrawblocks for subscription results and profiles).Hyphenated topic names require the YAML config file; they cannot be set via env vars. See the taskbroker Kafka config migration guide.
Breaking: Removed Sentry consumers (moved to TaskBroker raw mode)
These Deployments and related values keys are removed. Work is consumed by TaskBroker
rawtopics (products broker for subscription results; ingest broker forprofiles):sentry.subscriptionConsumerEventssentry.subscriptionConsumerTransactionssentry.subscriptionConsumerMetricssentry.subscriptionConsumerGenericMetricssentry.subscriptionConsumerResultsEapItemssentry.ingestProfilesRemove any overrides for these keys from your values. Snuba subscription scheduler/executor Deployments (
snuba.subscriptionConsumer*) are unchanged.Other
maxPollIntervalMs: 300000(parity with self-hostedSENTRY_KAFKA_MAX_POLL_INTERVAL_MS); set a consumer'smaxPollIntervalMs: nullto omit--max-poll-interval-msnginx.ingress.kubernetes.io/proxy-read-timeout: "90"(self-hosted nginxproxy_read_timeoutbump)v32.3.0: sentry: v32.3.0Compare Source
Features
Bug Fixes
v32.2.0: sentry: v32.2.0Compare Source
Features
v32.1.0: sentry: v32.1.0Compare Source
Features
Bug Fixes
v32.0.0Compare Source
snuba.rustConsumer: falseto revert.distutils.strtoboolfromsentry.conf.pytemplate — mail TLS/SSL now uses.lower() in ("true", "1", "yes").v31.7.1: sentry: v31.7.1Compare Source
Bug Fixes
v31.7.0Compare Source
Chart
31.7.0adds configuration for Sentry 26.5.0 that was not included whenappVersionwas bumped in31.4.0:feature-completeprofile): newlaunchpad-taskworkerDeployment andLAUNCHPAD_RPC_SHARED_SECRETon Sentry pods.organizations:tracemetrics-*feature flags are enabled in generatedsentry.conf.py.Launchpad RPC shared secret
When Launchpad is enabled (
launchpadTaskWorker.enabled=true, the default withfeature-complete), the chart automatically creates a shared RPC secret (<release-fullname>-launchpad-secret) via a Helm hook on both install and upgrade. The secret is only created if it does not already exist, so existing secrets are preserved.If you do not need Launchpad, set
launchpadTaskWorker.enabled=false, or use theerrors-onlyprofile.v31.6.0: sentry: v31.6.0Compare Source
Features
Bug Fixes
v31.5.1: sentry: v31.5.1Compare Source
Bug Fixes
v31.5.0: sentry: v31.5.0Compare Source
Features
Bug Fixes
v31.4.0: sentry: v31.4.0Compare Source
Features
v31.3.1: sentry: v31.3.1Compare Source
Bug Fixes
v31.3.0: sentry: v31.3.0Compare Source
Features
Bug Fixes
v31.2.0: sentry: v31.2.0Compare Source
Features
v31.1.0: sentry: v31.1.0Compare Source
Features
v31.0.0: sentry: v31.0.0Compare Source
⚠ BREAKING CHANGES
Features
Bug Fixes
v30.4.0: sentry: v30.4.0Compare Source
Features
v30.3.1: sentry: v30.3.1Compare Source
Bug Fixes
v30.3.0: sentry: v30.3.0Compare Source
Features
Bug Fixes
v30.2.0: sentry: v30.2.0Compare Source
Features
Bug Fixes
v30.1.0: sentry: v30.1.0Compare Source
Features
Bug Fixes
v30.0.1: sentry: v30.0.1Compare Source
Bug Fixes
v30.0.0: sentry: v30.0.0Compare Source
⚠ BREAKING CHANGES
Features
Bug Fixes
v29.5.1: sentry: v29.5.1Compare Source
Bug Fixes
v29.5.0: sentry: v29.5.0Compare Source
Features
Bug Fixes
v29.4.1: sentry: v29.4.1Compare Source
Bug Fixes
v29.4.0: sentry: v29.4.0Compare Source
Features
Bug Fixes
v29.3.0: sentry: v29.3.0Compare Source
Features
Bug Fixes
v29.2.0: sentry: v29.2.0Compare Source
Features
v29.1.0: sentry: v29.1.0Compare Source
Features
Bug Fixes
v29.0.0: sentry: v29.0.0Compare Source
⚠ BREAKING CHANGES
Features
Bug Fixes
Miscellaneous Chores
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.
flate diff
No differences detected.
Pipeline
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.