Source compatibility¶
KCP supports two source types - AWS MSK and Apache Kafka® - and not every command supports every source flavour today. This page is the authoritative quick-lookup for which kcp subcommands work against which source.
Tip
Looking for how a command works? See the Command Reference. This page covers whether it works for your source.
Source flavors¶
- MSK Provisioned / Express — AWS MSK provisioned clusters (including MSK Express brokers).
- MSK Serverless — AWS MSK Serverless clusters.
- Apache Kafka — Any Kafka API compatible source, reached via the Kafka Admin API.
Legend¶
| Marker | Meaning |
|---|---|
| Yes | Fully supported. |
| Limited | Partial support — see the inline note on the row for what's missing. |
| No | Not supported. |
| Coming | Planned for an upcoming release. |
| AWS only | Supported when the Apache Kafka source is hosted on AWS; the generated infrastructure assumes AWS networking. |
| N/A | Command is source-agnostic; the source type does not apply. |
Compatibility matrix¶
| Command | MSK Provisioned/Express | MSK Serverless | Apache Kafka |
|---|---|---|---|
kcp discover |
Yes | Limited (some resources not discoverable for Serverless) | No |
kcp scan client-inventory |
Yes | No | No |
kcp scan clusters |
Yes | No | Yes |
kcp scan msk-connectors |
Yes (pass --metrics-granularity to also pull per-connector CloudWatch metrics) |
Limited (only if MSK Connect connectors target the cluster) | No |
kcp scan schema-registry |
Yes | Yes | Yes |
kcp create-asset bastion-host |
N/A | N/A | N/A |
kcp create-asset migrate-acls iam |
Yes | Limited (manual IAM user/role mapping) | No |
kcp create-asset migrate-acls kafka |
Yes | No | Yes |
kcp create-asset migrate-connectors connector-utility |
Yes | Yes | Yes |
kcp create-asset migrate-connectors msk |
Yes | Yes | Yes |
kcp create-asset migrate-connectors self-managed |
Yes | No | Yes |
kcp create-asset migrate-schemas |
Yes | Yes | Yes |
kcp create-asset migrate-topics |
Yes | No | Yes |
kcp create-asset migration-infra - Type 1 |
Yes | N/A | AWS only |
kcp create-asset migration-infra - Type 2 |
Yes | N/A | AWS only |
kcp create-asset migration-infra - Type 3 |
Yes | N/A | AWS only |
kcp create-asset migration-infra - Type 4 |
Yes | N/A | AWS only |
kcp create-asset migration-infra - Type 5 |
Yes | Yes | AWS only - Requires IAM JAR |
kcp create-asset target-infra |
N/A | N/A | N/A |
kcp migration init |
Yes | No | Yes |
kcp migration lag-check |
Yes | No | Yes |
kcp migration execute |
Yes | No | Yes |
kcp migration list |
Yes | No | Yes |
kcp ui |
Yes | No | Yes |
Consumer group discovery¶
kcp scan clusters discovers consumer groups by default (disable with --skip-consumer-groups). Support mirrors the kcp scan clusters row above: available for MSK Provisioned/Express and Apache Kafka, and not for MSK Serverless (no Kafka Admin API).
For every group KCP records its id, state, coordinator, and type. The type is the group's KIP-848 protocol, and which types a cluster can report depends on its Kafka version:
| Group type | Introduced | Notes |
|---|---|---|
classic |
all versions | The original consumer-group protocol. Fully described. |
consumer |
Kafka 4.0 (KIP-848) | New consumer rebalance protocol. |
share |
Kafka 4.1 (KIP-932) | Share groups; requires group.share.enable on the broker. |
streams |
Kafka 4.2 (KIP-1071) | Kafka Streams groups. |
Note
Reading the group type requires a broker running Kafka 3.8 or newer (the ListGroups v5 API). Against older brokers the type is reported as blank and every group is treated as classic-protocol.
Important
Only classic groups are fully described — their members and per-member topic assignments are captured. consumer, share, and streams groups record their type, state, and coordinator but not member-level detail (that requires the newer ConsumerGroupDescribe API, which KCP does not yet call). Such groups are flagged with incomplete detail in kcp-state.json and marked "partial" in the UI's Consumer Groups tab.
Confluent Cloud destination¶
The matrix above describes source support. Independently, three create-asset commands require a --cc-type declaration naming the Confluent Cloud destination — commercial (Standard) or government (Confluent Cloud for Government):
kcp create-asset migration-infrakcp create-asset migrate-topicskcp create-asset migrate-schemas
The declaration is required on these three commands (there is no default). It is not accepted on any other command.
Confluent Cloud for Government does not provide Cluster Linking or Schema Linking, so the linking-based paths are refused before any Terraform is generated when --cc-type government is declared:
| Path | commercial (Standard) |
government (Government) |
|---|---|---|
migration-infra (all --type values) |
Supported | Refused — relies on Cluster Linking |
migrate-topics --mode mirror |
Supported | Refused — use --mode new instead |
migrate-topics --mode new |
Supported | Supported |
migrate-schemas --url (Schema Exporter) |
Supported | Refused — use --glue-registry instead |
migrate-schemas --glue-registry |
Supported | Supported |
If a row here doesn't match what you're seeing in practice, please open an issue.