Managing load balancers
On This Page
CircleCI server uses a load balancer to manage network traffic entering and leaving the Kubernetes cluster.
The load balancer manages all traffic coming into the application. The load balancer is public by default, but can be made private.
Make the frontend load balancer private
Webhooks: If you choose to make the frontend load balancer private, the following conditions must be met, depending on your VCS, for webhooks to work:
|
| The Private load balancers option only works with installations on CircleCI server on GKE or EKS. |
In your values.yaml override file, set the following parameter to true. The parameter is false (public) by default.
nginx:
private_load_balancers: false| If you are changing this setting after the initial deployment of CircleCI server, you may need to delete the old public load balancer so that Kubernetes requests a new load balancer with the new configuration. |
Help make this document better
This guide, as well as the rest of our docs, are open source and available on GitHub. We welcome your contributions.
- Suggest an edit to this page (please read the contributing guide first).
- To report a problem in the documentation, or to submit feedback and comments, please open an issue on GitHub.
- CircleCI is always seeking ways to improve your experience with our platform. If you would like to share feedback, please join our research community.
Need support?
Our support engineers are available to help with service issues, billing, or account related questions, and can help troubleshoot build configurations. Contact our support engineers by opening a ticket.
You can also visit our support site to find support articles, community forums, and training resources.
CircleCI Documentation by CircleCI is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.