redpanda-migrator

Generate Redpanda Migrator YAML configurations for Kafka-compatible cluster migrations.

1|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/ajurcenk/claude_code_redpanda_migrator_cfg_gen_agent_skiils --skill redpanda-migrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redpanda-migrator
Source: https://github.com/ajurcenk/claude_code_redpanda_migrator_cfg_gen_agent_skiils/tree/main/redpanda-migrator
Command: npx skills add https://github.com/ajurcenk/claude_code_redpanda_migrator_cfg_gen_agent_skiils --skill redpanda-migrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill removes the manual effort and guesswork of creating correct Redpanda Migrator YAML files by asking targeted questions, applying safe defaults, and producing validated, deployment-ready configurations for complex Kafka-compatible migrations.

Core Features & Use Cases

  • Migration Scope: Covers data migration, schema registry synchronization, consumer offset translation, and ACL migration across Apache Kafka, Redpanda, Confluent Cloud, AWS MSK, Azure Event Hubs, and other Kafka-compatible systems.
  • Security & Deployment Awareness: Automatically advises and formats secret usage for Redpanda Cloud/Serverless, supports SASL (PLAIN, SCRAM), AWS IAM, TLS/mTLS, and enforces serverless-specific flags.
  • Policy & Validation: Provides topic and schema filtering, replication factor overrides, serverless mode checks, and a validation script to verify required fields and warn about configuration pitfalls.
  • Use Case Example: Produce a YAML that migrates topics and schemas from Confluent Cloud to Redpanda Cloud while preserving consumer offsets and applying secret references for cloud deployment.

Quick Start

Ask the assistant to "Generate a Redpanda Migrator YAML to migrate data, schemas, consumer offsets, and ACLs from Confluent Cloud to Redpanda Cloud with secrets and SCRAM authentication."

Frequently Asked Questions about redpanda-migrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a Redpanda Migrator YAML configuration for migrating Kafka topics?

Yes, you can migrate schemas and consumer offsets from Confluent Cloud to Redpanda Cloud by generating a YAML configuration that specifies both clusters. The skill handles schema registry synchronization, consumer offset translation, and formats secret references correctly for cloud deployments.

Does the Redpanda Migrator support AWS MSK and Azure Event Hubs as source clusters?

Yes, the Redpanda Migrator supports AWS MSK and Azure Event Hubs as source clusters for data, schema, offset, and ACL migrations. It generates YAML configurations that apply necessary serverless flags, replication factor overrides, and required AWS IAM or SASL authentication parameters.

What is the best way to handle secrets when migrating data to Redpanda Serverless?

The best way to handle secrets when migrating to Redpanda Serverless is to use the generated YAML configuration which automatically formats and advises secret usage for cloud deployments. The skill ensures correct secret handling and enforces serverless-specific validation checks for your migration.

How do I apply topic and schema filtering during a Kafka to Redpanda data migration?

You apply topic and schema filtering by defining the specific filter criteria within the generated Redpanda Migrator YAML configuration. The skill includes these policy parameters to restrict the migration scope and validates the resulting file to warn about potential configuration pitfalls.

Why does my consumer offset migration require specific serverless flags for Redpanda Cloud?

Consumer offset migration requires specific serverless flags because Redpanda Serverless enforces distinct cluster constraints and security policies. The skill automatically enforces these serverless mode checks and validation rules to ensure your YAML configuration aligns with the destination environment.