From 5298f6af208f2f7fa700efedc6bc623a68cb1944 Mon Sep 17 00:00:00 2001 From: Rowena Date: Mon, 18 Aug 2025 17:43:46 +0200 Subject: [PATCH 01/14] feat(kafka): start doc --- .../additional-content/index.mdx | 5 ++ pages/clusters-for-kafka/concepts.mdx | 57 +++++++++++++ pages/clusters-for-kafka/faq.mdx | 18 +++++ .../how-to/create-cluster.mdx | 42 ++++++++++ pages/clusters-for-kafka/how-to/index.mdx | 5 ++ pages/clusters-for-kafka/index.mdx | 80 +++++++++++++++++++ pages/clusters-for-kafka/quickstart.mdx | 18 +++++ .../troubleshooting/index.mdx | 44 ++++++++++ 8 files changed, 269 insertions(+) create mode 100644 pages/clusters-for-kafka/additional-content/index.mdx create mode 100644 pages/clusters-for-kafka/concepts.mdx create mode 100644 pages/clusters-for-kafka/faq.mdx create mode 100644 pages/clusters-for-kafka/how-to/create-cluster.mdx create mode 100644 pages/clusters-for-kafka/how-to/index.mdx create mode 100644 pages/clusters-for-kafka/index.mdx create mode 100644 pages/clusters-for-kafka/quickstart.mdx create mode 100644 pages/clusters-for-kafka/troubleshooting/index.mdx diff --git a/pages/clusters-for-kafka/additional-content/index.mdx b/pages/clusters-for-kafka/additional-content/index.mdx new file mode 100644 index 0000000000..e618893973 --- /dev/null +++ b/pages/clusters-for-kafka/additional-content/index.mdx @@ -0,0 +1,5 @@ +--- +title: Clusters for Apache Kafka® - Additional content +description: Clusters for Apache Kafka® Additional content +noindex: true +--- diff --git a/pages/clusters-for-kafka/concepts.mdx b/pages/clusters-for-kafka/concepts.mdx new file mode 100644 index 0000000000..25ee14c8fd --- /dev/null +++ b/pages/clusters-for-kafka/concepts.mdx @@ -0,0 +1,57 @@ +--- +title: Clusters for Apache Kafka® - Concepts +description: Understand the key concepts for Clusters for Apache Kafka®. +tags: billing account pricing payment +dates: + posted: 2025-08-20 + validation: 2025-08-20 +noindex: true +--- + + +Clusters for Apache Kafka® is currently in [Private Beta](https://www.scaleway.com/en/betas/) and available to selected testers only. + + +## Cluster + +A cluster is a deployment of Apache Kafka®. It consists of one or more nodes (called **brokers**) that work together to store, manage and distribute event streams. [Data replication](#data-replication) across the cluster ensures high availability and robustness. + +## Clusters for Apache Kafka® + +Clusters for Apache Kafka® is Scaleway's product to provide a secure, fully-managed infrastructure for your Apache Kafka® deployments. With our clusters, you can create data pipelines and event-driven architectures that run natively on Apache Kafka®, without having to manage the underlying infrastructure. + +## Credentials + +Credentials consist of a username and password that allow you to connect to your cluster. These are defined during cluster creation. During Private Beta, a limit of one user (ie one set of credentials) per cluster is applied. + +## Data replication + +Data replication is the mechanism that ensures event data is copied across multiple brokers in a cluster, for fault tolerance and high availability. If a node fails, data replication means Apache Kafka® can keep serving data without downtime or data loss. + +## Endpoint + +During Private Beta, access to your Cluster for Apache Kafka® is via private endpoints only. When creating your cluster, you must attach it to a [Private Network](/vpc/concepts/#private-networks), and all nodes in the cluster receive a private IPv4 endpoint on this network. Endpoints are in a format similar to `bf610fb0-f7eb-4ec3-a893...634aea.Kafka.fr-par.scw.cloud`. + +## Event streaming + +Clusters for Apache Kafka® is specifically designed for implementing event streaming at scale. Event streaming is the process of capturing, storing and processing a continuous flow of events in real time. Each event represents something that happened,e.g.`User added item to cart`, `User clicked 'Pay now'`, `Payment was rejected by bank`. Events are stored in topics, e.g. `Inventory`, `Payment`, `Orders`. Typically, programs and microservices subscribe to these topics to consume their events and take action in relation to them, e.g. `Generate invoice`, `Check for fraud`, `Program delivery`. + +## Node + +A Cluster for Apache Kafka® consists of one or more nodes, also called **brokers**. Nodes work together to store, manage and distribute event streams. When creating a cluster, you can choose between **dedicated** nodes or **shared** nodes, based on your workload requirements, budget and use case: + +- **Dedicated node**: Runs only your cluster, with no other customers sharing the broker's resources. +- **Shared node**: Runs your cluster along with other customers', on the same broker. + +## Storage + +A cluster's storage is used to persist events, so they can be reliably consumed by services and applications. During Private Beta, each Cluster for Cluster for Apache Kafka® has a fixed amount of 100 GB of storage per node. + +## TLS certificate + +A TLS certificate (aka SSL certificate) is a digital credential that encrypts data in transit and verifies the identity of a server or client. Scaleway generates a TLS certificate for each Cluster for Apache Kafka®, and all clients connecting to the cluster must install this certificate in order to be authenticated. This ensures secure and encrypted communication between nodes (brokers) and clients. + +## Users + +See [credentials](#credentials). + diff --git a/pages/clusters-for-kafka/faq.mdx b/pages/clusters-for-kafka/faq.mdx new file mode 100644 index 0000000000..dbdac0d894 --- /dev/null +++ b/pages/clusters-for-kafka/faq.mdx @@ -0,0 +1,18 @@ +--- +title: Clusters for Apache Kafka® FAQ +description: Discover Clusters for Apache Kafka® TODO +dates: + validation: 2025-08-20 + posted: 2025-08-20 +productIcon: TODO +noindex: true +--- +## Cat 1 + +### FAQ 1 + +TODO + +### FAQ 2 + +TODO \ No newline at end of file diff --git a/pages/clusters-for-kafka/how-to/create-cluster.mdx b/pages/clusters-for-kafka/how-to/create-cluster.mdx new file mode 100644 index 0000000000..14274cd687 --- /dev/null +++ b/pages/clusters-for-kafka/how-to/create-cluster.mdx @@ -0,0 +1,42 @@ +--- +title: How to create a Cluster for Apache Kafka® +description: Learn how to create a Cluster for Apache Kafka® wih Scaleway, and get your hosted, fully-managed Kafka infrastructure up and running with just a few clicks. +dates: + validation: 2025-08-20 + posted: 2025-08-20 +noindex: true +--- +import Requirements from '@macros/iam/requirements.mdx' + + +Clusters for Apache Kafka® is currently in [Private Beta](https://www.scaleway.com/en/betas/) and available to selected testers only. + + +This page shows you how to create a Cluster for Apache Kafka® via the Scaleway console. + + + + - A Scaleway account logged into the [console](https://console.scaleway.com) + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + +1. Click **Apache Kafka®** in the **Data and Analytics** section of the [console](https://console.scaleway.com/) side menu. The **Clusters for Apache Kafka®a** product page displays. + +2. Click **Create cluster**. The creation wizard displays. + +3. Select a **region** for the cluster. During Private Beta, clusters are only available in the Paris region. + +4. Select a **Kafka® version** to run on the cluster. Only one pre-selected Kafka® version is available during Private Beta. + +5. Select the **number of nodes** (brokers) you want in the cluster, either **3 nodes** for a highly-available cluster enabling data replication, or **1 node** for a cluster suitable for testing and development. During Private Beta, the number of nodes cannot be changed after cluster creation. + +6. Select a **node type**. Choose between [dedicated or shared nodes](/clusters-for-kafka/concepts/#node), depending on your workload requirements and use case. For shared nodes, various types are available, each offering different cost-performance ratios. + +7. Configure **network connectivity**. During Private Beta, connectivity to clusters is facilitated exclusively through **Private Networks**. Select a Private Network from the dropdown list to attach your cluster to. + +8. Create **credentials** by defining a username and password. These will be used when connecting to your cluster. During Private Beta, only one user can be created per cluster, and the username is not modifiable after creation (though the password can be changed). + +9. Enter a **name**, and (optionally), **tags** to identify your cluster. + +10. Check the estimated cost summary, then click **Create cluster**. + +Your cluster is created, and you are taken to its **Overview** page in the console. diff --git a/pages/clusters-for-kafka/how-to/index.mdx b/pages/clusters-for-kafka/how-to/index.mdx new file mode 100644 index 0000000000..b431bfc49e --- /dev/null +++ b/pages/clusters-for-kafka/how-to/index.mdx @@ -0,0 +1,5 @@ +--- +title: Clusters for Apache Kafka® - How Tos +description: Clusters for Apache Kafka® How Tos +noindex: true +--- diff --git a/pages/clusters-for-kafka/index.mdx b/pages/clusters-for-kafka/index.mdx new file mode 100644 index 0000000000..57ca0166f6 --- /dev/null +++ b/pages/clusters-for-kafka/index.mdx @@ -0,0 +1,80 @@ +--- +title: Clusters for Apache Kafka® Documentation +description: Dive into Scaleway Clusters for Apache Kafka® with our quickstart guides, how-tos and more. +noindex: true +--- + + + +## Getting Started + + + + + + + + +## FAQ + + + + + + + + + + +## Changelog + + diff --git a/pages/clusters-for-kafka/quickstart.mdx b/pages/clusters-for-kafka/quickstart.mdx new file mode 100644 index 0000000000..8de157e7fa --- /dev/null +++ b/pages/clusters-for-kafka/quickstart.mdx @@ -0,0 +1,18 @@ +--- +title: Clusters for Apache Kafka® - Quickstart +description: Quickstart guide to setting up and managing Scaleway Clusters for Apache Kafka®. +tags: cluster apache kafka +dates: + validation: 2025-08-20 + posted: 2025-08-20 +noindex: true +--- +import Requirements from '@macros/iam/requirements.mdx' + + + + +- A Scaleway account logged into the [console](https://console.scaleway.com) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + +TODO \ No newline at end of file diff --git a/pages/clusters-for-kafka/troubleshooting/index.mdx b/pages/clusters-for-kafka/troubleshooting/index.mdx new file mode 100644 index 0000000000..baedd9bd33 --- /dev/null +++ b/pages/clusters-for-kafka/troubleshooting/index.mdx @@ -0,0 +1,44 @@ +--- +title: Clusters for Apache Kafka® +description: Find troubleshooting resources for resolving issues with Scaleway Clusters for Apache Kafka®. +dates: + posted: 2025-08-20 +productIcon: TODO +noindex: true +--- + + + +## Featured Pages + + + + + + + +## Clusters for Apache Kafka® troubleshooting pages + + + - TODO + - TODO + From edc7d3c6ee63d9b38723816a8f9700115b5fd146 Mon Sep 17 00:00:00 2001 From: Rowena Date: Tue, 19 Aug 2025 15:59:34 +0200 Subject: [PATCH 02/14] feat(kafka): finish main doc --- .../additional-content/index.mdx | 5 -- pages/clusters-for-kafka/faq.mdx | 34 ++++++-- .../how-to/connect-to-cluster.mdx | 82 +++++++++++++++++++ .../how-to/create-cluster.mdx | 2 +- .../how-to/delete-cluster.mdx | 37 +++++++++ .../how-to/manage-cluster.mdx | 69 ++++++++++++++++ pages/clusters-for-kafka/index.mdx | 14 ++-- pages/clusters-for-kafka/quickstart.mdx | 10 +++ .../troubleshooting/index.mdx | 44 ---------- 9 files changed, 235 insertions(+), 62 deletions(-) delete mode 100644 pages/clusters-for-kafka/additional-content/index.mdx create mode 100644 pages/clusters-for-kafka/how-to/connect-to-cluster.mdx create mode 100644 pages/clusters-for-kafka/how-to/delete-cluster.mdx create mode 100644 pages/clusters-for-kafka/how-to/manage-cluster.mdx delete mode 100644 pages/clusters-for-kafka/troubleshooting/index.mdx diff --git a/pages/clusters-for-kafka/additional-content/index.mdx b/pages/clusters-for-kafka/additional-content/index.mdx deleted file mode 100644 index e618893973..0000000000 --- a/pages/clusters-for-kafka/additional-content/index.mdx +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Clusters for Apache Kafka® - Additional content -description: Clusters for Apache Kafka® Additional content -noindex: true ---- diff --git a/pages/clusters-for-kafka/faq.mdx b/pages/clusters-for-kafka/faq.mdx index dbdac0d894..a2a3f2675d 100644 --- a/pages/clusters-for-kafka/faq.mdx +++ b/pages/clusters-for-kafka/faq.mdx @@ -7,12 +7,36 @@ dates: productIcon: TODO noindex: true --- -## Cat 1 -### FAQ 1 + +Clusters for Apache Kafka® is currently in [Private Beta](https://www.scaleway.com/en/betas/) and available to selected testers only. + -TODO +## General -### FAQ 2 +### What is Clusters for Apache Kafka®? -TODO \ No newline at end of file +Clusters for Apache Kafka® is Scaleway's product to provide a secure, fully-managed infrastructure for your Apache Kafka® deployments. With our clusters, you can create data pipelines and event-driven architectures that run natively on Apache Kafka®, without having to manage the underlying infrastructure. This product is currently in Private Beta. + +### What limitations apply during the Private Beta? + +Private Beta is aimed at providing an early version of a future product, to allow users to test and validate it during its development. The following limitations apply to Clusters for Apache Kafka® in its current Private Beta phase: + +- Only selected users can test the product ([request an invitation](https://www.scaleway.com/en/betas/)) +- Only one Kafka version is supported (TODO). +- Clusters can only be provisioned with either one or three nodes (brokers). +- Storage is fixed at 100 GB per node. +- Connectivity to the cluster is facilitated exclusively through Private Networks. +- Only one set of credentials (username and password) can be created per cluster. + +We aim to improve and develop the product based on feedback received during the beta stage. + +## Billing + +### How am I billed for Clusters for Apache Kafka®? + +Clusters for Apache Kafka® are free of charge during Private Beta, and you will not be billed. + +### How will pricing work in the future? + +We anticipate that future pricing will be based on TODO. diff --git a/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx b/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx new file mode 100644 index 0000000000..632ebdef5e --- /dev/null +++ b/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx @@ -0,0 +1,82 @@ +--- +title: How to connect to a Cluster for Apache Kafka® +description: Learn how to connect to your Scaleway Cluster for Apache Kafka® wih Scaleway, and understand how to securely establish a connection using TLS certificates and credentials. +dates: + validation: 2025-08-20 + posted: 2025-08-20 +noindex: true +--- +import Requirements from '@macros/iam/requirements.mdx' + + +Clusters for Apache Kafka® is currently in [Private Beta](https://www.scaleway.com/en/betas/) and available to selected testers only. + + +You can use different frameworks to connect to your Cluster for Apache Kafka®, and integrate it with your applications. + +All clients that want to connect to your cluster must: + +- Have downloaded the cluster's [TLS certificate](TODO) and configured the client to recognize it +- Be attached to a Private Network in the same VPC as the cluster, or connect via a Public Gateway in the VPC +- Know the cluster's username and password + + + + - A Scaleway account logged into the [console](https://console.scaleway.com) + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - A Cluster for Apache Kafka® + +## How to download the TLS certificate + +1. Click **Apache Kafka®** in the **Data and Analytics** section of the [console](https://console.scaleway.com/) side menu. A list of your clusters displays. + +2. Click the cluster you want to connect to. Its **Overview** page displays. + +3. In the **Connectivity** panel, click **Download** next to the TLS certificate. + +The TLS certificate is downloaded to your local device. If using Java, import it into a truststore and configure your `client.properties` appropriately. For other types of client (e.g. Python, Go, CLI), you may be able to use the certificate directly by setting its location in your Kafka consumer configuration code (e.g. `'ssl.ca.location': '/path/to/ca.crt'`). + +TODO CHECK: +- Check all of the info above +- Add more info for +- Server side TLS only? (no client cert needed?) +- What CA is used? Is it well known or private? Is the TLS cert in crt or pem format? + +## How to ensure clients have network access + +Any clients wanting to connect to the cluster must either be attached to a Private Network in the same VPC as the cluster, or connect via a Public Gateway in the VPC. + +TODO set up static NAT to map ports/IP address? + +See the following pages for help: +- [How to attach a resource to a Private Network](/vpc/how-to/attach-resources-to-pn/) +- [How to create a Public Gateway](/public-gateways/how-to/create-a-public-gateway/) +- [Getting the most from Private Networks](/vpc/reference-content/getting-most-private-networks/) + +## How to access the username and password + +The username and password for a Cluster for Apache Kafka® are defined when [creating the cluster](/clusters-for-kafka/how-to/create-cluster/). During Private Beta, only one user can be created per cluster. The username cannot be modified after creation, but the password can be changed at any time. + +If you need a reminder of the username after creating the cluster, follow the steps below. You cannot view the password you set, but you can change it to a new one. + +1. Click **Apache Kafka®** in the **Data and Analytics** section of the [console](https://console.scaleway.com/) side menu. A list of your clusters displays. + +2. Click the cluster you want to connect to. Its **Overview** page displays. + +3. Click the **Users** tab. + +The username displays in the list of users. Click **Change password** if you have forgotten the password and need to change it to a new one. + +## How to connect to the cluster + +Once you have ensured that the client in question has the cluster's TLS certificate, appropriate network access and the correct username and password, you can facilitate connection via the framework of your choice. Code snippets are provided for Go, Python and Java; access them by following the steps below. + +1. Click **Apache Kafka®** in the **Data and Analytics** section of the [console](https://console.scaleway.com/) side menu. A list of your clusters displays. + +2. Click the cluster you want to connect to. Its **Overview** page displays. + +3. In the **Connectivity** panel, click **Connect**. + + A pop-up displays, with tabs for each sample framework: **Go**, **Python** and **Java**. + +4. Click the tab of your choice to view the code sample. \ No newline at end of file diff --git a/pages/clusters-for-kafka/how-to/create-cluster.mdx b/pages/clusters-for-kafka/how-to/create-cluster.mdx index 14274cd687..44cdb5dfd4 100644 --- a/pages/clusters-for-kafka/how-to/create-cluster.mdx +++ b/pages/clusters-for-kafka/how-to/create-cluster.mdx @@ -1,6 +1,6 @@ --- title: How to create a Cluster for Apache Kafka® -description: Learn how to create a Cluster for Apache Kafka® wih Scaleway, and get your hosted, fully-managed Kafka infrastructure up and running with just a few clicks. +description: Learn how to create a Cluster for Apache Kafka® with Scaleway, and get your hosted, fully-managed Kafka infrastructure up and running with just a few clicks. dates: validation: 2025-08-20 posted: 2025-08-20 diff --git a/pages/clusters-for-kafka/how-to/delete-cluster.mdx b/pages/clusters-for-kafka/how-to/delete-cluster.mdx new file mode 100644 index 0000000000..b2a5539c15 --- /dev/null +++ b/pages/clusters-for-kafka/how-to/delete-cluster.mdx @@ -0,0 +1,37 @@ +--- +title: How to delete to a Cluster for Apache Kafka® +description: Learn how to safely delete your Scaleway Cluster for Apache Kafka® wih Scaleway in just a few clicks. +dates: + validation: 2025-08-20 + posted: 2025-08-20 +noindex: true +--- +import Requirements from '@macros/iam/requirements.mdx' + + +Clusters for Apache Kafka® is currently in [Private Beta](https://www.scaleway.com/en/betas/) and available to selected testers only. + + +You can delete your cluster at any time by following the steps on this page. + + + + - A Scaleway account logged into the [console](https://console.scaleway.com) + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - A Cluster for Apache Kafka® + +## How to delete a cluster + +1. Click **Apache Kafka®** in the **Data and Analytics** section of the [console](https://console.scaleway.com/) side menu. A list of your clusters displays. + +2. Click the cluster you want to delete. Its **Overview** page displays. + +3. Click the **Settings** tab. + +4. Click **Delete cluster**. + + A pop-up displays, informing you that this action will permanently delete the cluster, and all data stored on its nodes will be lost. + +5. Type **DELETE** in the box, and click **Delete cluster**. + + The cluster is deleted, and you are returned to the product page. \ No newline at end of file diff --git a/pages/clusters-for-kafka/how-to/manage-cluster.mdx b/pages/clusters-for-kafka/how-to/manage-cluster.mdx new file mode 100644 index 0000000000..9f4f3ccacd --- /dev/null +++ b/pages/clusters-for-kafka/how-to/manage-cluster.mdx @@ -0,0 +1,69 @@ +--- +title: How to manage to a Cluster for Apache Kafka® +description: Learn how to manage to your Scaleway Cluster for Apache Kafka® wih Scaleway, including editing its details, renewing its TLS certificate and more. +dates: + validation: 2025-08-20 + posted: 2025-08-20 +noindex: true +--- +import Requirements from '@macros/iam/requirements.mdx' + + +Clusters for Apache Kafka® is currently in [Private Beta](https://www.scaleway.com/en/betas/) and available to selected testers only. + + +After creating your cluster, you can renew its TLS certificate, change the attached Private Network, and change its password. + + + + - A Scaleway account logged into the [console](https://console.scaleway.com) + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - A Cluster for Apache Kafka® + +## How to renew the TLS certificate + +You may want or need to renew the cluster's TLS certificate for reasons of security, compliance or if the certificate expires. Follow the steps below to renew the certificate: + +1. Click **Apache Kafka®** in the **Data and Analytics** section of the [console](https://console.scaleway.com/) side menu. A list of your clusters displays. + +2. Click the cluster whose certificate you want to renew. Its **Overview** page displays. + +3. In the **Connectivity** panel, click **Renew** next to the TLS certificate. + + A pop-up displays, warning you that you will not be able to connect to your cluster using the previous certificate, and you will need to download the new certificate for all clients. + +4. Click **Renew TLS certificate** to confirm. + +The certificate is renewed, and you are returned to the cluster's **Overview** page. Remember to download the new certificate for all clients that want to connect to the cluster. + +## How to change the attached Private Network + +In order to facilitate connectivity to your cluster, it must always be attached to a Private Network. A cluster can only be attached to one Private Network at a time, but you can change the attached Private Network as follows: + +1. Click **Apache Kafka®** in the **Data and Analytics** section of the [console](https://console.scaleway.com/) side menu. A list of your clusters displays. + +2. Click the cluster whose certificate you want to renew. Its **Overview** page displays. + +3. In the **Network** panel, click **Detach Private Network** + +TODO + +## How to change the password + +During Private Beta, each cluster can have only one set of user credentials, which are set during cluster creation. You cannot change the username after creating the cluster, but you can change the password at any time: + +1. Click **Apache Kafka®** in the **Data and Analytics** section of the [console](https://console.scaleway.com/) side menu. A list of your clusters displays. + +2. Click the cluster whose password you want to change. Its **Overview** page displays. + +3. Click the **Users** tab. + +4. Click **Change password** next to the cluster's username credential. + + A pop-up displays, prompting you to change the password. Either enter the new password of your choice, or click **Generate password** to generate a new random password. + + Ensure that you copy or remember the password, as it will not be displayed again after this screen. + +5. Click **Update**. + + The password is changed and you are returned to your cluster's **Overview** page. \ No newline at end of file diff --git a/pages/clusters-for-kafka/index.mdx b/pages/clusters-for-kafka/index.mdx index 57ca0166f6..af687fe54d 100644 --- a/pages/clusters-for-kafka/index.mdx +++ b/pages/clusters-for-kafka/index.mdx @@ -5,11 +5,11 @@ noindex: true --- ## Getting Started @@ -18,9 +18,9 @@ noindex: true - -## Featured Pages - - - - - - - -## Clusters for Apache Kafka® troubleshooting pages - - - - TODO - - TODO - From 1269b732450548f93a35eb52e89d5ba7ae9f8e09 Mon Sep 17 00:00:00 2001 From: Rowena Date: Tue, 19 Aug 2025 16:23:45 +0200 Subject: [PATCH 03/14] fix(kafka): edits --- pages/clusters-for-kafka/faq.mdx | 1 + .../how-to/connect-to-cluster.mdx | 2 +- .../how-to/create-cluster.mdx | 2 + pages/clusters-for-kafka/index.mdx | 43 ++++--------------- 4 files changed, 13 insertions(+), 35 deletions(-) diff --git a/pages/clusters-for-kafka/faq.mdx b/pages/clusters-for-kafka/faq.mdx index a2a3f2675d..264aea52f5 100644 --- a/pages/clusters-for-kafka/faq.mdx +++ b/pages/clusters-for-kafka/faq.mdx @@ -25,6 +25,7 @@ Private Beta is aimed at providing an early version of a future product, to allo - Only selected users can test the product ([request an invitation](https://www.scaleway.com/en/betas/)) - Only one Kafka version is supported (TODO). - Clusters can only be provisioned with either one or three nodes (brokers). +- The number of nodes cannot be modified after creation of the cluster. - Storage is fixed at 100 GB per node. - Connectivity to the cluster is facilitated exclusively through Private Networks. - Only one set of credentials (username and password) can be created per cluster. diff --git a/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx b/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx index 632ebdef5e..e2e24bcb90 100644 --- a/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx +++ b/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx @@ -16,7 +16,7 @@ You can use different frameworks to connect to your Cluster for Apache Kafka®, All clients that want to connect to your cluster must: -- Have downloaded the cluster's [TLS certificate](TODO) and configured the client to recognize it +- Have downloaded the cluster's [TLS certificate](/clusters-for-kafka/how-to/manage-cluster/) and configured the client to recognize it - Be attached to a Private Network in the same VPC as the cluster, or connect via a Public Gateway in the VPC - Know the cluster's username and password diff --git a/pages/clusters-for-kafka/how-to/create-cluster.mdx b/pages/clusters-for-kafka/how-to/create-cluster.mdx index 44cdb5dfd4..fdd9ad0cb6 100644 --- a/pages/clusters-for-kafka/how-to/create-cluster.mdx +++ b/pages/clusters-for-kafka/how-to/create-cluster.mdx @@ -19,6 +19,8 @@ This page shows you how to create a Cluster for Apache Kafka® via the Scaleway - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +## How to create a Cluster for Apache Kafka® + 1. Click **Apache Kafka®** in the **Data and Analytics** section of the [console](https://console.scaleway.com/) side menu. The **Clusters for Apache Kafka®a** product page displays. 2. Click **Create cluster**. The creation wizard displays. diff --git a/pages/clusters-for-kafka/index.mdx b/pages/clusters-for-kafka/index.mdx index af687fe54d..83e22e11eb 100644 --- a/pages/clusters-for-kafka/index.mdx +++ b/pages/clusters-for-kafka/index.mdx @@ -25,56 +25,31 @@ noindex: true -## FAQ - - - - - - - - ## Changelog From 40726d9324b9c3deba2c06c92d01f334c05637e5 Mon Sep 17 00:00:00 2001 From: Rowena Date: Tue, 19 Aug 2025 16:27:16 +0200 Subject: [PATCH 04/14] fix(kafka): add quotas --- pages/clusters-for-kafka/faq.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/pages/clusters-for-kafka/faq.mdx b/pages/clusters-for-kafka/faq.mdx index 264aea52f5..f8942344f7 100644 --- a/pages/clusters-for-kafka/faq.mdx +++ b/pages/clusters-for-kafka/faq.mdx @@ -29,6 +29,7 @@ Private Beta is aimed at providing an early version of a future product, to allo - Storage is fixed at 100 GB per node. - Connectivity to the cluster is facilitated exclusively through Private Networks. - Only one set of credentials (username and password) can be created per cluster. +- Each Scaleway Organization in the Private Beta may have a maximum of 5 clusters at one time (TODO CHECK) We aim to improve and develop the product based on feedback received during the beta stage. From c3117a3c05861899e21b473c6ac46dcb9ee18b56 Mon Sep 17 00:00:00 2001 From: Rowena Date: Thu, 21 Aug 2025 13:38:08 +0200 Subject: [PATCH 05/14] fix(kafka): final modifs --- pages/clusters-for-kafka/faq.mdx | 8 +- .../how-to/manage-cluster.mdx | 8 +- pages/clusters-for-kafka/index.mdx | 53 ++++++++++++-- pages/clusters-for-kafka/quickstart.mdx | 73 ++++++++++++++++++- 4 files changed, 127 insertions(+), 15 deletions(-) diff --git a/pages/clusters-for-kafka/faq.mdx b/pages/clusters-for-kafka/faq.mdx index f8942344f7..47faf793e5 100644 --- a/pages/clusters-for-kafka/faq.mdx +++ b/pages/clusters-for-kafka/faq.mdx @@ -1,10 +1,10 @@ --- title: Clusters for Apache Kafka® FAQ -description: Discover Clusters for Apache Kafka® TODO +description: Get answers to all your questions about Scaleway Clusters for Apache Kafka® dates: validation: 2025-08-20 posted: 2025-08-20 -productIcon: TODO +productIcon: KafkaProductIcon noindex: true --- @@ -22,8 +22,8 @@ Clusters for Apache Kafka® is Scaleway's product to provide a secure, fully-man Private Beta is aimed at providing an early version of a future product, to allow users to test and validate it during its development. The following limitations apply to Clusters for Apache Kafka® in its current Private Beta phase: -- Only selected users can test the product ([request an invitation](https://www.scaleway.com/en/betas/)) -- Only one Kafka version is supported (TODO). +- Only selected users can test the product ([request an invitation](https://www.scaleway.com/en/betas/)). +- Only one Kafka version is supported. - Clusters can only be provisioned with either one or three nodes (brokers). - The number of nodes cannot be modified after creation of the cluster. - Storage is fixed at 100 GB per node. diff --git a/pages/clusters-for-kafka/how-to/manage-cluster.mdx b/pages/clusters-for-kafka/how-to/manage-cluster.mdx index 9f4f3ccacd..8167dd3960 100644 --- a/pages/clusters-for-kafka/how-to/manage-cluster.mdx +++ b/pages/clusters-for-kafka/how-to/manage-cluster.mdx @@ -14,6 +14,8 @@ Clusters for Apache Kafka® is currently in [Private Beta](https://www.scaleway. After creating your cluster, you can renew its TLS certificate, change the attached Private Network, and change its password. +Other management actions, such as creating topics and events, and configuring partitions and replication factors, must be carried out via TODO HOW. + - A Scaleway account logged into the [console](https://console.scaleway.com) @@ -46,7 +48,11 @@ In order to facilitate connectivity to your cluster, it must always be attached 3. In the **Network** panel, click **Detach Private Network** -TODO + A pop-up displays, asking you to confirm the action. + +4. Click **Detach resource** to confirm. + +The cluster is detached, and you are returned to its **Overview** page. Click **Attach Private Network** to choose a new Private Network to attach it to. Remember that the cluster is not accessible unless it is attached to a Private Network. ## How to change the password diff --git a/pages/clusters-for-kafka/index.mdx b/pages/clusters-for-kafka/index.mdx index 83e22e11eb..02f0674779 100644 --- a/pages/clusters-for-kafka/index.mdx +++ b/pages/clusters-for-kafka/index.mdx @@ -6,12 +6,18 @@ noindex: true + + This product is currently in [Private Beta](https://www.scaleway.com/en/betas/) and available to selected testers only. Watch this space to see how the product develops, or ask to join the beta for early access. + + ## Getting Started @@ -30,11 +36,44 @@ noindex: true url="/clusters-for-kafka/concepts" /> + + +## How-to guides + + + + + + @@ -43,13 +82,13 @@ noindex: true productLogo="cli" title="Clusters for Apache Kafka® API" description="Learn how to manage your clusters through the API." - url="https://www.scaleway.com/en/developers/api/TODO/" + url="https://www.scaleway.com/en/developers/api/clusters-for-kafka/" label="Go to Clusters for Apache Kafka® API" /> ## Changelog diff --git a/pages/clusters-for-kafka/quickstart.mdx b/pages/clusters-for-kafka/quickstart.mdx index dfaca6d74f..c0caf2e2e2 100644 --- a/pages/clusters-for-kafka/quickstart.mdx +++ b/pages/clusters-for-kafka/quickstart.mdx @@ -9,6 +9,13 @@ noindex: true --- import Requirements from '@macros/iam/requirements.mdx' + +Clusters for Apache Kafka® is currently in [Private Beta](https://www.scaleway.com/en/betas/) and available to selected testers only. + + +Clusters for Apache Kafka® is Scaleway's product to provide a secure, fully-managed infrastructure for your Apache Kafka® deployments. With our clusters, you can create data pipelines and event-driven architectures that run natively on Apache Kafka®, without having to manage the underlying infrastructure. + +Follow our quickstart guide to get your first cluster up and running efficiently, and know how to delete it when you no longer need it. @@ -17,12 +24,72 @@ import Requirements from '@macros/iam/requirements.mdx' ## How to create a Cluster for Apache Kafka® -TODO +1. Click **Apache Kafka®** in the **Data and Analytics** section of the [console](https://console.scaleway.com/) side menu. The **Clusters for Apache Kafka®a** product page displays. + +2. Click **Create cluster**. The creation wizard displays. + +3. Select a **region** for the cluster. During Private Beta, clusters are only available in the Paris region. + +4. Select a **Kafka® version** to run on the cluster. Only one pre-selected Kafka® version is available during Private Beta. + +5. Select the **number of nodes** (brokers) you want in the cluster, either **3 nodes** for a highly-available cluster enabling data replication, or **1 node** for a cluster suitable for testing and development. During Private Beta, the number of nodes cannot be changed after cluster creation. + +6. Select a **node type**. Choose between [dedicated or shared nodes](/clusters-for-kafka/concepts/#node), depending on your workload requirements and use case. For shared nodes, various types are available, each offering different cost-performance ratios. + +7. Configure **network connectivity**. During Private Beta, connectivity to clusters is facilitated exclusively through **Private Networks**. Select a Private Network from the dropdown list to attach your cluster to. + +8. Create **credentials** by defining a username and password. These will be used when connecting to your cluster. During Private Beta, only one user can be created per cluster, and the username is not modifiable after creation (though the password can be changed). + +9. Enter a **name**, and (optionally), **tags** to identify your cluster. + +10. Check the estimated cost summary, then click **Create cluster**. + +Your cluster is created, and you are taken to its **Overview** page in the console. ## How to connect to your cluster -TODO +All clients that want to connect to your cluster must: + +- Have downloaded the cluster's [TLS certificate](/clusters-for-kafka/how-to/manage-cluster/) and configured the client to recognize it. +- Be [attached to a Private Network](/vpc/how-to/attach-resources-to-pn/) in the same VPC as the cluster, or connect via a [Public Gateway](/public-gateways/how-to/create-a-public-gateway/) in the VPC +- Know the cluster's [username and password](/clusters-for-kafka/how-to/connect-to-cluster/#how-to-access-the-username-and-password) + +Once you have ensured the client satisfies the conditions above, you can facilitate connection via the framework of your choice. Code snippets are provided for Go, Python and Java; access them by following the steps below. + +1. Click **Apache Kafka®** in the **Data and Analytics** section of the [console](https://console.scaleway.com/) side menu. A list of your clusters displays. + +2. Click the cluster you want to connect to. Its **Overview** page displays. + +3. In the **Connectivity** panel, click **Connect**. + + A pop-up displays, with tabs for each sample framework: **Go**, **Python** and **Java**. + +4. Click the tab of your choice to view the code sample. + +## How to configure your cluster + +Configuration actions that cannot currently be carried out via the Scaleway console, API or devtools include: + +- Creating topics, events and streams +- Configuring cluster parameters, such as replication factors, retention policies, and partitions +- Integrating clients and consumers + +These actions can be done via TODO HOW? ## How to delete a cluster -TODO \ No newline at end of file +You can delete your cluster when you no longer need it. + +1. Click **Apache Kafka®** in the **Data and Analytics** section of the [console](https://console.scaleway.com/) side menu. A list of your clusters displays. + +2. Click the cluster you want to delete. Its **Overview** page displays. + +3. Click the **Settings** tab. + +4. Click **Delete cluster**. + + A pop-up displays, informing you that this action will permanently delete the cluster, and all data stored on its nodes will be lost. + +5. Type **DELETE** in the box, and click **Delete cluster**. + + The cluster is deleted, and you are returned to the product page. \ No newline at end of file From 874f7543c283a99b3eb5aecf40e3dca7139d64f2 Mon Sep 17 00:00:00 2001 From: Rowena Date: Thu, 21 Aug 2025 13:50:22 +0200 Subject: [PATCH 06/14] fix(kafka): typos --- pages/clusters-for-kafka/how-to/connect-to-cluster.mdx | 2 +- pages/clusters-for-kafka/quickstart.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx b/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx index e2e24bcb90..aed84cdc45 100644 --- a/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx +++ b/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx @@ -38,7 +38,7 @@ The TLS certificate is downloaded to your local device. If using Java, import it TODO CHECK: - Check all of the info above -- Add more info for +- Add more info to help users with whatever else is likely to be problematic - Server side TLS only? (no client cert needed?) - What CA is used? Is it well known or private? Is the TLS cert in crt or pem format? diff --git a/pages/clusters-for-kafka/quickstart.mdx b/pages/clusters-for-kafka/quickstart.mdx index c0caf2e2e2..c821de750c 100644 --- a/pages/clusters-for-kafka/quickstart.mdx +++ b/pages/clusters-for-kafka/quickstart.mdx @@ -22,7 +22,7 @@ Follow our quickstart guide to get your first cluster up and running efficiently - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization -## How to create a Cluster for Apache Kafka® +## How to create a cluster 1. Click **Apache Kafka®** in the **Data and Analytics** section of the [console](https://console.scaleway.com/) side menu. The **Clusters for Apache Kafka®a** product page displays. From 9b9dae4ed2388f561cb2c534dd8079cac1bfc3d8 Mon Sep 17 00:00:00 2001 From: Rowena Date: Tue, 26 Aug 2025 11:23:40 +0200 Subject: [PATCH 07/14] fix(kafka): add info --- pages/clusters-for-kafka/faq.mdx | 18 ++++++++++++++++++ .../how-to/connect-to-cluster.mdx | 19 +++++-------------- .../how-to/manage-cluster.mdx | 2 +- pages/clusters-for-kafka/quickstart.mdx | 2 +- 4 files changed, 25 insertions(+), 16 deletions(-) diff --git a/pages/clusters-for-kafka/faq.mdx b/pages/clusters-for-kafka/faq.mdx index 47faf793e5..830ef86c6a 100644 --- a/pages/clusters-for-kafka/faq.mdx +++ b/pages/clusters-for-kafka/faq.mdx @@ -18,6 +18,10 @@ Clusters for Apache Kafka® is currently in [Private Beta](https://www.scaleway. Clusters for Apache Kafka® is Scaleway's product to provide a secure, fully-managed infrastructure for your Apache Kafka® deployments. With our clusters, you can create data pipelines and event-driven architectures that run natively on Apache Kafka®, without having to manage the underlying infrastructure. This product is currently in Private Beta. +### How do I use my cluster, and how can I connect to it? + +To use your cluster, you first [connect](/clusters-for-kafka/how-to/connect-to-cluster/) via the Kafka CLI or any supported programming language. The connection is secured, and requires the appropriate credentials, certificate, and endpoint provided by Scaleway. All configuration is done through a Kafka client, allowing you to manage topics, producers, and consumers easily. This flexibility ensures seamless integration with your applications and workflows. + ### What limitations apply during the Private Beta? Private Beta is aimed at providing an early version of a future product, to allow users to test and validate it during its development. The following limitations apply to Clusters for Apache Kafka® in its current Private Beta phase: @@ -33,6 +37,20 @@ Private Beta is aimed at providing an early version of a future product, to allo We aim to improve and develop the product based on feedback received during the beta stage. +### Is Scaleway's Clusters for Apache Kafka® based on the open-source Kafka framework? + +Yes, Scaleway's Clusters for Apache Kafka is built on the open-source Apache Kafka framework. We use the Kafka API to ensure compatibility and leverage the robust features of the open-source ecosystem. + +## How is Apache Kafka® different to RabbitMQ and NATS? + +Apache Kafka, RabbitMQ, and NATS are all messaging systems but serve different purposes and have distinct architectures. + +- Apache Kafka is designed for high-throughput, real-time data streaming, and is topic-based, using the pull model. It can process large amounts of data in real-time with high concurrency and fault tolerance, and is ideal for stream processing, event sourcing, and big data applications. +- RabbitMQ is a versatile message broker that supports multiple protocols, and offers strong support for message delivery guarantees and reliability. It uses the push model, and is well-suited for traditional message queuing and task distribution. +- [NATS](/nats/) is a lightweight, high-performance subject-based messaging system focused on speed and simplicity, making it great for microservices. + +Each system has its own strengths and is suited to different use cases depending on the requirements of the application. + ## Billing ### How am I billed for Clusters for Apache Kafka®? diff --git a/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx b/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx index aed84cdc45..14c190fb6d 100644 --- a/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx +++ b/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx @@ -34,24 +34,15 @@ All clients that want to connect to your cluster must: 3. In the **Connectivity** panel, click **Download** next to the TLS certificate. -The TLS certificate is downloaded to your local device. If using Java, import it into a truststore and configure your `client.properties` appropriately. For other types of client (e.g. Python, Go, CLI), you may be able to use the certificate directly by setting its location in your Kafka consumer configuration code (e.g. `'ssl.ca.location': '/path/to/ca.crt'`). +The TLS certificate in `.pem` format is downloaded to your local device. If using Java, import it into a truststore and configure your `client.properties` appropriately. For other types of client (e.g. Python, Go, CLI), you may be able to use the certificate directly by setting its location in your Kafka consumer configuration code. -TODO CHECK: -- Check all of the info above -- Add more info to help users with whatever else is likely to be problematic -- Server side TLS only? (no client cert needed?) -- What CA is used? Is it well known or private? Is the TLS cert in crt or pem format? + +TLS is server-side only, and no client certificate is required. + ## How to ensure clients have network access -Any clients wanting to connect to the cluster must either be attached to a Private Network in the same VPC as the cluster, or connect via a Public Gateway in the VPC. - -TODO set up static NAT to map ports/IP address? - -See the following pages for help: -- [How to attach a resource to a Private Network](/vpc/how-to/attach-resources-to-pn/) -- [How to create a Public Gateway](/public-gateways/how-to/create-a-public-gateway/) -- [Getting the most from Private Networks](/vpc/reference-content/getting-most-private-networks/) +Any clients wanting to connect to the cluster must be [attached to a Private Network](/vpc/how-to/attach-resources-to-pn/) in the same VPC as the cluster. ## How to access the username and password diff --git a/pages/clusters-for-kafka/how-to/manage-cluster.mdx b/pages/clusters-for-kafka/how-to/manage-cluster.mdx index 8167dd3960..a780c4d7f2 100644 --- a/pages/clusters-for-kafka/how-to/manage-cluster.mdx +++ b/pages/clusters-for-kafka/how-to/manage-cluster.mdx @@ -14,7 +14,7 @@ Clusters for Apache Kafka® is currently in [Private Beta](https://www.scaleway. After creating your cluster, you can renew its TLS certificate, change the attached Private Network, and change its password. -Other management actions, such as creating topics and events, and configuring partitions and replication factors, must be carried out via TODO HOW. +Other management actions for internally configuring your cluster, such as creating topics and events, and configuring partitions and replication factors, can be carried out via a client library or Kafka CLI. diff --git a/pages/clusters-for-kafka/quickstart.mdx b/pages/clusters-for-kafka/quickstart.mdx index c821de750c..d662b51885 100644 --- a/pages/clusters-for-kafka/quickstart.mdx +++ b/pages/clusters-for-kafka/quickstart.mdx @@ -74,7 +74,7 @@ Configuration actions that cannot currently be carried out via the Scaleway cons - Configuring cluster parameters, such as replication factors, retention policies, and partitions - Integrating clients and consumers -These actions can be done via TODO HOW? +All such actions for internally configuring your cluster can be carried out via a client library or Kafka CLI. ## How to delete a cluster From 9df3fa734f2a1e38ba6b2664a02de25524ed1593 Mon Sep 17 00:00:00 2001 From: Rowena Date: Tue, 26 Aug 2025 11:50:29 +0200 Subject: [PATCH 08/14] =?UTF-8?q?fix(kafka):=20add=20supported=20details?= =?UTF-8?q?=C3=A9?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- pages/clusters-for-kafka/faq.mdx | 2 +- pages/clusters-for-kafka/how-to/connect-to-cluster.mdx | 2 +- pages/clusters-for-kafka/how-to/manage-cluster.mdx | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/clusters-for-kafka/faq.mdx b/pages/clusters-for-kafka/faq.mdx index 830ef86c6a..70a778fff4 100644 --- a/pages/clusters-for-kafka/faq.mdx +++ b/pages/clusters-for-kafka/faq.mdx @@ -20,7 +20,7 @@ Clusters for Apache Kafka® is Scaleway's product to provide a secure, fully-man ### How do I use my cluster, and how can I connect to it? -To use your cluster, you first [connect](/clusters-for-kafka/how-to/connect-to-cluster/) via the Kafka CLI or any supported programming language. The connection is secured, and requires the appropriate credentials, certificate, and endpoint provided by Scaleway. All configuration is done through a Kafka client, allowing you to manage topics, producers, and consumers easily. This flexibility ensures seamless integration with your applications and workflows. +To use your cluster, you first [connect](/clusters-for-kafka/how-to/connect-to-cluster/) via the Kafka CLI or any Kafka-supported programming language. The connection is secured, and requires the appropriate credentials, certificate, and endpoint provided by Scaleway. All configuration is done through a Kafka client, allowing you to manage topics, producers, and consumers easily. This flexibility ensures seamless integration with your applications and workflows. ### What limitations apply during the Private Beta? diff --git a/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx b/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx index 14c190fb6d..2c25ca2196 100644 --- a/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx +++ b/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx @@ -60,7 +60,7 @@ The username displays in the list of users. Click **Change password** if you hav ## How to connect to the cluster -Once you have ensured that the client in question has the cluster's TLS certificate, appropriate network access and the correct username and password, you can facilitate connection via the framework of your choice. Code snippets are provided for Go, Python and Java; access them by following the steps below. +Once you have ensured that the client in question has the cluster's TLS certificate, appropriate network access and the correct username and password, you can facilitate connection via the Kafka-compatible framework of your choice. Code snippets are provided for Go, Python and Java; access them by following the steps below. 1. Click **Apache Kafka®** in the **Data and Analytics** section of the [console](https://console.scaleway.com/) side menu. A list of your clusters displays. diff --git a/pages/clusters-for-kafka/how-to/manage-cluster.mdx b/pages/clusters-for-kafka/how-to/manage-cluster.mdx index a780c4d7f2..ac2de37330 100644 --- a/pages/clusters-for-kafka/how-to/manage-cluster.mdx +++ b/pages/clusters-for-kafka/how-to/manage-cluster.mdx @@ -14,7 +14,7 @@ Clusters for Apache Kafka® is currently in [Private Beta](https://www.scaleway. After creating your cluster, you can renew its TLS certificate, change the attached Private Network, and change its password. -Other management actions for internally configuring your cluster, such as creating topics and events, and configuring partitions and replication factors, can be carried out via a client library or Kafka CLI. +Other management actions for internally configuring your cluster, such as creating topics and events, and configuring partitions and replication factors, can be carried out via a Kafka-compatible client library or a Kafka CLI. From fb107da512d1daabf69fe296a16f1d9454d734c8 Mon Sep 17 00:00:00 2001 From: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> Date: Thu, 28 Aug 2025 11:14:13 +0200 Subject: [PATCH 09/14] Apply suggestions from code review --- pages/clusters-for-kafka/faq.mdx | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/pages/clusters-for-kafka/faq.mdx b/pages/clusters-for-kafka/faq.mdx index 70a778fff4..2613616ad3 100644 --- a/pages/clusters-for-kafka/faq.mdx +++ b/pages/clusters-for-kafka/faq.mdx @@ -33,7 +33,7 @@ Private Beta is aimed at providing an early version of a future product, to allo - Storage is fixed at 100 GB per node. - Connectivity to the cluster is facilitated exclusively through Private Networks. - Only one set of credentials (username and password) can be created per cluster. -- Each Scaleway Organization in the Private Beta may have a maximum of 5 clusters at one time (TODO CHECK) +- Each Scaleway Organization in the Private Beta may have a maximum of 5 clusters at one time We aim to improve and develop the product based on feedback received during the beta stage. @@ -57,6 +57,3 @@ Each system has its own strengths and is suited to different use cases depending Clusters for Apache Kafka® are free of charge during Private Beta, and you will not be billed. -### How will pricing work in the future? - -We anticipate that future pricing will be based on TODO. From 5a61dd801777a7d25974bf7a176822ce51b0dfc8 Mon Sep 17 00:00:00 2001 From: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> Date: Thu, 28 Aug 2025 11:31:36 +0200 Subject: [PATCH 10/14] Apply suggestions from code review Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com> Co-authored-by: Benedikt Rollik --- pages/clusters-for-kafka/concepts.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pages/clusters-for-kafka/concepts.mdx b/pages/clusters-for-kafka/concepts.mdx index 25ee14c8fd..348f166b48 100644 --- a/pages/clusters-for-kafka/concepts.mdx +++ b/pages/clusters-for-kafka/concepts.mdx @@ -22,7 +22,7 @@ Clusters for Apache Kafka® is Scaleway's product to provide a secure, fully-man ## Credentials -Credentials consist of a username and password that allow you to connect to your cluster. These are defined during cluster creation. During Private Beta, a limit of one user (ie one set of credentials) per cluster is applied. +Credentials consist of a username and password that allow you to connect to your cluster. These are defined during cluster creation. During Private Beta, a limit of one user (i.e. one set of credentials) per cluster is applied. ## Data replication @@ -30,15 +30,15 @@ Data replication is the mechanism that ensures event data is copied across multi ## Endpoint -During Private Beta, access to your Cluster for Apache Kafka® is via private endpoints only. When creating your cluster, you must attach it to a [Private Network](/vpc/concepts/#private-networks), and all nodes in the cluster receive a private IPv4 endpoint on this network. Endpoints are in a format similar to `bf610fb0-f7eb-4ec3-a893...634aea.Kafka.fr-par.scw.cloud`. +During Private Beta, access to your Cluster for Apache Kafka® is via private endpoints only. When creating your cluster, you must attach it to a [Private Network](/vpc/concepts/#private-networks), and all nodes in the cluster receive a private IPv4 endpoint on this network. Endpoints are in a format similar to `bf610fb0-f7eb-4ec3-a893...634aea.kafka.fr-par.scw.cloud`. ## Event streaming -Clusters for Apache Kafka® is specifically designed for implementing event streaming at scale. Event streaming is the process of capturing, storing and processing a continuous flow of events in real time. Each event represents something that happened,e.g.`User added item to cart`, `User clicked 'Pay now'`, `Payment was rejected by bank`. Events are stored in topics, e.g. `Inventory`, `Payment`, `Orders`. Typically, programs and microservices subscribe to these topics to consume their events and take action in relation to them, e.g. `Generate invoice`, `Check for fraud`, `Program delivery`. +Clusters for Apache Kafka® is specifically designed for implementing event streaming at scale. Event streaming is the process of capturing, storing and processing a continuous flow of events in real time. Each event represents something that happened, e.g.`User added item to cart`, `User clicked 'Pay now'`, `Payment was rejected by bank`. Events are stored in topics, e.g. `Inventory`, `Payment`, `Orders`. Typically, programs and microservices subscribe to these topics to consume their events and take action in relation to them, e.g. `Generate invoice`, `Check for fraud`, `Program delivery`. ## Node -A Cluster for Apache Kafka® consists of one or more nodes, also called **brokers**. Nodes work together to store, manage and distribute event streams. When creating a cluster, you can choose between **dedicated** nodes or **shared** nodes, based on your workload requirements, budget and use case: +A Cluster for Apache Kafka® consists of one or more nodes, also called **brokers**. Nodes work together to store, manage, and distribute event streams. When creating a cluster, you can choose between **dedicated** nodes or **shared** nodes, based on your workload requirements, budget, and use case: - **Dedicated node**: Runs only your cluster, with no other customers sharing the broker's resources. - **Shared node**: Runs your cluster along with other customers', on the same broker. From 7cbec3ff8822ae52d657fb71d195b59200d66ebc Mon Sep 17 00:00:00 2001 From: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> Date: Thu, 28 Aug 2025 11:32:49 +0200 Subject: [PATCH 11/14] Update pages/clusters-for-kafka/concepts.mdx --- pages/clusters-for-kafka/concepts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/clusters-for-kafka/concepts.mdx b/pages/clusters-for-kafka/concepts.mdx index 348f166b48..cadaa40bd7 100644 --- a/pages/clusters-for-kafka/concepts.mdx +++ b/pages/clusters-for-kafka/concepts.mdx @@ -45,7 +45,7 @@ A Cluster for Apache Kafka® consists of one or more nodes, also called **broker ## Storage -A cluster's storage is used to persist events, so they can be reliably consumed by services and applications. During Private Beta, each Cluster for Cluster for Apache Kafka® has a fixed amount of 100 GB of storage per node. +A cluster's storage is used to persist events, so they can be reliably consumed by services and applications. During Private Beta, each Cluster for Apache Kafka® has a fixed amount of 100 GB of storage per node. ## TLS certificate From 2518910bf0103fd452a44a77c75264490512f53a Mon Sep 17 00:00:00 2001 From: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> Date: Thu, 28 Aug 2025 11:59:42 +0200 Subject: [PATCH 12/14] Apply suggestions from code review Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com> --- pages/clusters-for-kafka/how-to/connect-to-cluster.mdx | 2 +- pages/clusters-for-kafka/how-to/delete-cluster.mdx | 2 +- pages/clusters-for-kafka/how-to/manage-cluster.mdx | 2 +- pages/clusters-for-kafka/index.mdx | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx b/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx index 2c25ca2196..5eade20100 100644 --- a/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx +++ b/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx @@ -1,6 +1,6 @@ --- title: How to connect to a Cluster for Apache Kafka® -description: Learn how to connect to your Scaleway Cluster for Apache Kafka® wih Scaleway, and understand how to securely establish a connection using TLS certificates and credentials. +description: Learn how to connect to your Scaleway Cluster for Apache Kafka® with Scaleway, and understand how to securely establish a connection using TLS certificates and credentials. dates: validation: 2025-08-20 posted: 2025-08-20 diff --git a/pages/clusters-for-kafka/how-to/delete-cluster.mdx b/pages/clusters-for-kafka/how-to/delete-cluster.mdx index b2a5539c15..a5c3b3fe08 100644 --- a/pages/clusters-for-kafka/how-to/delete-cluster.mdx +++ b/pages/clusters-for-kafka/how-to/delete-cluster.mdx @@ -1,6 +1,6 @@ --- title: How to delete to a Cluster for Apache Kafka® -description: Learn how to safely delete your Scaleway Cluster for Apache Kafka® wih Scaleway in just a few clicks. +description: Learn how to safely delete your Scaleway Cluster for Apache Kafka® with Scaleway in just a few clicks. dates: validation: 2025-08-20 posted: 2025-08-20 diff --git a/pages/clusters-for-kafka/how-to/manage-cluster.mdx b/pages/clusters-for-kafka/how-to/manage-cluster.mdx index ac2de37330..d357e8e544 100644 --- a/pages/clusters-for-kafka/how-to/manage-cluster.mdx +++ b/pages/clusters-for-kafka/how-to/manage-cluster.mdx @@ -1,6 +1,6 @@ --- title: How to manage to a Cluster for Apache Kafka® -description: Learn how to manage to your Scaleway Cluster for Apache Kafka® wih Scaleway, including editing its details, renewing its TLS certificate and more. +description: Learn how to manage to your Scaleway Cluster for Apache Kafka® with Scaleway, including editing its details, renewing its TLS certificate and more. dates: validation: 2025-08-20 posted: 2025-08-20 diff --git a/pages/clusters-for-kafka/index.mdx b/pages/clusters-for-kafka/index.mdx index 02f0674779..423c37c4a6 100644 --- a/pages/clusters-for-kafka/index.mdx +++ b/pages/clusters-for-kafka/index.mdx @@ -57,7 +57,7 @@ noindex: true From 6b3645f64eff8c13cabdcfa756838e4d09c3b74d Mon Sep 17 00:00:00 2001 From: nerda-codes Date: Mon, 15 Sep 2025 14:22:08 +0200 Subject: [PATCH 13/14] docs(fix): dates and typos --- pages/clusters-for-kafka/concepts.mdx | 6 +++--- pages/clusters-for-kafka/faq.mdx | 10 +++++----- pages/clusters-for-kafka/how-to/connect-to-cluster.mdx | 6 +++--- pages/clusters-for-kafka/how-to/create-cluster.mdx | 4 ++-- pages/clusters-for-kafka/how-to/delete-cluster.mdx | 4 ++-- pages/clusters-for-kafka/how-to/manage-cluster.mdx | 6 +++--- pages/clusters-for-kafka/index.mdx | 2 +- pages/clusters-for-kafka/quickstart.mdx | 8 ++++---- 8 files changed, 23 insertions(+), 23 deletions(-) diff --git a/pages/clusters-for-kafka/concepts.mdx b/pages/clusters-for-kafka/concepts.mdx index cadaa40bd7..08753cabf3 100644 --- a/pages/clusters-for-kafka/concepts.mdx +++ b/pages/clusters-for-kafka/concepts.mdx @@ -3,8 +3,8 @@ title: Clusters for Apache Kafka® - Concepts description: Understand the key concepts for Clusters for Apache Kafka®. tags: billing account pricing payment dates: - posted: 2025-08-20 - validation: 2025-08-20 + posted: 2025-09-15 + validation: 2025-09-15 noindex: true --- @@ -40,7 +40,7 @@ Clusters for Apache Kafka® is specifically designed for implementing event stre A Cluster for Apache Kafka® consists of one or more nodes, also called **brokers**. Nodes work together to store, manage, and distribute event streams. When creating a cluster, you can choose between **dedicated** nodes or **shared** nodes, based on your workload requirements, budget, and use case: -- **Dedicated node**: Runs only your cluster, with no other customers sharing the broker's resources. +- **Dedicated node**: Runs only your cluster, with no other customers sharing the broker's resources. - **Shared node**: Runs your cluster along with other customers', on the same broker. ## Storage diff --git a/pages/clusters-for-kafka/faq.mdx b/pages/clusters-for-kafka/faq.mdx index 2613616ad3..cb48c2c078 100644 --- a/pages/clusters-for-kafka/faq.mdx +++ b/pages/clusters-for-kafka/faq.mdx @@ -2,8 +2,8 @@ title: Clusters for Apache Kafka® FAQ description: Get answers to all your questions about Scaleway Clusters for Apache Kafka® dates: - validation: 2025-08-20 - posted: 2025-08-20 + validation: 2025-09-15 + posted: 2025-09-15 productIcon: KafkaProductIcon noindex: true --- @@ -33,17 +33,17 @@ Private Beta is aimed at providing an early version of a future product, to allo - Storage is fixed at 100 GB per node. - Connectivity to the cluster is facilitated exclusively through Private Networks. - Only one set of credentials (username and password) can be created per cluster. -- Each Scaleway Organization in the Private Beta may have a maximum of 5 clusters at one time +- Each Scaleway Organization in the Private Beta may have a maximum of 5 clusters at one time. We aim to improve and develop the product based on feedback received during the beta stage. -### Is Scaleway's Clusters for Apache Kafka® based on the open-source Kafka framework? +### Is Scaleway's Clusters for Apache Kafka® based on the open-source Kafka framework? Yes, Scaleway's Clusters for Apache Kafka is built on the open-source Apache Kafka framework. We use the Kafka API to ensure compatibility and leverage the robust features of the open-source ecosystem. ## How is Apache Kafka® different to RabbitMQ and NATS? -Apache Kafka, RabbitMQ, and NATS are all messaging systems but serve different purposes and have distinct architectures. +Apache Kafka, RabbitMQ, and NATS are all messaging systems but serve different purposes and have distinct architectures. - Apache Kafka is designed for high-throughput, real-time data streaming, and is topic-based, using the pull model. It can process large amounts of data in real-time with high concurrency and fault tolerance, and is ideal for stream processing, event sourcing, and big data applications. - RabbitMQ is a versatile message broker that supports multiple protocols, and offers strong support for message delivery guarantees and reliability. It uses the push model, and is well-suited for traditional message queuing and task distribution. diff --git a/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx b/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx index 5eade20100..86694c9899 100644 --- a/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx +++ b/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx @@ -2,8 +2,8 @@ title: How to connect to a Cluster for Apache Kafka® description: Learn how to connect to your Scaleway Cluster for Apache Kafka® with Scaleway, and understand how to securely establish a connection using TLS certificates and credentials. dates: - validation: 2025-08-20 - posted: 2025-08-20 + validation: 2025-09-15 + posted: 2025-09-15 noindex: true --- import Requirements from '@macros/iam/requirements.mdx' @@ -42,7 +42,7 @@ TLS is server-side only, and no client certificate is required. ## How to ensure clients have network access -Any clients wanting to connect to the cluster must be [attached to a Private Network](/vpc/how-to/attach-resources-to-pn/) in the same VPC as the cluster. +Any clients wanting to connect to the cluster must be [attached to a Private Network](/vpc/how-to/attach-resources-to-pn/) in the same VPC as the cluster. ## How to access the username and password diff --git a/pages/clusters-for-kafka/how-to/create-cluster.mdx b/pages/clusters-for-kafka/how-to/create-cluster.mdx index fdd9ad0cb6..739ea62762 100644 --- a/pages/clusters-for-kafka/how-to/create-cluster.mdx +++ b/pages/clusters-for-kafka/how-to/create-cluster.mdx @@ -2,8 +2,8 @@ title: How to create a Cluster for Apache Kafka® description: Learn how to create a Cluster for Apache Kafka® with Scaleway, and get your hosted, fully-managed Kafka infrastructure up and running with just a few clicks. dates: - validation: 2025-08-20 - posted: 2025-08-20 + validation: 2025-09-15 + posted: 2025-09-15 noindex: true --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/clusters-for-kafka/how-to/delete-cluster.mdx b/pages/clusters-for-kafka/how-to/delete-cluster.mdx index a5c3b3fe08..8e65414a74 100644 --- a/pages/clusters-for-kafka/how-to/delete-cluster.mdx +++ b/pages/clusters-for-kafka/how-to/delete-cluster.mdx @@ -2,8 +2,8 @@ title: How to delete to a Cluster for Apache Kafka® description: Learn how to safely delete your Scaleway Cluster for Apache Kafka® with Scaleway in just a few clicks. dates: - validation: 2025-08-20 - posted: 2025-08-20 + validation: 2025-09-15 + posted: 2025-09-15 noindex: true --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/clusters-for-kafka/how-to/manage-cluster.mdx b/pages/clusters-for-kafka/how-to/manage-cluster.mdx index d357e8e544..bb5f7aa9e1 100644 --- a/pages/clusters-for-kafka/how-to/manage-cluster.mdx +++ b/pages/clusters-for-kafka/how-to/manage-cluster.mdx @@ -2,8 +2,8 @@ title: How to manage to a Cluster for Apache Kafka® description: Learn how to manage to your Scaleway Cluster for Apache Kafka® with Scaleway, including editing its details, renewing its TLS certificate and more. dates: - validation: 2025-08-20 - posted: 2025-08-20 + validation: 2025-09-15 + posted: 2025-09-15 noindex: true --- import Requirements from '@macros/iam/requirements.mdx' @@ -46,7 +46,7 @@ In order to facilitate connectivity to your cluster, it must always be attached 2. Click the cluster whose certificate you want to renew. Its **Overview** page displays. -3. In the **Network** panel, click **Detach Private Network** +3. In the **Network** panel, click **Detach Private Network**. A pop-up displays, asking you to confirm the action. diff --git a/pages/clusters-for-kafka/index.mdx b/pages/clusters-for-kafka/index.mdx index 423c37c4a6..ab6edc9e8f 100644 --- a/pages/clusters-for-kafka/index.mdx +++ b/pages/clusters-for-kafka/index.mdx @@ -14,7 +14,7 @@ noindex: true + title="Clusters for Apache Kafka® is now in Private Beta"> This product is currently in [Private Beta](https://www.scaleway.com/en/betas/) and available to selected testers only. Watch this space to see how the product develops, or ask to join the beta for early access. diff --git a/pages/clusters-for-kafka/quickstart.mdx b/pages/clusters-for-kafka/quickstart.mdx index d662b51885..5eeb61ab9a 100644 --- a/pages/clusters-for-kafka/quickstart.mdx +++ b/pages/clusters-for-kafka/quickstart.mdx @@ -3,14 +3,14 @@ title: Clusters for Apache Kafka® - Quickstart description: Quickstart guide to setting up and managing Scaleway Clusters for Apache Kafka®. tags: cluster apache kafka dates: - validation: 2025-08-20 - posted: 2025-08-20 + validation: 2025-09-15 + posted: 2025-09-15 noindex: true --- import Requirements from '@macros/iam/requirements.mdx' -Clusters for Apache Kafka® is currently in [Private Beta](https://www.scaleway.com/en/betas/) and available to selected testers only. + Clusters for Apache Kafka® is currently in [Private Beta](https://www.scaleway.com/en/betas/) and available to selected testers only. Clusters for Apache Kafka® is Scaleway's product to provide a secure, fully-managed infrastructure for your Apache Kafka® deployments. With our clusters, you can create data pipelines and event-driven architectures that run natively on Apache Kafka®, without having to manage the underlying infrastructure. @@ -50,7 +50,7 @@ Your cluster is created, and you are taken to its **Overview** page in the conso All clients that want to connect to your cluster must: -- Have downloaded the cluster's [TLS certificate](/clusters-for-kafka/how-to/manage-cluster/) and configured the client to recognize it. +- Have downloaded the cluster's [TLS certificate](/clusters-for-kafka/how-to/manage-cluster/) and configured the client to recognize it - Be [attached to a Private Network](/vpc/how-to/attach-resources-to-pn/) in the same VPC as the cluster, or connect via a [Public Gateway](/public-gateways/how-to/create-a-public-gateway/) in the VPC - Know the cluster's [username and password](/clusters-for-kafka/how-to/connect-to-cluster/#how-to-access-the-username-and-password) From 56fa8a5c5dba03501674abdb69bdd6b7d1a6efd7 Mon Sep 17 00:00:00 2001 From: nerda-codes Date: Mon, 15 Sep 2025 15:45:14 +0200 Subject: [PATCH 14/14] docs(add): faq question & frameworks --- pages/clusters-for-kafka/faq.mdx | 7 ++++--- pages/clusters-for-kafka/how-to/connect-to-cluster.mdx | 5 +++-- pages/clusters-for-kafka/quickstart.mdx | 2 +- 3 files changed, 8 insertions(+), 6 deletions(-) diff --git a/pages/clusters-for-kafka/faq.mdx b/pages/clusters-for-kafka/faq.mdx index cb48c2c078..deb1acae4e 100644 --- a/pages/clusters-for-kafka/faq.mdx +++ b/pages/clusters-for-kafka/faq.mdx @@ -39,15 +39,15 @@ We aim to improve and develop the product based on feedback received during the ### Is Scaleway's Clusters for Apache Kafka® based on the open-source Kafka framework? -Yes, Scaleway's Clusters for Apache Kafka is built on the open-source Apache Kafka framework. We use the Kafka API to ensure compatibility and leverage the robust features of the open-source ecosystem. +Yes, Scaleway's Clusters for Apache Kafka is built on the open-source Apache Kafka framework. We use the Kafka API to ensure compatibility and leverage the robust features of the open-source ecosystem. ## How is Apache Kafka® different to RabbitMQ and NATS? Apache Kafka, RabbitMQ, and NATS are all messaging systems but serve different purposes and have distinct architectures. - Apache Kafka is designed for high-throughput, real-time data streaming, and is topic-based, using the pull model. It can process large amounts of data in real-time with high concurrency and fault tolerance, and is ideal for stream processing, event sourcing, and big data applications. -- RabbitMQ is a versatile message broker that supports multiple protocols, and offers strong support for message delivery guarantees and reliability. It uses the push model, and is well-suited for traditional message queuing and task distribution. -- [NATS](/nats/) is a lightweight, high-performance subject-based messaging system focused on speed and simplicity, making it great for microservices. +- RabbitMQ is a versatile message broker that supports multiple protocols, and offers strong support for message delivery guarantees and reliability. It uses the push model, and is well-suited for traditional message queuing and task distribution. +- [NATS](/nats/) is a lightweight, high-performance subject-based messaging system focused on speed and simplicity, making it great for microservices. Each system has its own strengths and is suited to different use cases depending on the requirements of the application. @@ -56,4 +56,5 @@ Each system has its own strengths and is suited to different use cases depending ### How am I billed for Clusters for Apache Kafka®? Clusters for Apache Kafka® are free of charge during Private Beta, and you will not be billed. +After the Private Beta, we are considering a usage-based pricing model that will be competitive with current market offerings. diff --git a/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx b/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx index 86694c9899..e83a0113c9 100644 --- a/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx +++ b/pages/clusters-for-kafka/how-to/connect-to-cluster.mdx @@ -68,6 +68,7 @@ Once you have ensured that the client in question has the cluster's TLS certific 3. In the **Connectivity** panel, click **Connect**. - A pop-up displays, with tabs for each sample framework: **Go**, **Python** and **Java**. + A pop-up displays, with tabs for each sample framework: **Go**, **Python**, **Java**, **Node.js**, and **Mongoose**. + +4. Click the tab of your choice to view the code sample. -4. Click the tab of your choice to view the code sample. \ No newline at end of file diff --git a/pages/clusters-for-kafka/quickstart.mdx b/pages/clusters-for-kafka/quickstart.mdx index 5eeb61ab9a..2e6bcdb8b0 100644 --- a/pages/clusters-for-kafka/quickstart.mdx +++ b/pages/clusters-for-kafka/quickstart.mdx @@ -62,7 +62,7 @@ Once you have ensured the client satisfies the conditions above, you can facilit 3. In the **Connectivity** panel, click **Connect**. - A pop-up displays, with tabs for each sample framework: **Go**, **Python** and **Java**. + A pop-up displays, with tabs for each sample framework: **Go**, **Python**, **Java**, **Node.js**, and **Mongoose**. 4. Click the tab of your choice to view the code sample.