You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(konnect): Rename: Gateway Manager and AI Manager to API Gateway and AI Gateway (#2975)
* rename Gateway Manager and AI Manager to regular product names
* breadcrumbs and index link
* fix(indices): liquid variables in titles
* fix(indices): items have `title` not `text`
* change all the URLs
---------
Co-authored-by: Fabian Rodriguez <[email protected]>
- text: "{{site.konnect_short_name}} control plane resource limits"
29
+
url: /gateway/control-plane-resource-limits/
30
30
31
31
faqs:
32
32
- q: What are credentials, and why do I need them?
@@ -167,29 +167,29 @@ rows:
167
167
168
168
## Centrally-managed Consumers {% new_in 3.10 %}
169
169
170
-
Consumers can be scoped to a {{site.konnect_short_name}} region and managed centrally, or be scoped to a Control Plane in Gateway Manager.
170
+
Consumers can be scoped to a {{site.konnect_short_name}} region and managed centrally, or be scoped to a control plane.
171
171
172
172
Centralized Consumer management provides the following benefits:
173
-
***Set up a Consumer identity centrally**: Only define a Consumer once, instead of defining it in multiple Control Planes.
174
-
***Avoid conflicts from duplicate Consumer configuration**: Users don't need to replicate changes to Consumer identity in multiple Control Planes and Consumer configuration doesn't conflict.
175
-
***Reduce configuration sync issues between the Control Plane and the Data Planes**: Consumers that are managed centrally aren't part of the configuration that is pushed down from the Control Plane to the Data Planes, so it reduces config size and latency.
173
+
***Set up a Consumer identity centrally**: Only define a Consumer once, instead of defining it in multiple control planes.
174
+
***Avoid conflicts from duplicate Consumer configuration**: Users don't need to replicate changes to Consumer identity in multiple control planes and Consumer configuration doesn't conflict.
175
+
***Reduce configuration sync issues between the control plane and the data planes**: Consumers that are managed centrally aren't part of the configuration that is pushed down from the control plane to the data planes, so it reduces config size and latency.
176
176
177
-
Centrally managed Consumers exist outside of Control Planes, so they can be used across Control Planes.
177
+
Centrally managed Consumers exist outside of control planes, so they can be used across control planes.
178
178
179
-
Use the following table to help you determine if you should use centrally-managed Consumers or Consumers scoped to Control Planes:
179
+
Use the following table to help you determine if you should use centrally-managed Consumers or Consumers scoped to control planes:
180
180
181
181
<!--vale off-->
182
182
{% feature_table %}
183
183
columns:
184
184
- title: "Centrally-managed Consumers"
185
185
key: central
186
186
center: true
187
-
- title: Control Plane scoped Consumer
187
+
- title: Control plane scoped Consumer
188
188
key: cp_consumer
189
189
center: true
190
190
191
191
features:
192
-
- title: "Share Consumer identity in more than one Control Plane"
192
+
- title: "Share Consumer identity in more than one control plane"
193
193
central: true
194
194
cp_consumer: false
195
195
- title: "Supported authentication strategies"
@@ -205,15 +205,15 @@ features:
205
205
<!--vale on-->
206
206
207
207
You can manage Consumers centrally using the [{{site.konnect_short_name}} Consumers API](/api/konnect/consumers/v1/).
208
-
Only Org Admins and Control Plane Admins have CRUD permissions for these Consumers.
208
+
Only Org Admins and control plane Admins have CRUD permissions for these Consumers.
209
209
210
210
When you create a Consumer centrally, you must assign it to a realm. A realm groups Consumers around an identity, defined by organizational boundaries, such as a production realm or a development realm.
211
211
Realms are connected to a [geographic region](/konnect-platform/geos/) in {{site.konnect_short_name}}. Additionally, centrally managed Consumers must have a [specific Key Authentication configuration](/plugins/key-auth/examples/identity-realms/) set up to allow these Consumers to authenticate.
212
212
213
213
For a complete tutorial, see [Create a centrally-managed Consumer in {{site.konnect_short_name}}](/how-to/create-centrally-managed-consumer/).
214
214
215
215
{:.info}
216
-
> **Note:** If you are using KIC to manage your Data Plane nodes in {{site.konnect_short_name}}, ensure that you configure the [`cluster_telemetry_endpoint`](/gateway/configuration/#cluster-telemetry-endpoint)in the Data Plane. You can find your specific `cluster_telemetry_endpoint`in [Gateway Manager](https://cloud.konghq.com/gateway-manager/), in the Data Plane node setup instructions.
216
+
> **Note:** If you are using KIC to manage your data plane nodes in {{site.konnect_short_name}}, ensure that you configure the [`cluster_telemetry_endpoint`](/gateway/configuration/#cluster-telemetry-endpoint) in the data plane. You can find your specific `cluster_telemetry_endpoint`when setting up a data plane node.
0 commit comments