[bitnami/kafka] Unify and document production values

Signed-off-by: Carlos Rodriguez Hernandez <crhernandez@bitnami.com>
This commit is contained in:
Carlos Rodriguez Hernandez
2019-06-07 12:29:30 +00:00
parent f37e9a84d6
commit 9cabcc9e1a
4 changed files with 64 additions and 3 deletions

View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: kafka
version: 3.0.4
version: 3.0.5
appVersion: 2.2.1
description: Apache Kafka is a distributed streaming platform.
keywords:

View File

@@ -178,6 +178,69 @@ $ helm install --name my-release -f values.yaml bitnami/kafka
> **Tip**: You can use the default [values.yaml](values.yaml)
### Production configuration
This chart includes a `values-production.yaml` file where you can find some parameters oriented to production configuration in comparison to the regular `values.yaml`:
- Number of Kafka nodes:
```diff
- replicaCount: 1
+ replicaCount: 3
```
- Allow to use the PLAINTEXT listener:
```diff
- allowPlaintextListener: true
+ allowPlaintextListener: false
```
- Default replication factors for automatically created topics:
```diff
- defaultReplicationFactor: 1
+ defaultReplicationFactor: 3
```
- The replication factor for the offsets topic:
```diff
- offsetsTopicReplicationFactor: 1
+ offsetsTopicReplicationFactor: 3
```
- The replication factor for the transaction topic:
```diff
- transactionStateLogReplicationFactor: 1
+ transactionStateLogReplicationFactor: 3
```
- Overridden min.insync.replicas config for the transaction topic:
```diff
- transactionStateLogMinIsr: 1
+ transactionStateLogMinIsr: 3
```
- Switch to enable the kafka authentication:
```diff
- auth.enabled: false
+ auth.enabled: true
```
- Whether or not to create a separate Kafka exporter:
```diff
- metrics.kafka.enabled: false
+ metrics.kafka.enabled: true
```
- Whether or not to expose JMX metrics to Prometheus:
```diff
- metrics.jmx.enabled: false
+ metrics.jmx.enabled: true
```
- Zookeeper chart metrics configuration:
```diff
+ zookeeper.metrics.enabled: true
```
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.

View File

@@ -54,7 +54,6 @@ updateStrategy: RollingUpdate
podDisruptionBudget:
maxUnavailable: 1
replicaCount: 3
config: |-

View File

@@ -54,7 +54,6 @@ updateStrategy: RollingUpdate
podDisruptionBudget:
maxUnavailable: 1
replicaCount: 1
config: |-