CircleCI server v4.3 overview
Introduction
CircleCI server is an on-premises CI/CD platform for enterprise customers who have compliance or security needs that require them to operate within their firewall, in a private cloud, or in a data center.
CircleCI server provides the same features as CircleCI’s cloud offering, but operates within your Kubernetes cluster.
| For installation instructions, you have the option of either the regular or air-gapped installation guide. |
The CircleCI server application exposes four services, using a single load balancer. If required, the load balancer can be made private, separating it from the public internet.
| Service | Ports | Description |
|---|---|---|
Frontend GUI Proxy & API | 80 and 443 | Exposes the web application. |
Nomad Control Plane | 4647 | Exposes an RPC protocol for Nomad clients. |
The application exposes a number of external ports. These ports are used for various functions as defined in the table below.
| Port number | Protocol | Direction | Source / Destination | Use | Notes |
|---|---|---|---|---|---|
| TCP | Inbound | End users | HTTP web app traffic | |
| TCP | Inbound | End users | HTTP web app traffic | |
| TCP | Inbound | Administrators | SSH | Only required for the bastion host. |
| TCP | Inbound | SSH into builds | Only required for the Nomad clients. |
CircleCI server schedules CI jobs using the Nomad scheduler. The Nomad control plane runs inside of Kubernetes, while the Nomad clients, which are responsible for running scheduled CircleCI jobs, are provisioned outside the cluster. CircleCI server can run Docker jobs on the Nomad clients themselves or in a dedicated virtual machine (VM).
Job artifacts and outputs are sent directly from jobs in Nomad to object storage (S3, Google Cloud Storage, or other supported options). Audit logs and other items from the application are also stored in object storage, so both the Kubernetes cluster and the Nomad clients need access to object storage.
Services
CircleCI server v4.3 consists of the following services. Find their descriptions and failure implications below:
| Service | Component | Description | What happens if it fails? | Notes |
|---|---|---|---|---|
| App Core | Provides a GraphQL API that provides data to render the web frontend. | Many parts of the UI (such as Contexts) will fail completely. | |
| App Core | Persists audit log events to blob storage for long-term storage. | Some events may not be recorded. | |
| App Core | A service responsible for listening to the event stream. Detects branch deletions, job updates, pushes, workflow updates. | ||
| App Core | Ingests from www-api and sends to plans-service, workflows-conductor, and to orbs-service. | ||
| Execution | Primary datastore | ||
| Data storage for microservices. | |||
| Pipelines and Execution | Queuing for workflow messaging, test results, usage, crons, output, notifications, and scheduler. | ||
| Execution | Caches data that will not be stored permanently (such as build logs), for request caching, and for rate limit calculations. | A failed cache can result in rate limiting from the VCS if too many calls are made to it. | |
| Telegraf collects statsd metrics. All white-boxed metrics in our services publish statsd metrics that are sent to Telegraf, but can also be configured to be exported to other places (such as Datadog or Prometheus). | |||
| HashiCorp Vault to run encryption and decryption as a service for secrets. | |||
| App Core | Stores and provides encrypted contexts. | All builds using Contexts will fail. | |
| Pipelines | Triggers scheduled workflows. | Scheduled workflows will not run. | |
| App Core | Responsible for accepting build requests and distributing the job to appropriate queues. | ||
| App Core | Stores and provides information about our domain model. Works with permissions and API. | Workflows will fail to start and some REST API calls may fail, causing 500 errors in the CircleCI UI. If LDAP authentication is in use, all logins will fail. | |
| Frontend | CircleCI web app and www-api proxy. | The UI and REST API will be unavailable and no jobs will be triggered by GitHub/Enterprise. Running builds will be OK, but no updates will be seen. | Rate limit of 150 requests per second with a single user instantaneous limit of 300 requests. |
| Metrics | A service to aggregate build and usage metrics for exporting and analysis. | ||
| App Core | API management. | ||
| App Core | Handles notifications to external services (for example, Slack or email). | ||
| App Core / Frontend | Handles traffic redirection and ingress. | ||
| Nomad | Manages scaling of Nomad clusters in AWS and GCP environments. | ||
| Nomad | Responsible for managing Nomad clients. | ||
| Pipelines | Handles communication between orb registry and config. | ||
output | Execution | Receives job output and status updates and writes them to S3. Also provides an API to running jobs to access caches, workspaces, store caches, workspaces, artifacts, and test results. | ||
| App Core | Provides the CircleCI permissions interface. | Workflows will fail to start and some REST API calls may fail, causing 500 errors in the UI. | |
| Frontend | Websockets server. | ||
| Frontend | Provides UI output in the job view | ||
| Metrics | Collection of metrics. | ||
| Runner Admin | Manages Runner resource classes and tokens, & coordinates runner task handling | ||
| Docker Compute Management | Responsible for scheduling jobs on Nomad cluster(s). | ||
| Machine Compute Management | Periodically requests machines from compute provider to run jobs for both | Periodically checks for stale machine and remote Docker instances and requests that provider removes them. | |
| Execution | Boundary for execution to provide API to rest of CircleCI | ||
| Frontend | Micro Front End (MFE) services used to render the frontend web application GUI. | The respective services page will fail to load. Example: A | The MFEs are used to render the web application located at |
| App Core | Service responsible for all webhooks, including management of state and handling events. | ||
| Pipelines | Takes in information from VCS to kick off pipelines. | New Pipelines will not be kicked off when there are changes in the VCS. | |
| Pipelines | Helps translate the information through gRPC. |
Platforms
CircleCI server is designed to deploy within a Kubernetes cluster. The machine service (machine provisioner) is able to leverage unique EKS or GKE offerings to dynamically create VM images.
If installing outside of EKS or GKE, additional work is required to access some of the same machine build features. Setting up CircleCI runner gives you access to the same feature set as machine provisioner across a much wider range of operating systems and machine types (for example, macOS).
We do our best to support a wide range of platforms for installation. We use environment-agnostic solutions wherever possible. However, we do not test all platforms and options. For that reason, we provide a list of tested environments, which we will continue to expand.
| Environment | Status | Notes |
|---|---|---|
EKS | Tested | |
GKE | Tested | |
Local installation | Tested | See Air-gapped installation docs |
Azure | Untested | Should work with MinIO and Runner. |
Digital Ocean | Untested | Should work with MinIO and Runner. |
OpenShift | Untested | Known not to work. |
Rancher | Untested | Should work with MinIO and Runner. |