Closed ngingihy closed 2 years ago
Hi,
It seems to me that this is not related to the Bitnami packaging, but the configuration in your cluster. The error shows that you have a ResourceQuota object in the namespace that is forcing you to define the CPU and Memory limits.
hey @javsalgar, does that mean i need to specify it in the values.yaml file?
Hi,
Exactly, you may need to tweak the limit settings inside the PostgreSQL subchart. Check the PostgreSQL chart settings
https://github.com/bitnami/charts/blob/master/bitnami/postgresql/values.yaml
For these values, you need to add postgresql.
, as it is part of a subchart.
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.
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.
Name and Version
bitnami/kong
What steps will reproduce the bug?
I had Kong running normally on a previous namespace that i provisioned previously. Now i changed the namespace, it should have the same specs as the old one. I keep getting that error failed quota: ns-resource-quota: must specify limits.cpu,limits.memory. I'm using the exact same values.yaml file
These are namespace events (below). Looks like It doesn't happen for all pods.
Are you using any custom parameters or values?
What is the expected behavior?
No response
What do you see instead?
I'm seeing this error, i'm using a postgres bitnami image pulled from a private repo registry StatefulSet my-release-postgresql failed error: pods "my-release-postgresql-0" is forbidden: failed quota: ns-resource-quota: must specify limits.cpu,limits.memory
Additional information
No response