Problem description
Currently when applying a SIPCluster CR, the SIP controller uses hard-coded HAProxy configurations to build the load balancer infrastructure services for the API server and the workload services. There may be situations where a different configuration is desired for one or both of the load balancers such as timeout settings and health checks.
Proposed change
Provide a mechanism to customize the HAProxy configuration. This could be done by allowing the use of custom templates referenced in the SIPCluster CR for the HAProxy configurations or by allowing individual values within the default HAProxy configuration to be overridden from within the CR.
Adding the "design needed" label for a design discussion on an approach.
Problem description Currently when applying a SIPCluster CR, the SIP controller uses hard-coded HAProxy configurations to build the load balancer infrastructure services for the API server and the workload services. There may be situations where a different configuration is desired for one or both of the load balancers such as timeout settings and health checks.
Proposed change Provide a mechanism to customize the HAProxy configuration. This could be done by allowing the use of custom templates referenced in the SIPCluster CR for the HAProxy configurations or by allowing individual values within the default HAProxy configuration to be overridden from within the CR.
Adding the "design needed" label for a design discussion on an approach.