flink-jobs

Deploy Flink CDC pipelines from MySQL to StarRocks on Kubernetes via Helm charts.

Updated Dec 3, 2025
One-click install
npx skills add https://github.com/grey8848/infra-gitops --skill flink-jobs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flink-jobs
Source: https://github.com/grey8848/infra-gitops/tree/main/charts/flink-jobs
Command: npx skills add https://github.com/grey8848/infra-gitops --skill flink-jobs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to deploy and manage Flink CDC pipelines that synchronize data from MySQL into StarRocks, providing near real-time analytics with minimal manual orchestration.

Core Features & Use Cases

  • CDC-driven data replication: MySQL to StarRocks synchronization using FlinkDeployment.
  • Kubernetes-ready Helm templates: Simple deployment via Helm charts under charts/flink-jobs.
  • Use Case: Set up a development environment to continuously replicate customer data from a MySQL source into StarRocks for analytics dashboards.

Quick Start

Use Helm to enable CDC and deploy the Flink CDC pipeline:

  • set cdc.enabled: true in values.yaml
  • customize mysql and starrocks connection parameters
  • run helm upgrade --install flink-jobs ./charts/flink-jobs

Frequently Asked Questions about flink-jobs

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

FAQPage Schema
How do I deploy a Flink CDC pipeline to synchronize MySQL data into StarRocks on Kubernetes?

You can deploy a Flink CDC pipeline by using Helm charts to configure a FlinkDeployment, which automates MySQL to StarRocks synchronization. Set cdc.enabled to true in values.yaml, define the connection parameters, and run helm upgrade to generate the Kubernetes resources.

Can I toggle CDC on or off when deploying Flink jobs with Helm?

Yes, you can toggle CDC on or off by setting the cdc.enabled parameter in values.yaml. This allows you to control whether the FlinkDeployment enables the MySQL to StarRocks data pipeline during Helm deployment across development or production clusters.

Does this Helm-based Flink CDC deployment require manual Kubernetes resource creation?

No, it does not require manual Kubernetes resource creation. The Helm-driven workflow automatically generates the necessary Kubernetes resources for the FlinkDeployment based on your customized MySQL and StarRocks connection parameters in values.yaml.

What connection parameters do I need to configure for a MySQL to StarRocks Flink CDC pipeline?

You need to define MySQL and StarRocks connection parameters in the values.yaml file. These parameters configure the FlinkDeployment to establish the CDC-driven data replication pipeline from the MySQL source into StarRocks for near real-time analytics.

Is a Helm chart the best way to manage Flink CDC pipelines across multiple Kubernetes clusters?

Using a Helm chart is an effective way to manage Flink CDC pipelines across development and production Kubernetes clusters. It provides simple deployment templates and allows you to consistently toggle CDC features and define connection parameters for MySQL to StarRocks synchronization.

Why use FlinkDeployment for MySQL to StarRocks CDC instead of other data pipeline approaches?

FlinkDeployment provides near real-time analytics with minimal manual orchestration by automating CDC-driven data replication from MySQL into StarRocks. Deploying it via Helm on Kubernetes standardizes the pipeline configuration across different cluster environments.