fetch upstream#5
Open
bluehawk27 wants to merge 611 commits intodoc-ai:developfrom
Open
Conversation
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
… sentry components (#1599)
Introduce a new configuration option `noStrictOffsetReset` in the Snuba replacer deployment template and values file. This allows users to optionally disable strict offset reset behavior by setting `noStrictOffsetReset` to true in the `values.yaml` file. This change provides more flexibility in handling offset resets, which can be useful in certain deployment scenarios where strict offset management is not required or desired.
…1622) Co-authored-by: Michał Zgliński <michal@cloudart.pl>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…1662) Co-authored-by: Anton Patsev <patcev_aa@magnit.ru>
Add global.volumeMounts to values and documentation, and apply it consistently to workload templates so shared mounts can be injected without maintaining a fork-only patchset.
…2063) Co-authored-by: Milan Reljin <milanreljin@rivianvw.tech>
Co-authored-by: Milan Reljin <milanreljin@rivianvw.tech>
… drops during redeployment (#2078) * feat: Add optional memory-based autoscaling to all HPA components * fix(relay): add explicit RollingUpdate strategy to prevent connection drops during redeployment The relay deployment had no deployment strategy configured, unlike the web deployment which explicitly sets `strategyType: RollingUpdate`. Without an explicit strategy, redeployments could terminate all relay pods simultaneously, causing client connections to drop. This adds a configurable `strategyType` field (defaulting to `RollingUpdate`) to the relay deployment spec, matching the pattern used by the web component. Backward compatible: the template uses `| default "RollingUpdate"` so existing deployments that do not specify `relay.strategyType` in their values will continue to work without any changes. Made-with: Cursor
Missing keeper port & image
…chart (#2064) ## ### Summary The upstream sentry chart (v29.3.0) has a bug in `templates/sentry/taskscheduler/deployment-taskscheduler.yaml` where the arguments to the Sprig `default` function are reversed: # Before (broken) — always evaluates to 1 replicas: {{ default .Values.sentry.taskScheduler.replicas 1 }} # After (fixed) — uses the configured value, falls back to 1 replicas: {{ default 1 .Values.sentry.taskScheduler.replicas }}
…tion (#2089) * feat: Add optional memory-based autoscaling to all HPA components * fix(relay): escape sed special characters in SASL credential substitution The sentry-relay-config-render init container uses sed to substitute KAFKA_SASL_* variables into the relay config.yml. Characters that are special in sed replacement strings (&, |, \) in the credential values cause the substitution to produce a corrupted config, breaking Kafka SASL authentication for Relay. Escape the three variables before passing them to sed so that any special characters are treated as literals. Made-with: Cursor
* fix(kafka): topic provisioning for external Kafka cluster * fix: replace bitnamilegacy/kafka with apache/kafka in provisioning job * fix: move helm hook annotations to job metadata, remove ttlSecondsAfterFinished --------- Co-authored-by: Milan Reljin <milanreljin@rivianvw.tech>
…idecars, volumeMounts, and volumes (#2096)
* feat: per taskbroker & taskworker resources * fix: mergeOverwrite
* feat(symbolicator): support existing PVC name * feat(vroom): support existing PVC name
…memory growth (#2126) Adds maxChildTaskCount field to taskWorker values, passed as --max-child-task-count to the taskworker command. This causes child processes to restart after N tasks, preventing memory accumulation that leads to OOMKill. Mirrors the fix applied to self-hosted docker-compose in: getsentry/self-hosted#4279 Co-authored-by: Aleksei Kriuchkov <a.kriuchkov@strikerz.inc>
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
20 participants
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.
No description provided.