We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The default replica count for Sentry workers is 1 (see below)
https://github.com/sentry-kubernetes/charts/blob/develop/charts/sentry/values.yaml#L252
However, the ConfigMap has a hard-coded value of 3 replicas (see below).
https://github.com/sentry-kubernetes/charts/blob/develop/charts/sentry/templates/sentry/_helper-sentry.tpl#L352
This inconsistency could lead to resource allocation issues and potential service disruptions.
Consistent replica count across all configurations Configuration should be parameterised rather than hard-coded
N/A
Latest
No response
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open for 30 days with no activity.
Sorry, something went wrong.
I have to admit it feels a little wrong to mark this as stale when their has been no interaction from maintainers on it.
No branches or pull requests
Issue submitter TODO list
Describe the bug (actual behavior)
The default replica count for Sentry workers is 1 (see below)
https://github.com/sentry-kubernetes/charts/blob/develop/charts/sentry/values.yaml#L252
However, the ConfigMap has a hard-coded value of 3 replicas (see below).
https://github.com/sentry-kubernetes/charts/blob/develop/charts/sentry/templates/sentry/_helper-sentry.tpl#L352
This inconsistency could lead to resource allocation issues and potential service disruptions.
Expected behavior
Consistent replica count across all configurations
Configuration should be parameterised rather than hard-coded
values.yaml
N/A
Helm chart version
Latest
Steps to reproduce
N/A
Screenshots
N/A
Logs
N/A
Additional context
No response
The text was updated successfully, but these errors were encountered: