Repository navigation
What things to do after setting up load balancer on top of management servers. #14400
Replies: 1 comment 1 reply
|
Dear @anirudh09041, I haven't used Oracle LB for ACS myself, but it is straightforward. Note: you do not need to use the LB for port 8250, since the hosts will receive a list of MGMT servers they can connect to. I would go this route because the LB may close idle TCP connections, forcing hosts to reconnect frequently (this may be adjustable in the settings, like stickiness or long timeouts). I'm not saying it is a bad idea, it just needs some testing and adjustments. For the UI/API, there is not much mystery: the LB can terminate TLS and manage the certificate, then relay HTTP traffic to port 8080 as you described. ACS does not really check which Host header is used or anything like that, so it behaves as a simple web app. Still, it is good to have the headers proxied to the targets so they get logged appropriately. And, of course, create a rule to redirect requests that arrive on port 80 to HTTPS on the same host and URI. Here is an equivalent setup for NGINX, if you want to take a peek: |


Dear @anirudh09041,
I haven't used Oracle LB for ACS myself, but it is straightforward.
Note: you do not need to use the LB for port 8250, since the hosts will receive a list of MGMT servers they can connect to. I would go this route because the LB may close idle TCP connections, forcing hosts to reconnect frequently (this may be adjustable in the settings, like stickiness or long timeouts). I'm not saying it is a bad idea, it just needs some testing and adjustments.
For the UI/API, there is not much mystery: the LB can terminate TLS and manage the certificate, then relay HTTP traffic to port 8080 as you described. ACS does not really check which Host header is used or anything like that,…