You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Is your feature request related to a problem? Please describe.
Many of the Kubernetes Jobs that are installed with Helm hooks (e.g., post-install, pre-delete, etc.) have hardcoded resource requests and limits. For instance:
On some of my Kubernetes environments where I install this Consul Helm chart, I get OOMKilled events on the Jobs with hardcoded requests and limits, blocking operations like Helm deletes, Helm installs, and Helm upgrades.
I can workaround this issue by installing Kyverno on the cluster and using a ClusterPolicy to mutate the resource requests and limits for these Jobs upon admission to the cluster, but I should not have to depend on Kyverno mutating policies to configure Consul properly in my clusters.
Feature Description
I would request you expose values in your Helm chart to allow me to customize the resource requests and limits for Jobs installed by the Chart.
Use Case(s)
All cases. This is fundamental to the management of the chart with Helm.
Contributions
I can contribute with a PR if desired. This is a small, low-risk change.
The text was updated successfully, but these errors were encountered:
Community Note
Is your feature request related to a problem? Please describe.
Many of the Kubernetes Jobs that are installed with Helm hooks (e.g.,
post-install
,pre-delete
, etc.) have hardcoded resource requests and limits. For instance:gateway-cleanup-job
(pre-delete
hook): https://github.com/hashicorp/consul-k8s/blob/v1.6.0/charts/consul/templates/gateway-cleanup-job.yaml#L49-L55gossip-encryption-autogenerate-job
(pre-install
,pre-upgrade
hooks): https://github.com/hashicorp/consul-k8s/blob/v1.6.0/charts/consul/templates/gossip-encryption-autogenerate-job.yaml#L64-L70Other jobs have the ability to customize these requests and limits:
gateway-resources-job
(post-install
,post-upgrade
hooks): https://github.com/hashicorp/consul-k8s/blob/v1.6.0/charts/consul/templates/gateway-resources-job.yaml#L92-L94On some of my Kubernetes environments where I install this Consul Helm chart, I get OOMKilled events on the Jobs with hardcoded requests and limits, blocking operations like Helm deletes, Helm installs, and Helm upgrades.
I can workaround this issue by installing Kyverno on the cluster and using a
ClusterPolicy
to mutate the resource requests and limits for these Jobs upon admission to the cluster, but I should not have to depend on Kyverno mutating policies to configure Consul properly in my clusters.Feature Description
I would request you expose values in your Helm chart to allow me to customize the resource requests and limits for Jobs installed by the Chart.
Use Case(s)
All cases. This is fundamental to the management of the chart with Helm.
Contributions
I can contribute with a PR if desired. This is a small, low-risk change.
The text was updated successfully, but these errors were encountered: