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

Haproxy maxconn customconfig setting is not working #3025

Open
krimeshshah opened this issue Nov 12, 2024 · 0 comments
Open

Haproxy maxconn customconfig setting is not working #3025

krimeshshah opened this issue Nov 12, 2024 · 0 comments
Labels
argo-cd bug Something isn't working

Comments

@krimeshshah
Copy link

krimeshshah commented Nov 12, 2024

Describe the bug

Hi Team,

I am trying to deploy argocd with redis-ha proxy. This chart argo-cd chart uses dependency subchart for redis-ha https://github.com/DandyDeveloper/charts/tree/master/charts/redis-ha. Now when i deploy the argocd helm chart on the kubernetes cluster with nodes containing latest linux image. ha-proxy pods goes into carshloopback off state due to OOM.
After investigating found solution of setting maxconn parameter value 4096 in haproxy.cfg file . I can see in subchart there is parameter called customConfig where we can define this maxconn parameter. But it is not working https://github.com/DandyDeveloper/charts/blob/redis-ha-4.27.6/charts/redis-ha/values.yaml#L203.
Can someone help me how to make it workin in argo-cd helm chart?

Ref

Regards,
krimesh

Related helm chart

argo-cd

Helm chart version

7.7.1

To Reproduce

  1. Deploy argo-cd helm chart with redis-ha and haproxy enabled on the kubernetes cluster with latest linux image. I am using gardenlinux[15192.1.0].
  2. After argo-cd helm chart deployment you will find the redis-ha-haproxy pods in crashloopbackoff state due to oom issue.
  3. There is already root cause and solution available to resolve this issue
  4. How do i set/configure maxconn 4096 in haproxy.cfg while argo-cd chart is using redis-ha dependency subchart.

I tried to configure under haproxy block in values.yaml as shown below but it doesnt work.

customConfig
   global
      maxConn 4096

Expected behavior

redis-ha-haproxy pod should be in running state.

Screenshots

No response

Additional context

No response

@krimeshshah krimeshshah added the bug Something isn't working label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
argo-cd bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants