feat(snuba): add uptime consumer deployment configuration #1830
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.
This pull request introduces a significant update to the Sentry Helm charts, primarily focusing on renaming and restructuring components related to "subscription-consumer-results-eap-items" and introducing new configurations for "uptime-results" and "uptime-consumer." The changes aim to improve clarity, consistency, and functionality in deployment configurations.
Renaming and Refactoring Subscription Consumer:
The file
deployment-sentry-subscription-results-eap-items.yaml
was renamed todeployment-sentry-uptime-results.yaml
, and all references tosubscriptionConsumerResultsEapItems
were replaced withuptimeResults
in the deployment configuration. This includes updates to fields such asreplicas
,annotations
,podLabels
,affinity
,nodeSelector
,tolerations
,volumes
, andsecurityContext
. [1] [2] [3] [4] [5]The service account file
serviceaccount-sentry-subscription-results-eap-items.yaml
was renamed toserviceaccount-sentry-uptime-results.yaml
, with corresponding updates to the service account naming and enabling conditions.Addition of Snuba Uptime Consumer:
deployment-snuba-uptime-consumer.yaml
. This includes support for configurable replicas, environment variables, resource limits, liveness probes, and other deployment settings.Updates to Values Configuration:
values.yaml
, thesubscriptionConsumerResultsEapItems
section was replaced withuptimeResults
, and a newuptimeConsumer
section was added under thesnuba
configuration. These changes introduce default settings for replicas, liveness probes, and other deployment parameters. [1] [2]