Home / Companies / Confluent / Blog / Post Details
Content Deep Dive

The Last (and Longest) Mile of Apache Kafka® Migrations: Client Migrations With KCP and Confluent Cloud Gateway

Blog post from Confluent

Post Details
Company
Date Published
Author
David Marsh Senior
Word Count
2,374
Company Posts That Month
3
Language
English
Hacker News Points
-
Post removed?
No
Summary

Kafka Copy Paste (KCP), an open-source CLI tool, has been enhanced with Confluent Cloud Gateway support to fully automate the migration of Apache Kafka environments to Confluent Cloud, significantly reducing the time and complexity involved. Previously, while KCP could automate the discovery, provisioning, and data migration, the client migration phase required extensive manual coordination and posed significant challenges, such as coordinating across teams, managing authentication differences, and offset management. The integration with Gateway now allows KCP to handle client migration seamlessly by acting as a Kafka proxy, enabling client traffic to be rerouted without client-side changes. This includes transparent authentication translation, incremental group-based migrations, and rollback capabilities, thereby transforming a process that traditionally took weeks into a matter of hours. The migration process is divided into four stages: deploying Gateway, planning migration groups, onboarding clients to Gateway, and executing group-by-group migration using a series of CLI commands. This approach minimizes downtime and coordination overhead, offering a predictable, incremental, and low-risk migration pathway, making client migration efficient and straightforward.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Real-time 5 6,296 1,346 246 -2%
Secrets Management 3 1,821 338 111 +22%
Vector Search 2 1,739 413 146 -27%
Kubernetes 1 2,306 381 103 +25%
MCP 1 6,108 613 170 +36%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.