Tune Connection Draining for Apiserver ELB on AWS
Environment
- Red Hat OpenShift Container Platform 4.x
Issue
- Is it possible to allow the "Connection Draining" setting on the apiserver ELB to be tuned via OpenShift cluster configuration?
- OpenShift is Dedicated as a build farm and makes heavy use of Binary sources in their builds. Without connection, and draining enabled, would be found that builds would fail to upload their source code on a regular basis.
Resolution
Currently, there is no supported way to enable ELB connection draining, ELB logging to S3, or changing the listeners on the ELB. Also, Connection draining is already implemented in the OpenShift router.
-
Question: Is it fine to change the below AWS's recommended settings?
- RedHat only supports what is in the product documentation. As this is a third-party load balancer, all the changes are subjected to support from AWS. Therefore, it is best to follow the recommended setting from them.
-
Question: What impact can be expected by changing to AWS recommended settings?
- RedHat only supports what is in the product documentation. As this is a third-party load balancer, these changes haven't test internally by RedHat.
-
Question: If Red Hat does not allow changes to the AWS recommended settings?
- RedHat only supports what is in the product documentation. As this is a third-party load balancer, We recommend a cloud team from the customer side, have to check internally
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Comments