Confluent Control Center Deployment Overview

You can deploy Control Center with Confluent Platform in more than one way, from a Docker quick start to a multi-node production install. Choose the path that fits your environment. For on-premises Confluent Platform installation, see Install Confluent Platform On-Premises.

For Control Center system requirements and compatibility with Confluent Platform, see System Requirements and Compatibility.

Warning

Do not install Control Center on the same node as Confluent Platform. Control Center is a control plane component. Running Control Center alongside Confluent Platform data plane services, such as Schema Registry or REST Proxy, can cause conflicts between Control Center and Confluent Platform packages.

Ensure that Confluent Platform packages (for example, Schema Registry, REST Proxy, or other Confluent share/java libraries) are not installed or present on the Control Center host. Duplicate Confluent packages on the same host can be picked up on the Control Center classpath and cause class-loading conflicts that prevent startup, even when Confluent Platform is not running. If Control Center previously shared a host with Confluent Platform, remove the other Confluent packages before starting Control Center.

For production deployments, install Control Center on a dedicated node. For more information, see Multi-Node Installation for Production.

Choose a deployment path

After you install