Connections
A Gateway Group's card shows how many Kafka clusters and API Products it's connected to, a quick signal of how much traffic depends on it before you edit or upgrade it.
Connected Clusters
A Kafka cluster becomes bound to a Gateway Group when an API Product published to that group is backed by it. Attaching a cluster to the environment makes it available; publishing a product against it is what binds it. Open the Gateway Group's Clusters tab to see every bound cluster, along with its region, broker and topic counts, traffic, and health status, plus a count and a roll-up of whether all of them are healthy. A cluster carved out of a physical one is marked Virtual.
The tab reads the group's published products to decide what's bound, so a cluster attached to the environment but not yet backing any published product shows as No clusters attached yet.
Connected Products
An API Product is connected to a Gateway Group once it's published to a server the group serves. A single Gateway Group commonly serves multiple API Products at once, each addressed by its own hostname alias. The Gateway Group's card shows how many products it currently serves; to see which ones, check each product's own Publishing tab.
Next Steps
- Configuration covers viewing the resolved routing that backs these connections.
- API Products covers publishing a product to a Gateway.