ticdc-next-gen-deploy

Deploy and destroy TiCDC next-gen test stacks via SSH with TiUP.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/alex-quan-001/nutshell-skills --skill ticdc-next-gen-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticdc-next-gen-deploy
Source: https://github.com/alex-quan-001/nutshell-skills/tree/main/skills/ops/ticdc-next-gen-deploy
Command: npx skills add https://github.com/alex-quan-001/nutshell-skills --skill ticdc-next-gen-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tiup, minio, mc, ssh, curl, wget, and includes scripts (resource) components.

What problem does it solve?

Manually setting up TiCDC next-gen test stacks requires dozens of error-prone steps including TiUP cluster deployment, binary patching, MinIO setup, keyspace TiDB instance configuration, and optional changefeed creation, all of which this skill automates via SSH-based remote execution.

Core Features & Use Cases

  • Automated SSH-based Deployment: Remotely deploy TiUP-managed TiDB clusters with custom patch binaries for TiKV, TiDB, PD, and CDC on a target host with a single command.
  • Configurable Keyspace Support: Launch a custom number of keyspace-specific TiDB instances with auto-generated topo configurations that include required monitoring and Grafana sections.
  • Optional Changefeed Creation: Automatically create TiCDC changefeeds with auto-resolved sink URIs from deployed keyspace instances, plus full teardown of all deployed components when testing is complete.
  • Use Case: TiDB Cloud engineers testing TiCDC new-architecture features can use this skill to spin up and tear down isolated test environments in minutes instead of hours of manual work.

Quick Start

Ask your AI agent to use the ticdc-next-gen-deploy skill to deploy a 2-keyspace TiCDC next-gen test stack on host 10.2.7.6 with patch files in /root, and create a changefeed from keyspace 1 to keyspace 2 with ID test-sink.

Frequently Asked Questions about ticdc-next-gen-deploy

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

FAQPage Schema
How do I automate TiUP cluster deployment for TiCDC testing with custom patch binaries?

Automate TiUP cluster deployment for TiCDC testing by running SSH-based remote execution scripts that deploy TiDB clusters with custom patch binaries for TiKV, TiDB, PD, and CDC, replacing manual multi-step setup.

What's the best way to configure multiple keyspace TiDB instances for TiCDC next-gen feature testing?

The best way to configure keyspace TiDB instances for TiCDC testing is using automated topo generation scripts that launch a custom number of keyspace-specific TiDB instances with required monitoring and Grafana sections included.

Does this TiCDC test stack deployment support automatic changefeed creation between keyspaces?

Yes, this TiCDC test stack deployment supports automatic changefeed creation by auto-resolving sink URIs from deployed keyspace instances, allowing you to create a changefeed from one keyspace to another.

Do I need SSH access and MinIO to deploy a TiCDC next-gen test stack?

Yes, you need SSH access for remote execution and MinIO for storage when deploying a TiCDC next-gen test stack, along with dependencies like tiup, mc, curl, and wget for automated installation.

Can I safely tear down all deployed TiCDC test resources after completing feature testing?

Yes, you can safely tear down all deployed TiCDC test resources, as the deployment automation includes full destruction of all deployed components, ensuring clean removal of test environments.

Why does manually setting up TiCDC next-gen test stacks require automation?

Manually setting up TiCDC next-gen test stacks requires automation because it involves dozens of error-prone steps including TiUP deployment, binary patching, MinIO setup, and keyspace configuration that cause significant overhead.