Project

General

Profile

Actions

Bug #63171

open

Customize haproxy config when using ingress

Added by Jie Wang 7 months ago. Updated 4 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
orchestrator
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

We tried to increasing the maxconn by modify the haproxy file inside the docker container and reloading haproxy.
I followed the documentation : https://tracker.ceph.com/issues/55544
set the haproxy config file:
ceph config-key set mgr/cephadm/services/ingress/haproxy.cfg -i <custom-haproxy-config>
ceph orch redeploy <ingress-service-name>
And I used the j2 template from the github:
https://github.com/ceph/ceph/blob/master/src/pybind/mgr/cephadm/templates/services/ingress/haproxy.cfg.j2
The only thing I edited was the maxconn, but after I redeployed the ingress. Nothing change, the haproxy.cfg was still generated by cephadm including the parameters.

Actions #1

Updated by Ilya Dryomov 4 months ago

  • Target version deleted (v17.2.7)
Actions

Also available in: Atom PDF