<a id="co-deploy-cp"></a>

<a id="co-deployment"></a>

# Deploy Confluent Platform using Confluent for Kubernetes

Using Confluent for Kubernetes (CFK), install Confluent Platform components in the following steps:

1. Review and complete the required configuration tasks for Confluent Platform components.

   There might be CFK-specific considerations for some components.

   For example, in CFK, ksqlDB can only be deployed in the interactive mode.
   CFK does not support the headless mode deployment of ksqlDB.

   For detailed configuration information, refer to specific configuration pages
   under [Configure Confluent Platform](co-configure-overview.md#co-config-overview).
2. [Specify the Confluent Platform images and the version to deploy](#co-deploy-cp-version).
3. [Deploy Confluent Platform](#co-deploy-cp-components).
4. [Specify the Confluent Control Center image and the version to deploy](#co-deploy-c3-version).
5. [Deploy Confluent Control Center](#co-deploy-c3).
6. [Validate deployment](#co-deploy-validate).

<a id="co-deploy-cp-version"></a>

## Specify the Confluent Platform images and the version to deploy

1. For the Confluent Platform components you want to deploy, specify the Docker image names
   and the version tags in the components custom resources (CRs).

   See [Confluent Docker Image Reference](https://docs.confluent.io/platform/current/installation/docker/image-reference.html#docker-image-reference)
   for the list of Confluent images.

   The tags are the version of Confluent Platform. For example, for Schema Registry version 8.3.0,
   set  `application: confluentinc/cp-schema-registry:8.3.0` in
   the Schema Registry CR.

   See [how to specify different Confluent Platform versions in the component custom resources](https://github.com/confluentinc/confluent-kubernetes-examples/tree/master/general/cp-version).
2. Specify the init container in `spec.image.init:`. The tag of the init container
   is the version of Confluent for Kubernetes (CFK).

   To deploy the 6.2.0 and later versions of Confluent Platform, you must use the
   `confluent-init-container` instead of the legacy
   `cp-init-container-operator`.

   An example Schema Registry CR to deploy Schema Registry 8.3.0 with CFK 3.3.0:
   ```yaml
   kind: SchemaRegistry
   metadata:
     name: schemaregistry
     namespace: confluent
   spec:
     replicas: 1
     image:
       application: confluentinc/cp-schema-registry:8.3.0
       init: confluentinc/confluent-init-container:3.3.0
   ```
3. Specify the number of replicas for Confluent Platform components in the component CRs using
   the `spec.replicas` property.

   In the Schema Registry CR example in the previous step, one Schema Registry
   replica is to be deployed.

   Note that you can deploy only one replica of Control Center in CFK.
4. If you are using CFK 3.x to deploy Confluent Platform 7.x, you need to set the following
   annotation in the component CR to use Log4j. CFK 3.x uses Log4j 2 by
   default. When the annotation is set to `true`, CFK will deploy the Confluent Platform
   component with Log4j.
   ```yaml
   kind: <Component>
   metadata:
     annotations:
       platform.confluent.io/use-log4j1: true
   ```

<a id="co-deploy-cp-components"></a>

## Deploy Confluent Platform

1. Apply the Confluent Platform CR configurations. You can apply one configuration file for
   all Confluent Platform components, or apply multiple configuration files for individual
   Confluent Platform component.
   ```bash
   kubectl apply -f <CR>
   ```
2. Check that all Confluent Platform resources are successfully deployed:
   ```bash
   kubectl get pods
   ```

<a id="co-deploy-c3-version"></a>

## Specify the Confluent Control Center image and the version to deploy

You can deploy only one replica of Control Center (`spec.replica: 1`) in CFK.

1. To deploy Control Center, specify the Docker image name and the version tags in the
   Control Center CR in `spec.image.application`. The tag is the version of Control Center.

   For example:
   ```yaml
   kind: ControlCenter
   spec:
     image:
       application: confluentinc/cp-enterprise-control-center-next-gen:latest
       init: confluentinc/confluent-init-container:3.3.0
   ```
2. Specify the init container in `spec.image.init:`. The tag of the init container
   is the version of CFK.

   The init container tag should be at least `2.11.1` to deploy Control Center.

   `<c3-tag>` is the Control Center release you are installing.

   An example Control Center CR:
   ```yaml
   kind: ControlCenter
   metadata:
     name: control-center-next-gen
     namespace: confluent
   spec:
     replicas: 1
     image:
       application: confluentinc/cp-enterprise-control-center-next-gen:<c3-tag>
       init: confluentinc/confluent-init-container:<c3-tag>
   ```
3. Specify the Prometheus and Alertmanager images and tags:
   ```yaml
   kind: ControlCenter
   metadata:
     name: control-center-next-gen
     namespace: confluent
   spec:
     replicas: 1
     image:
       application: confluentinc/cp-enterprise-control-center-next-gen:<c3-tag>
       init: confluentinc/confluent-init-container:3.3.0
     services:
       prometheus:
         image: confluentinc/cp-enterprise-prometheus:<c3-tag>
         pvc:
           dataVolumeCapacity: 10Gi
       alertmanager:
         image: confluentinc/cp-enterprise-alertmanager:<c3-tag>
   ```

<a id="co-deploy-c3"></a>

## Deploy Confluent Control Center

1. After you [configure Control Center](co-monitor-cp.md#co-c3) and
   [specify the image name and tag](#co-deploy-c3-version),
   apply the ControlCenter CR:
   ```bash
   kubectl apply -f <CR>
   ```
2. Check that the Control Center pod is successfully deployed. For example:
   ```bash
   kubectl get pod controlcenter-next-gen-0 -n confluent \
     -o jsonpath="{range .status.containerStatuses[*]}{.name}:{.state.*.reason}{'\n'}{end}"
   ```
3. Use local port forwarding to load Control Center at localhost:9021:
   ```bash
   kubectl port-forward pod/{pod-name} 9021:9021 -n <namespace>
   ```

<a id="co-deploy-validate"></a>

## Validate deployment

After you set up your Confluent Platform environment, validate the deployment, starting with the following list:

1. Pods are running and healthy
2. Services are deployed
3. Control Center is accessible and monitors Kafka and other components
4. Client can create topics

Refer to the [Confluent for Kubernetes example Git Hub repo](https://github.com/confluentinc/confluent-kubernetes-examples/tree/master/quickstart-deploy#validate)
for sample steps to validate a basic deployment. You can also review the other
scenarios for validating various deployment configurations, such as with various
external access methods and security setups.