For AI agents: the complete documentation index is available at https://docs.us.ovhcloud.com/en/llms.txt, the full documentation bundle is available at https://docs.us.ovhcloud.com/en/llms-full.txt, and this page is available as Markdown at https://docs.us.ovhcloud.com/en/public-cloud/data-analytics/kafka-connect-capabilities-limitations.md.
  • English

Kafka® Connect - Capabilities and limitations

View as Markdown

This page provides the technical capabilities and limitations of the Cloud Analytics with Kafka® Connect offer.

We continuously improve our offers. You can follow and submit ideas to add to our roadmap.

 

Capabilities and limitations

Supported regions

To view Cloud Analytics availability, please see our regions and availability webpage.

Entire analytics instances have to be in the same region.

 

Kafka® Connect versions

The following Kafka Connect versions are supported:

  • Kafka® Connect 3.8
  • Kafka® Connect 3.9

Please refer to the Lifecycle policy guide for recommendations on version upgrades and end of life announcements of major versions.

 

Plans

Three plans are available:

  • Essential
  • Business
  • Enterprise

Here is an overview of the various plans' capabilities:

PlanNumber of nodesAdditional nodes
Essential1No
Business3No
Enterprise6No

Your choice affects the number of nodes your cluster runs or the SLA.

Info

Be aware that you will be able to upgrade your plan, but you won't be able to downgrade it afterward.

 

Nodes

  • Essential: the cluster consists of one node.
  • Business: the cluster is delivered with 3 nodes.
  • Enterprise: the cluster is delivered with 6 nodes.

 

Hardware resources

For more information about node types and their specifications, see our pricing page.

 

Features

Network

Public as well as private networking (vRack) can be used for all the offers.

Ingress and Egress traffic are included in the service plans and are unmetered.

The Analytics service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.

Private network considerations

Here are some considerations to take into account when using a private network:

  • Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g., you won’t be able to delete the network if you didn’t stop the Cloud Analytics services first.
  • When connecting from an outside subnet, the OpenStack IP gateway must be enabled in the subnet used for the Analytics service. The customer is responsible for any other custom network setup.
  • Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
  • OpenStack subnet routes announcement will not be applied to your services.
  • You can only create private network services if you are the original owner of the network. You cannot create private network services on a shared network.
Authorized IPs

Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorize incoming traffic. Until then, your service will be unreachable.

 

Advanced parameters

You can further customize your Kafka® Connect by using advanced parameters. See our Kafka® Connect - Advanced parameters references guide for more information on the supported parameters.

 

Logs and metrics

Logs and metrics are available through the Control Panel and the API. Additionally, cross-service integration can be configured to leverage your logs and metrics in other Cloud Databases and Analytics services. You could then view your Kafka® Connect logs in OpenSearch™ and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL®). See our Set up a service integration guide for more information.

  • Logs retention: 1000 lines of logs
  • Metrics retention: 1 calendar month

Please note that if the cluster is deleted, logs and metrics are also automatically deleted.

 

Data encryption

For detailed information about encryption, see our Security Overview guide.

 

Go further

Browse all the Analytics guides.

Browse the rest of the OVHcloud US documentation for guides on our other products and services.

Learn more about Cloud Analytics on the OVHcloud US website.

OVHcloud Managed Databases and Analytics:

  • Grafana® is a registered trademark of Grafana Labs and is used with the permission of Grafana Labs. OVH SAS and its subsidiaries are not affiliated with or endorsed by Grafana Labs.
  • Kafka® is a registered trademark of The Apache Software Foundation and has been licensed for use by OVHcloud, who has no affiliation with and is not endorsed by The Apache Software Foundation.
  • MongoDB® is a registered trademark of MongoDB, Inc.
  • MySQL® is a registered trademark of Oracle and/or its affiliates.
  • PostgreSQL® is a registered trademark of the PostgreSQL Community Association of Canada.