Manage Flink With Confluent for Kubernetes
You can use Confluent for Kubernetes (CFK) to declaratively manage the Apache Flink® lifecycle in Kubernetes through custom resources (CRs) that CFK reconciles with Confluent Manager for Apache Flink (CMF). This includes environments, applications, and Flink SQL objects.
CFK provides the following Flink custom resources:
CMFRestClassThe connection that every Flink CR uses to reach CMF. Only CFK uses this resource; it is not part of CMF.
FlinkEnvironmentA set of configurations that Flink applications and SQL statements share.
FlinkApplicationA packaged Flink program, such as a JAR or container image that contains compiled DataStream or Table API code.
FlinkComputePoolThe compute that runs SQL statements, either
DEDICATEDorSHARED.FlinkStatementA single Flink SQL statement that runs as a streaming job.
FlinkKafkaCatalogBinds a Schema Registry instance for the databases in the catalog.
FlinkKafkaDatabaseA SQL database in a catalog, mapped to a Kafka cluster.
FlinkSecretSyncs a Kubernetes Secret that holds Kafka or Schema Registry credentials to CMF.
FlinkEnvironmentSecretMappingExposes a synced secret to an environment so that catalogs and databases can reference it.
Note
Flink SQL support through CFK is a preview feature in CFK 3.3.0 and requires CMF 2.3.0 or later. Do not use preview features in production.
For the requirements and the end-to-end steps to manage Flink on-premises with CFK, see the following operator documentation:
