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

kubeapps Postgresql Resource Settings are being ignored and stay default with HELM Chart Version 15.0.2 #25183

Closed
ILZ1105 opened this issue Apr 16, 2024 · 3 comments
Assignees
Labels
kubeapps solved stale 15 days without activity tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@ILZ1105
Copy link

ILZ1105 commented Apr 16, 2024

Name and Version

bitnami/kubeapps 15.0.2

What architecture are you using?

None

What steps will reproduce the bug?

  1. Use either a resourcepreset or dial in your required resources in the part for postgres
  2. Deploy the chart (done via kubeapps in my case)
  3. Check the resources of the pod or the respective statefulset
    The values are still the defaults:
    resources:
    limits:
    cpu: 150m
    ephemeral-storage: 1Gi
    memory: 192Mi
    requests:
    cpu: 100m
    ephemeral-storage: 50Mi
    memory: 128Mi

Are you using any custom parameters or values?

I've used resourcePreset: medium, nothing changed
I've dialed in the specific resources, nothing changed

resources:
requests:
cpu: 2
memory: 512Mi
limits:
cpu: 3
memory: 1024Mi

What is the expected behavior?

The resources are accordingly set to the statefulset and the respective pod.

What do you see instead?

I see the default values used, regardles of what I define in the values.yaml:

limits:
cpu: 150m
ephemeral-storage: 1Gi
memory: 192Mi
requests:
cpu: 100m
ephemeral-storage: 50Mi
memory: 128Mi

Additional information

Causes issues when kubeapps tries to sync the bitnami repo and potentially other repos. The DB can even crash multiple times and not accept any more requests because it's in recovery mode. It's constantly at the limit of 150m for CPU when it's synching Bitnami.

@ILZ1105 ILZ1105 added the tech-issues The user has a technical issue about an application label Apr 16, 2024
@ILZ1105 ILZ1105 changed the title Postgresql Resource Settings are being ignored and stay default with HELM Chart Version 15.0.2 kubeapps Postgresql Resource Settings are being ignored and stay default with HELM Chart Version 15.0.2 Apr 16, 2024
@github-actions github-actions bot added the triage Triage is needed label Apr 16, 2024
@javsalgar
Copy link
Contributor

Hi,

Looking at the values.yaml there is an error. It shouldn't be postgresql.resources / postgresql.resourcesPreset but postgresql.primary.resources and postgresql.primary.resourcesPreset

Copy link

github-actions bot commented May 4, 2024

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label May 4, 2024
Copy link

github-actions bot commented May 9, 2024

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@github-actions github-actions bot added the solved label May 9, 2024
@bitnami-bot bitnami-bot closed this as not planned Won't fix, can't repro, duplicate, stale May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kubeapps solved stale 15 days without activity tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Development

No branches or pull requests

3 participants