# Use Custom Docker Registry for Confluent Platform Using Confluent for Kubernetes
Confluent for Kubernetes (CFK) deploys publicly available Docker images hosted on Docker Hub
from the `confluentinc` repositories.
If you want CFK to deploy Confluent Platform images from a different registry, or from
your own set of repositories on Docker Hub, take the following steps.
## Step 1: Host the images in the custom registry
1. Get a list of the images and their tags to install.
The default CFK and Confluent Platform image URIs are:
```text
docker.io/confluentinc/confluent-init-container:
docker.io/confluentinc/confluent-operator:
docker.io/confluentinc/cp-enterprise-control-center-next-gen:
docker.io/confluentinc/cp-enterprise-control-center:
docker.io/confluentinc/cp-enterprise-replicator:
docker.io/confluentinc/cp-kafka-rest:
docker.io/confluentinc/cp-ksqldb-server:
docker.io/confluentinc/cp-schema-registry:
docker.io/confluentinc/cp-server:
docker.io/confluentinc/cp-server-connect:
docker.io/confluentinc/cp-zookeeper:
```
* The `` for a Confluent Platform component image is the release version of the
component. For example, the URI for the ZooKeeper version 8.3.0 image is
`docker.io/confluentinc/cp-zookeeper:8.3.0`.
* The `` for the Control Center image is the release version of Control Center.
* The `` for the init container is the version of CFK.
* The default `` for the `confluent-operator` image is
` 0.1718.10` for the current version. To select a different
version tag, refer to [Confluent for Kubernetes image tags](co-supported-environments.md#co-operator-image-tags).
#### IMPORTANT
Starting with Confluent Platform version 8.0, ZooKeeper is no longer part of Confluent Platform.
2. Pull the desired CFK and Confluent Platform images from the Confluent Docker repositories.
By default, the `docker pull` command pulls the image matching the system’s
architecture where the command is executed.
* To pull the CFK images from the workstation with the same architecture
of the CFK and Confluent Platform cluster you want to use:
```bash
docker pull confluentinc/:
```
For example:
```bash
docker pull confluentinc/confluent-operator: 0.1718.10
```
* To pull the CFK images from a workstation whose architecture is different
from the architecture of the Kubernetes cluster that you want to run CFK,
specify the CFK architecture with the `--platform` flag:
```bash
docker pull --platform :
```
For example, if you run `docker pull` on an ARM-based workstation, but want
to run CFK and Confluent Platform on a Kubernetes cluster running AMD64 worker nodes:
```bash
docker pull --platform linux/amd64 confluentinc/confluent-operator:
```
Alternatively, you can pull and push multi-architecture images
(`linux/amd64` and `linux/arm64`) of CFK and Confluent Platform components to your
private repository.
3. Push the CFK and Confluent Platform images to your target registry.
## Step 2: Create a pull secret for the custom registry
If you need to authenticate to image registries with the username and password,
for each of those registries, create a Kubernetes secret of the
`docker-registry` type in the same namespace as the Confluent Platform component.
An image pull secret contains the credentials to the registry the image is
pulled from.
`` denotes the namespace you deploy this Confluent Platform
component in.
```bash
kubectl create secret docker-registry \
--namespace \
--docker-server= \
--docker-username= \
--docker-password= \
--docker-email=
```
## Step 3: Configure Confluent Platform to be installed from the custom registry
Configure the following settings in the custom resource (CR) for each Confluent Platform
component:
```yaml
spec:
image: # Changes in this property will roll the cluster.
application: # Required. Specify
# //:
init: # Required. Specify
# //:
pullSecretRef: # The image pull secret added in the previous step.
```
For example, to pull the Schema Registry image from a custom registry using the
`registry-secret` created in the previous step:
```yaml
spec:
image:
application: docker.io/myrepository/cp-schema-registry:8.3.0
init: docker.io/myrepository/confluent-init-container:3.3.0
pullSecretRef:
- registry-secret
```