2.8.1-debian-10-r57 release
This commit is contained in:
Bitnami Bot
parent
ff01bea510
commit
3f2396ac7e
|
|
@ -24,7 +24,7 @@ COPY rootfs /
|
|||
RUN /opt/bitnami/scripts/java/postunpack.sh
|
||||
RUN /opt/bitnami/scripts/kafka/postunpack.sh
|
||||
ENV BITNAMI_APP_NAME="kafka" \
|
||||
BITNAMI_IMAGE_VERSION="2.8.1-debian-10-r56" \
|
||||
BITNAMI_IMAGE_VERSION="2.8.1-debian-10-r57" \
|
||||
JAVA_HOME="/opt/bitnami/java" \
|
||||
PATH="/opt/bitnami/java/bin:/opt/bitnami/common/bin:/opt/bitnami/kafka/bin:$PATH"
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
# Kafka packaged by Bitnami
|
||||
# Apache Kafka packaged by Bitnami
|
||||
|
||||
## What is Kafka?
|
||||
## What is Apache Kafka?
|
||||
|
||||
> Kafka is a distributed streaming platform designed to build real-time pipelines and can be used as a message broker or as a replacement for a log aggregation solution for big data applications.
|
||||
> Apache Kafka is a distributed streaming platform designed to build real-time pipelines and can be used as a message broker or as a replacement for a log aggregation solution for big data applications.
|
||||
|
||||
[Overview of Kafka](http://kafka.apache.org/)
|
||||
[Overview of Apache Kafka](http://kafka.apache.org/)
|
||||
|
||||
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
|
||||
|
||||
|
|
@ -30,9 +30,9 @@ $ docker-compose up -d
|
|||
|
||||
> This [CVE scan report](https://quay.io/repository/bitnami/kafka?tab=tags) contains a security report with all open CVEs. To get the list of actionable security issues, find the "latest" tag, click the vulnerability report link under the corresponding "Security scan" field and then select the "Only show fixable" filter on the next page.
|
||||
|
||||
## How to deploy Apache Kafka in Kubernetes?
|
||||
## How to deploy Apache Apache Kafka in Kubernetes?
|
||||
|
||||
Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the [Bitnami Apache Kafka Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/kafka).
|
||||
Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the [Bitnami Apache Apache Kafka Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/kafka).
|
||||
|
||||
Bitnami containers can be used with [Kubeapps](https://kubeapps.com/) for deployment and management of Helm Charts in clusters.
|
||||
|
||||
|
|
@ -44,13 +44,13 @@ Non-root container images add an extra layer of security and are generally recom
|
|||
|
||||
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/tutorials/understand-rolling-tags-containers/).
|
||||
* [`3`, `3-debian-10`, `3.0.0`, `3.0.0-debian-10-r39`, `latest` (3/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-kafka/blob/3.0.0-debian-10-r39/3/debian-10/Dockerfile)
|
||||
* [`2`, `2-debian-10`, `2.8.1`, `2.8.1-debian-10-r56` (2/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-kafka/blob/2.8.1-debian-10-r56/2/debian-10/Dockerfile)
|
||||
* [`2`, `2-debian-10`, `2.8.1`, `2.8.1-debian-10-r57` (2/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-kafka/blob/2.8.1-debian-10-r57/2/debian-10/Dockerfile)
|
||||
|
||||
Subscribe to project updates by watching the [bitnami/kafka GitHub repo](https://github.com/bitnami/bitnami-docker-kafka).
|
||||
|
||||
## Get this image
|
||||
|
||||
The recommended way to get the Bitnami Kafka Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/kafka).
|
||||
The recommended way to get the Bitnami Apache Kafka Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/kafka).
|
||||
|
||||
```console
|
||||
$ docker pull bitnami/kafka:latest
|
||||
|
|
@ -76,7 +76,7 @@ If you remove the container all your data and configurations will be lost, and t
|
|||
|
||||
> Note: If you have already started using your database, follow the steps on [backing up](#backing-up-your-container) and [restoring](#restoring-a-backup) to pull the data from your running container down to your host.
|
||||
|
||||
The image exposes a volume at `/bitnami/kafka` for the Kafka data. For persistence you can mount a directory at this location from your host. If the mounted directory is empty, it will be initialized on the first run.
|
||||
The image exposes a volume at `/bitnami/kafka` for the Apache Kafka data. For persistence you can mount a directory at this location from your host. If the mounted directory is empty, it will be initialized on the first run.
|
||||
|
||||
Using Docker Compose:
|
||||
|
||||
|
|
@ -94,13 +94,13 @@ kafka:
|
|||
|
||||
## Connecting to other containers
|
||||
|
||||
Using [Docker container networking](https://docs.docker.com/engine/userguide/networking/), a Kafka server running inside a container can easily be accessed by your application containers.
|
||||
Using [Docker container networking](https://docs.docker.com/engine/userguide/networking/), a Apache Kafka server running inside a container can easily be accessed by your application containers.
|
||||
|
||||
Containers attached to the same network can communicate with each other using the container name as the hostname.
|
||||
|
||||
### Using the Command Line
|
||||
|
||||
In this example, we will create a Kafka client instance that will connect to the server instance that is running on the same docker network as the client.
|
||||
In this example, we will create a Apache Kafka client instance that will connect to the server instance that is running on the same docker network as the client.
|
||||
|
||||
#### Step 1: Create a network
|
||||
|
||||
|
|
@ -119,9 +119,9 @@ $ docker run -d --name zookeeper-server \
|
|||
bitnami/zookeeper:latest
|
||||
```
|
||||
|
||||
#### Step 2: Launch the Kafka server instance
|
||||
#### Step 2: Launch the Apache Kafka server instance
|
||||
|
||||
Use the `--network app-tier` argument to the `docker run` command to attach the Kafka container to the `app-tier` network.
|
||||
Use the `--network app-tier` argument to the `docker run` command to attach the Apache Kafka container to the `app-tier` network.
|
||||
|
||||
```console
|
||||
$ docker run -d --name kafka-server \
|
||||
|
|
@ -131,9 +131,9 @@ $ docker run -d --name kafka-server \
|
|||
bitnami/kafka:latest
|
||||
```
|
||||
|
||||
#### Step 3: Launch your Kafka client instance
|
||||
#### Step 3: Launch your Apache Kafka client instance
|
||||
|
||||
Finally we create a new container instance to launch the Kafka client and connect to the server created in the previous step:
|
||||
Finally we create a new container instance to launch the Apache Kafka client and connect to the server created in the previous step:
|
||||
|
||||
```console
|
||||
$ docker run -it --rm \
|
||||
|
|
@ -144,7 +144,7 @@ $ docker run -it --rm \
|
|||
|
||||
### Using Docker Compose
|
||||
|
||||
When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new `bridge` network named `app-tier`. In this example we assume that you want to connect to the Kafka server from your own custom application image which is identified in the following snippet by the service name `myapp`.
|
||||
When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new `bridge` network named `app-tier`. In this example we assume that you want to connect to the Apache Kafka server from your own custom application image which is identified in the following snippet by the service name `myapp`.
|
||||
|
||||
```yaml
|
||||
version: '2'
|
||||
|
|
@ -171,8 +171,8 @@ services:
|
|||
> **IMPORTANT**:
|
||||
>
|
||||
> 1. Please update the `YOUR_APPLICATION_IMAGE` placeholder in the above snippet with your application image
|
||||
> 2. Configure Kafka and ZooKeeper persistence, and configure them either via environment variables or by [mounting configuration files](#full-configuration).
|
||||
> 3. In your application container, use the hostname `kafka` to connect to the Kafka server
|
||||
> 2. Configure Apache Kafka and ZooKeeper persistence, and configure them either via environment variables or by [mounting configuration files](#full-configuration).
|
||||
> 3. In your application container, use the hostname `kafka` to connect to the Apache Kafka server
|
||||
|
||||
Launch the containers using:
|
||||
|
||||
|
|
@ -182,18 +182,18 @@ $ docker-compose up -d
|
|||
|
||||
## Configuration
|
||||
|
||||
The configuration can easily be setup with the Bitnami Kafka Docker image using the following environment variables:
|
||||
The configuration can easily be setup with the Bitnami Apache Kafka Docker image using the following environment variables:
|
||||
|
||||
* `ALLOW_PLAINTEXT_LISTENER`: Allow to use the PLAINTEXT listener. Default: **no**.
|
||||
* `KAFKA_INTER_BROKER_USER`: Kafka inter broker communication user. Default: admin. Default: **user**.
|
||||
* `KAFKA_INTER_BROKER_PASSWORD`: Kafka inter broker communication password. Default: **bitnami**.
|
||||
* `KAFKA_INTER_BROKER_USER`: Apache Kafka inter broker communication user. Default: admin. Default: **user**.
|
||||
* `KAFKA_INTER_BROKER_PASSWORD`: Apache Kafka inter broker communication password. Default: **bitnami**.
|
||||
* `KAFKA_CERTIFICATE_PASSWORD`: Password for certificates. No defaults.
|
||||
* `KAFKA_HEAP_OPTS`: Kafka's Java Heap size. Default: **-Xmx1024m -Xms1024m**.
|
||||
* `KAFKA_HEAP_OPTS`: Apache Kafka's Java Heap size. Default: **-Xmx1024m -Xms1024m**.
|
||||
* `KAFKA_ZOOKEEPER_PROTOCOL`: Authentication protocol for Zookeeper connections. Allowed protocols: **PLAINTEXT**, **SASL**, **SSL**, and **SASL_SSL**. Defaults: **PLAINTEXT**.
|
||||
* `KAFKA_ZOOKEEPER_USER`: Kafka Zookeeper user for SASL authentication. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_PASSWORD`: Kafka Zookeeper user password for SASL authentication. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_TLS_KEYSTORE_PASSWORD`: Kafka Zookeeper keystore file password and key password. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_TLS_TRUSTSTORE_PASSWORD`: Kafka Zookeeper truststore file password. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_USER`: Apache Kafka Zookeeper user for SASL authentication. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_PASSWORD`: Apache Kafka Zookeeper user password for SASL authentication. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_TLS_KEYSTORE_PASSWORD`: Apache Kafka Zookeeper keystore file password and key password. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_TLS_TRUSTSTORE_PASSWORD`: Apache Kafka Zookeeper truststore file password. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_TLS_VERIFY_HOSTNAME`: Verify Zookeeper hostname on TLS certificates. Defaults: **true**.
|
||||
* `KAFKA_ZOOKEEPER_TLS_TYPE`: Choose the TLS certificate format to use. Allowed values: `JKS`, `PEM`. Defaults: **JKS**.
|
||||
* `KAFKA_CFG_SASL_ENABLED_MECHANISMS`: Allowed mechanism when using SASL either for clients, inter broker, or zookeeper comunications. Allowed values: `PLAIN`, `SCRAM-SHA-256`, `SCRAM-SHA-512` or a comma separated combination of those values. Default: **PLAIN,SCRAM-SHA-256,SCRAM-SHA-512**
|
||||
|
|
@ -205,7 +205,7 @@ The configuration can easily be setup with the Bitnami Kafka Docker image using
|
|||
* `KAFKA_CFG_MAX_PARTITION_FETCH_BYTES`: The maximum amount of data per-partition the server will return. Default: 1048576
|
||||
* `KAFKA_CFG_MAX_REQUEST_SIZE`: The maximum size of a request in bytes. Default: 1048576
|
||||
|
||||
Additionally, any environment variable beginning with `KAFKA_CFG_` will be mapped to its corresponding Kafka key. For example, use `KAFKA_CFG_BACKGROUND_THREADS` in order to set `background.threads` or `KAFKA_CFG_AUTO_CREATE_TOPICS_ENABLE` in order to configure `auto.create.topics.enable`.
|
||||
Additionally, any environment variable beginning with `KAFKA_CFG_` will be mapped to its corresponding Apache Kafka key. For example, use `KAFKA_CFG_BACKGROUND_THREADS` in order to set `background.threads` or `KAFKA_CFG_AUTO_CREATE_TOPICS_ENABLE` in order to configure `auto.create.topics.enable`.
|
||||
|
||||
```console
|
||||
$ docker run --name kafka -e KAFKA_CFG_ZOOKEEPER_CONNECT=zookeeper:2181 -e ALLOW_PLAINTEXT_LISTENER=yes -e KAFKA_CFG_AUTO_CREATE_TOPICS_ENABLE=true bitnami/kafka:latest
|
||||
|
|
@ -221,9 +221,9 @@ kafka:
|
|||
...
|
||||
```
|
||||
|
||||
### Kafka development setup example
|
||||
### Apache Kafka development setup example
|
||||
|
||||
To use Kafka in a development setup, create the following `docker-compose.yml` file:
|
||||
To use Apache Kafka in a development setup, create the following `docker-compose.yml` file:
|
||||
|
||||
```yaml
|
||||
version: "3"
|
||||
|
|
@ -254,9 +254,9 @@ To deploy it, run the following command in the directory where the `docker-compo
|
|||
docker-compose up -d
|
||||
```
|
||||
|
||||
### Accessing Kafka with internal and external clients
|
||||
### Accessing Apache Kafka with internal and external clients
|
||||
|
||||
In order to use internal and external clients to access Kafka brokers you need to configure one listener for each kind of clients.
|
||||
In order to use internal and external clients to access Apache Kafka brokers you need to configure one listener for each kind of clients.
|
||||
|
||||
To do so, add the following environment variables to your docker-compose:
|
||||
|
||||
|
|
@ -282,7 +282,7 @@ And expose the external port:
|
|||
|
||||
#### Producer and consumer using external client
|
||||
|
||||
These clients, from the host, will use `localhost` to connect to Kafka.
|
||||
These clients, from the host, will use `localhost` to connect to Apache Kafka.
|
||||
|
||||
```console
|
||||
kafka-console-producer.sh --broker-list 127.0.0.1:9093 --topic test
|
||||
|
|
@ -291,7 +291,7 @@ kafka-console-consumer.sh --bootstrap-server 127.0.0.1:9093 --topic test --from-
|
|||
|
||||
#### Producer and consumer using internal client
|
||||
|
||||
These clients, from other containers on the same Docker network, will use the kafka container service hostname to connect to Kafka.
|
||||
These clients, from other containers on the same Docker network, will use the kafka container service hostname to connect to Apache Kafka.
|
||||
|
||||
```console
|
||||
kafka-console-producer.sh --broker-list kafka:9092 --topic test
|
||||
|
|
@ -300,22 +300,22 @@ kafka-console-consumer.sh --bootstrap-server kafka:9092 --topic test --from-begi
|
|||
|
||||
Similarly, application code will need to use `bootstrap.servers=kafka:9092`
|
||||
|
||||
More info about Kafka listeners can be found in [this great article](https://rmoff.net/2018/08/02/kafka-listeners-explained/)
|
||||
More info about Apache Kafka listeners can be found in [this great article](https://rmoff.net/2018/08/02/kafka-listeners-explained/)
|
||||
|
||||
### Security
|
||||
|
||||
The Bitnami Kafka docker image disables the PLAINTEXT listener for security reasons. You can enable the PLAINTEXT listener by adding the next environment variable, but remember that this configuration is not recommended for production.
|
||||
The Bitnami Apache Kafka docker image disables the PLAINTEXT listener for security reasons. You can enable the PLAINTEXT listener by adding the next environment variable, but remember that this configuration is not recommended for production.
|
||||
|
||||
```console
|
||||
ALLOW_PLAINTEXT_LISTENER=yes
|
||||
```
|
||||
|
||||
In order to configure authentication, you must configure the Kafka listeners properly. This container assumes the names below will be used for the listeners:
|
||||
In order to configure authentication, you must configure the Apache Kafka listeners properly. This container assumes the names below will be used for the listeners:
|
||||
|
||||
* INTERNAL: used for inter-broker communications.
|
||||
* CLIENT: used for coummunications with clients that are within the same network as Kafka brokers.
|
||||
* CLIENT: used for coummunications with clients that are within the same network as Apache Kafka brokers.
|
||||
|
||||
Let's see an example to configure Kafka with `SASL_SSL` authentication for communications with clients, and `SSL` authentication for inter-broker communication.
|
||||
Let's see an example to configure Apache Kafka with `SASL_SSL` authentication for communications with clients, and `SSL` authentication for inter-broker communication.
|
||||
|
||||
The environment variables below should be define to configure the listeners, and the SASL credentials for client communications:
|
||||
|
||||
|
|
@ -340,11 +340,11 @@ The following script can help you with the creation of the JKS and certificates:
|
|||
Keep in mind the following notes:
|
||||
|
||||
* When prompted to enter a password, use the same one for all.
|
||||
* Set the Common Name or FQDN values to your Kafka container hostname, e.g. `kafka.example.com`. After entering this value, when prompted "What is your first and last name?", enter this value as well.
|
||||
* Set the Common Name or FQDN values to your Apache Kafka container hostname, e.g. `kafka.example.com`. After entering this value, when prompted "What is your first and last name?", enter this value as well.
|
||||
* As an alternative, you can disable host name verification setting the environment variable `KAFKA_CFG_SSL_ENDPOINT_IDENTIFICATION_ALGORITHM` to an empty string.
|
||||
* When setting up a Kafka Cluster (check [this section](#setting-up-a-kafka-cluster) for more information), each Kafka broker and logical client needs its own keystore. You will have to repeat the process for each of the brokers in the cluster.
|
||||
* When setting up a Apache Kafka Cluster (check [this section](#setting-up-a-kafka-cluster) for more information), each Apache Kafka broker and logical client needs its own keystore. You will have to repeat the process for each of the brokers in the cluster.
|
||||
|
||||
The following docker-compose file is an example showing how to mount your JKS certificates protected by the password `certificatePassword123`. Additionally it is specifying the Kafka container hostname and the credentials for the client and zookeeper users.
|
||||
The following docker-compose file is an example showing how to mount your JKS certificates protected by the password `certificatePassword123`. Additionally it is specifying the Apache Kafka container hostname and the credentials for the client and zookeeper users.
|
||||
|
||||
```yaml
|
||||
version: '2'
|
||||
|
|
@ -382,7 +382,7 @@ services:
|
|||
- './kafka.truststore.jks:/opt/bitnami/kafka/config/certs/kafka.truststore.jks:ro'
|
||||
```
|
||||
|
||||
In order to get the required credentials to consume and produce messages you need to provide the credentials in the client. If your Kafka client allows it, use the credentials you've provided.
|
||||
In order to get the required credentials to consume and produce messages you need to provide the credentials in the client. If your Apache Kafka client allows it, use the credentials you've provided.
|
||||
|
||||
While producing and consuming messages using the `bitnami/kafka` image, you'll need to point to the `consumer.properties` and/or `producer.properties` file, which contains the needed configuration
|
||||
to work. You can find this files in the `/opt/bitnami/kafka/conf` directory.
|
||||
|
|
@ -401,23 +401,23 @@ export KAFKA_OPTS="-Djava.security.auth.login.config=/opt/bitnami/kafka/conf/kaf
|
|||
kafka-console-consumer.sh --bootstrap-server 127.0.0.1:9092 --topic test --consumer.config /opt/bitnami/kafka/conf/consumer.properties
|
||||
```
|
||||
|
||||
If you use other tools to use your Kafka cluster, you'll need to provide the required information. You can find the required information in the files located at `/opt/bitnami/kafka/conf` directory.
|
||||
If you use other tools to use your Apache Kafka cluster, you'll need to provide the required information. You can find the required information in the files located at `/opt/bitnami/kafka/conf` directory.
|
||||
|
||||
#### InterBroker communications
|
||||
|
||||
When configuring your broker to use `SASL` or `SASL_SSL` for inter-broker communications, you can provide the SASL credentials using these environment variables:
|
||||
|
||||
* `KAFKA_INTER_BROKER_USER`: Kafka inter broker communication user. Deprecated in favor of `KAFKA_CLIENT_USERS`.
|
||||
* `KAFKA_INTER_BROKER_PASSWORD`: Kafka inter broker communication password. Deprecated in favor of `KAFKA_CLIENT_PASSWORDS`.
|
||||
* `KAFKA_INTER_BROKER_USER`: Apache Kafka inter broker communication user. Deprecated in favor of `KAFKA_CLIENT_USERS`.
|
||||
* `KAFKA_INTER_BROKER_PASSWORD`: Apache Kafka inter broker communication password. Deprecated in favor of `KAFKA_CLIENT_PASSWORDS`.
|
||||
|
||||
#### Kafka client configuration
|
||||
#### Apache Kafka client configuration
|
||||
|
||||
When configuring Kafka with `SASL` or `SASL_SSL` for communications with clients, you can provide your the SASL credentials using this environment variables:
|
||||
When configuring Apache Kafka with `SASL` or `SASL_SSL` for communications with clients, you can provide your the SASL credentials using this environment variables:
|
||||
|
||||
* `KAFKA_CLIENT_USER`: Kafka client user. Default: **user**
|
||||
* `KAFKA_CLIENT_PASSWORD`: Kafka client user password. Default: **bitnami**
|
||||
* `KAFKA_CLIENT_USER`: Apache Kafka client user. Default: **user**
|
||||
* `KAFKA_CLIENT_PASSWORD`: Apache Kafka client user password. Default: **bitnami**
|
||||
|
||||
#### Kafka ZooKeeper client configuration
|
||||
#### Apache Kafka ZooKeeper client configuration
|
||||
|
||||
There are different options of configuration to connect a Zookeeper server.
|
||||
|
||||
|
|
@ -425,36 +425,36 @@ In order to connect a Zookeeper server without authentication, you should provid
|
|||
|
||||
* `KAFKA_ZOOKEEPER_PROTOCOL`: **PLAINTEXT**.
|
||||
|
||||
In order to authenticate Kafka against a Zookeeper server with `SASL`, you should provide the environment variables below:
|
||||
In order to authenticate Apache Kafka against a Zookeeper server with `SASL`, you should provide the environment variables below:
|
||||
|
||||
* `KAFKA_ZOOKEEPER_PROTOCOL`: **SASL**.
|
||||
* `KAFKA_ZOOKEEPER_USER`: Kafka Zookeeper user for SASL authentication. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_PASSWORD`: Kafka Zookeeper user password for SASL authentication. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_USER`: Apache Kafka Zookeeper user for SASL authentication. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_PASSWORD`: Apache Kafka Zookeeper user password for SASL authentication. No defaults.
|
||||
|
||||
In order to authenticate Kafka against a Zookeeper server with `SSL`, you should provide the environment variables below:
|
||||
In order to authenticate Apache Kafka against a Zookeeper server with `SSL`, you should provide the environment variables below:
|
||||
|
||||
* `KAFKA_ZOOKEEPER_PROTOCOL`: **SSL**.
|
||||
* `KAFKA_ZOOKEEPER_TLS_KEYSTORE_PASSWORD`: Kafka Zookeeper keystore file password and key password. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_TLS_TRUSTSTORE_PASSWORD`: Kafka Zookeeper truststore file password. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_TLS_KEYSTORE_PASSWORD`: Apache Kafka Zookeeper keystore file password and key password. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_TLS_TRUSTSTORE_PASSWORD`: Apache Kafka Zookeeper truststore file password. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_TLS_VERIFY_HOSTNAME`: Verify Zookeeper hostname on TLS certificates. Defaults: **true**.
|
||||
* `KAFKA_ZOOKEEPER_TLS_TYPE`: Choose the TLS certificate format to use. Allowed values: `JKS`, `PEM`. Defaults: **JKS**.
|
||||
|
||||
In order to authenticate Kafka against a Zookeeper server with `SASL_SSL`, you should provide the environment variables below:
|
||||
In order to authenticate Apache Kafka against a Zookeeper server with `SASL_SSL`, you should provide the environment variables below:
|
||||
|
||||
* `KAFKA_ZOOKEEPER_PROTOCOL`: **SASL_SSL**.
|
||||
* `KAFKA_ZOOKEEPER_USER`: Kafka Zookeeper user for SASL authentication. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_PASSWORD`: Kafka Zookeeper user password for SASL authentication. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_TLS_TRUSTSTORE_FILE`: Kafka Zookeeper truststore file location. Set it if the mount location is different from `/bitnami/kafka/conf/certs/zookeeper.truststore.pem`, `/bitnami/kafka/conf/certs/zookeeper.truststore.jks`, `/opt/bitnami/kafka/config/certs/zookeeper.truststore.jks` or `/opt/bitnami/kafka/conf/certs/zookeeper.truststore.pem` No defaults.
|
||||
* `KAFKA_ZOOKEEPER_TLS_KEYSTORE_PASSWORD`: Kafka Zookeeper keystore file password and key password. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_TLS_TRUSTSTORE_PASSWORD`: Kafka Zookeeper truststore file password. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_USER`: Apache Kafka Zookeeper user for SASL authentication. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_PASSWORD`: Apache Kafka Zookeeper user password for SASL authentication. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_TLS_TRUSTSTORE_FILE`: Apache Kafka Zookeeper truststore file location. Set it if the mount location is different from `/bitnami/kafka/conf/certs/zookeeper.truststore.pem`, `/bitnami/kafka/conf/certs/zookeeper.truststore.jks`, `/opt/bitnami/kafka/config/certs/zookeeper.truststore.jks` or `/opt/bitnami/kafka/conf/certs/zookeeper.truststore.pem` No defaults.
|
||||
* `KAFKA_ZOOKEEPER_TLS_KEYSTORE_PASSWORD`: Apache Kafka Zookeeper keystore file password and key password. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_TLS_TRUSTSTORE_PASSWORD`: Apache Kafka Zookeeper truststore file password. No defaults.
|
||||
* `KAFKA_ZOOKEEPER_TLS_VERIFY_HOSTNAME`: Verify Zookeeper hostname on TLS certificates. Defaults: **true**.
|
||||
* `KAFKA_ZOOKEEPER_TLS_TYPE`: Choose the TLS certificate format to use. Allowed values: `JKS`, `PEM`. Defaults: **JKS**.
|
||||
|
||||
> Note: You **must** also use your own certificates for SSL. You can mount your Java Key Stores (`zookeeper.keystore.jks` and `zookeeper.truststore.jks`) or PEM files (`zookeeper.keystore.pem`, `zookeeper.keystore.key` and `zookeeper.truststore.pem`) into `/opt/bitnami/kafka/conf/certs`. If client authentication is `none` or `want` in Zookeeper, the cert files are optional.
|
||||
|
||||
### Setting up a Kafka Cluster
|
||||
### Setting up a Apache Kafka Cluster
|
||||
|
||||
A Kafka cluster can easily be setup with the Bitnami Kafka Docker image using the following environment variables:
|
||||
A Apache Kafka cluster can easily be setup with the Bitnami Apache Kafka Docker image using the following environment variables:
|
||||
|
||||
- `KAFKA_CFG_ZOOKEEPER_CONNECT`: Comma separated host:port pairs, each corresponding to a Zookeeper Server.
|
||||
|
||||
|
|
@ -476,9 +476,9 @@ $ docker run --name zookeeper \
|
|||
bitnami/zookeeper:latest
|
||||
```
|
||||
|
||||
#### Step 2: Create the first node for Kafka
|
||||
#### Step 2: Create the first node for Apache Kafka
|
||||
|
||||
The first step is to create one Kafka instance.
|
||||
The first step is to create one Apache Kafka instance.
|
||||
|
||||
```console
|
||||
$ docker run --name kafka1 \
|
||||
|
|
@ -491,7 +491,7 @@ $ docker run --name kafka1 \
|
|||
|
||||
#### Step 2: Create the second node
|
||||
|
||||
Next we start a new Kafka container.
|
||||
Next we start a new Apache Kafka container.
|
||||
|
||||
```console
|
||||
$ docker run --name kafka2 \
|
||||
|
|
@ -504,7 +504,7 @@ $ docker run --name kafka2 \
|
|||
|
||||
### Step 3: Create the third node
|
||||
|
||||
Next we start another new Kafka container.
|
||||
Next we start another new Apache Kafka container.
|
||||
|
||||
```console
|
||||
$ docker run --name kafka3 \
|
||||
|
|
@ -515,7 +515,7 @@ $ docker run --name kafka3 \
|
|||
bitnami/kafka:latest
|
||||
```
|
||||
|
||||
You now have a Kafka cluster up and running. You can scale the cluster by adding/removing slaves without incurring any downtime.
|
||||
You now have a Apache Kafka cluster up and running. You can scale the cluster by adding/removing slaves without incurring any downtime.
|
||||
|
||||
With Docker Compose, topic replication can be setup using:
|
||||
|
||||
|
|
@ -575,9 +575,9 @@ $ docker run --name kafka -v /path/to/server.properties:/bitnami/kafka/config/se
|
|||
|
||||
After that, your changes will be taken into account in the server's behaviour.
|
||||
|
||||
#### Step 1: Run the Kafka image
|
||||
#### Step 1: Run the Apache Kafka image
|
||||
|
||||
Run the Kafka image, mounting a directory from your host.
|
||||
Run the Apache Kafka image, mounting a directory from your host.
|
||||
|
||||
Modify the [`docker-compose.yml`](https://github.com/bitnami/bitnami-docker-kafka/blob/master/docker-compose.yml) file present in this repository:
|
||||
|
||||
|
|
@ -599,9 +599,9 @@ Edit the configuration on your host using your favorite editor.
|
|||
vi /path/to/server.properties
|
||||
```
|
||||
|
||||
#### Step 3: Restart Kafka
|
||||
#### Step 3: Restart Apache Kafka
|
||||
|
||||
After changing the configuration, restart your Kafka container for changes to take effect.
|
||||
After changing the configuration, restart your Apache Kafka container for changes to take effect.
|
||||
|
||||
```console
|
||||
$ docker restart kafka
|
||||
|
|
@ -615,7 +615,7 @@ $ docker-compose restart kafka
|
|||
|
||||
## Logging
|
||||
|
||||
The Bitnami Kafka Docker image sends the container logs to the `stdout`. To view the logs:
|
||||
The Bitnami Apache Kafka Docker image sends the container logs to the `stdout`. To view the logs:
|
||||
|
||||
```console
|
||||
$ docker logs kafka
|
||||
|
|
@ -681,7 +681,7 @@ kafka:
|
|||
|
||||
### Upgrade this image
|
||||
|
||||
Bitnami provides up-to-date versions of Kafka, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.
|
||||
Bitnami provides up-to-date versions of Apache Kafka, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.
|
||||
|
||||
#### Step 1: Get the updated image
|
||||
|
||||
|
|
@ -728,7 +728,7 @@ $ docker-compose up kafka
|
|||
|
||||
### 3.0.0-debian-10-r0
|
||||
|
||||
* Apache Kafka 3.0 deprecates the `--zookeper` flag in shell commands. Related operations such as topic creation require the use of updated flags. Please, refer to [Kafka's official release notes](https://downloads.apache.org/kafka/3.0.0/RELEASE_NOTES.html) for further information on the changes introduced by this version.
|
||||
* Apache Apache Kafka 3.0 deprecates the `--zookeper` flag in shell commands. Related operations such as topic creation require the use of updated flags. Please, refer to [Apache Kafka's official release notes](https://downloads.apache.org/kafka/3.0.0/RELEASE_NOTES.html) for further information on the changes introduced by this version.
|
||||
|
||||
### 2.5.0-debian-10-r111
|
||||
|
||||
|
|
@ -750,20 +750,20 @@ The configuration directory was changed to `/opt/bitnami/kafka/config`. Configur
|
|||
|
||||
### 1.1.1-debian-9-r224, 2.2.1-debian-9-r16, 1.1.1-ol-7-r306 and 2.2.1-ol-7-r14
|
||||
|
||||
* The following environment variables were beingly wrongly translated into `KAFKA_CFG_` environment variables, and therefore they were being wrongly mapped into Kafka keys:
|
||||
* The following environment variables were beingly wrongly translated into `KAFKA_CFG_` environment variables, and therefore they were being wrongly mapped into Apache Kafka keys:
|
||||
|
||||
* `KAFKA_LOGS_DIRS` -> `KAFKA_CFG_LOG_DIRS`
|
||||
* `KAFKA_PORT_NUMBER` -> `KAFKA_CFG_PORT`
|
||||
* `KAFKA_ZOOKEEPER_CONNECT_TIMEOUT_MS` -> `KAFKA_CFG_ZOOKEEPER_CONNECTION_TIMEOUT_MS`
|
||||
|
||||
* For consistency reasons with previous environment variables, the following `KAFKA_` to `KAFKA_CFG_` environment variable translations are now supported for mapping into Kafka keys:
|
||||
* For consistency reasons with previous environment variables, the following `KAFKA_` to `KAFKA_CFG_` environment variable translations are now supported for mapping into Apache Kafka keys:
|
||||
|
||||
* `KAFKA_LOG_DIRS` -> `KAFKA_CFG_LOG_DIRS`
|
||||
* `KAFKA_ZOOKEEPER_CONNECTION_TIMEOUT_MS` -> `KAFKA_CFG_ZOOKEEPER_CONNECTION_TIMEOUT_MS`
|
||||
|
||||
### 1.1.1-debian-9-r205, 2.2.0-debian-9-r40, 1.1.1-ol-7-r286, and 2.2.0-ol-7-r53
|
||||
|
||||
Configuration changes. Most environment variables now start with `KAFKA_CFG_`, as they are now mapped directly to Kafka keys. Variables changed:
|
||||
Configuration changes. Most environment variables now start with `KAFKA_CFG_`, as they are now mapped directly to Apache Kafka keys. Variables changed:
|
||||
|
||||
* `KAFKA_ADVERTISED_LISTENERS` -> `KAFKA_CFG_ADVERTISED_LISTENERS`
|
||||
* `KAFKA_BROKER_ID` -> `KAFKA_CFG_BROKER_ID`
|
||||
|
|
|
|||
Loading…
Reference in New Issue