Skip to content
New issue

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

Do not set .spec.replicas for store-gateway if autoscaling is enabled #472

Closed
alex-berger opened this issue Jun 27, 2023 · 2 comments · Fixed by #480
Closed

Do not set .spec.replicas for store-gateway if autoscaling is enabled #472

alex-berger opened this issue Jun 27, 2023 · 2 comments · Fixed by #480
Assignees
Labels
bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed

Comments

@alex-berger
Copy link

If a HorizontalPodAutoscaler (HPA) is in place, one must not explicitly set .spec.replicas on the corresponding workload (StatefulSet or Deployment). Failing to adhere to that rule can cause severe service outage as the workload is scaled down unexpectedly and then might crash as it immediately gets overloaded (RAM or CPU).

In https://github.com/cortexproject/cortex-helm-chart/blob/master/templates/store-gateway/store-gateway-statefulset.yaml#L13

  replicas: {{ .Values.store_gateway.replicas }}

should actually be:

  {{- if not .Values.store_gateway.autoscaling.enabled }}
  replicas: {{ .Values.store_gateway.replicas }}
  {{- end }}
@nschad nschad added bug Something isn't working help wanted Extra attention is needed good first issue Good for newcomers labels Jun 28, 2023
@nschad
Copy link
Collaborator

nschad commented Jun 28, 2023

Thanks.

Do you want to give it a go?

@husnialhamdani
Copy link
Contributor

Hi @nschad,
I Interested to work on it, can you please assign to me?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants