Ordering Event Streaming¶
We provision and operate the Apache Kafka cluster for you. Once the cluster
exists, you manage your own topics, users and access control lists (ACLs) as
KafkaTopic and KafkaUser resources. This page describes how to order a
cluster and which options you can choose.
How to Order¶
Open a ticket in our Service Desk. State that you want an Event Streaming (Kafka) cluster and include the information below.
Information to Include¶
| Field | Required | Description | Example |
|---|---|---|---|
| Cluster | Yes | The Contain Platform cluster the Kafka cluster runs in. | prod1-dc4 |
| Namespace | Yes | The namespace we provision the Kafka cluster in. Your KafkaTopic and KafkaUser resources live in the same namespace. |
your-application-namespace |
| Cluster name | No | The name of the Kafka resource. We choose one if you leave it out. |
my-kafka-cluster |
| Environment | Yes | Production or non-production. This decides the default size and availability. | Production |
| Size | Yes | The broker count, compute and storage you need. See Options. | 3 brokers, medium |
| Expected load | No | Message rate, average message size and retention. We use this to validate the size. | 2,000 msg/s, 1 KB, 7 days |
| Technical contact | Yes | The person we contact about the cluster. | Name and email |
Options¶
| Option | Choices | Guidance |
|---|---|---|
| Broker count | 1 or 3 | Use 1 broker for development and test only. It has no redundancy, so topics can only use a replication factor of 1. Use 3 brokers for production. With 3 brokers, topics can use a replication factor of 3 with min.insync.replicas: 2, so the cluster tolerates the loss of one broker without data loss. |
| Compute per broker | Small, medium or large | CPU and memory reserved for each broker. Throughput, partition count and the number of connected clients drive the need. |
| Storage per broker | Size in GiB | The disk available to each broker. Size it from message rate × message size × retention × replication factor, divided by the broker count, plus headroom. |
| Kafka version | Current supported version | We run a Kafka version supported by the Strimzi operator on the platform and upgrade it as part of operating the service. |
The cluster accepts client connections with SCRAM-SHA-512 authentication over
TLS on port 9093. You create the users with KafkaUser resources.
What You Receive¶
When the cluster is ready, we tell you:
- The name of the
Kafkaresource. You set it in thestrimzi.io/clusterlabel on everyKafkaTopicandKafkaUseryou create. - The bootstrap address your applications connect to.
Changes and Cancellation¶
To resize, upgrade or remove a cluster, open a new Service Desk ticket that names the cluster and the change you need. Topics and users are your own resources, so you change them in your GitOps repository without a ticket.
Next Steps¶
- Getting Started shows how to create topics, users and ACLs.
- Reference:
KafkaTopicand Reference:KafkaUserlist every field you can set.