Skip to content

align API Gateway definition with CNCF Glossary #3653

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 5, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 12 additions & 13 deletions site-src/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,23 +66,22 @@ Guide](/guides/tls) for more details about passthrough and other TLS
configurations.

#### What's the difference between Gateway API and an API Gateway?
An API Gateway is a general concept that describes anything that exposes
capabilities of a backend service, while providing extra capabilities for
traffic routing and manipulation, such as load balancing, request and response
transformation, and sometimes more advanced features like authentication and
authorization, rate limiting, and circuit breaking.
An [API gateway](https://glossary.cncf.io/api-gateway/) is a tool that
aggregates unique application APIs, making them all available in one place.
It allows organizations to move key functions, such as authentication and
authorization or limiting the number of requests between applications, to a
centrally managed location. An API gateway functions as a common interface to (often external) API consumers.

Gateway API is an interface, or set of resources, that model service networking
in Kubernetes. One of the main resources is a `Gateway`, which declares the
Gateway type (or class) to instantiate and its configuration. As a Gateway
Provider, you can implement Gateway API to model Kubernetes service networking
in an expressive, extensible, and role-oriented way.
Gateway API is an interface, defined as a set of Kubernetes resources, that
models service networking in Kubernetes. One of the main resources is a `Gateway`,
which declares the Gateway type (or class) to instantiate and its configuration.
As a Gateway provider, you can implement Gateway API to model Kubernetes service
networking in an expressive, extensible, and role-oriented way.

Most Gateway API implementations are API Gateways to some extent, but not all
API Gateways are Gateway API implementations.
Some API gateways can be programmed using the Gateway API.

#### Is Gateway API a standard for API Management?
No. API Management is a much broader concept than what Gateway API aims to be,
or what an API Gateway is intended to provide. An API Gateway can be an
essential part of an API Management solution. Gateway API can be seen as a way
to standardize on that aspect of API Management.
to standardize provisioning of API Gateways.
27 changes: 13 additions & 14 deletions site-src/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -183,20 +183,19 @@ it must fit the uses to which each of Ana, Chihiro, and Ian will put it.

## What's the difference between Gateway API and an API Gateway?

An API Gateway is a general concept that describes anything that exposes
capabilities of a backend service, while providing extra capabilities for
traffic routing and manipulation, such as load balancing, request and response
transformation, and sometimes more advanced features like authentication and
authorization, rate limiting, and circuit breaking.

Gateway API is an interface, or set of resources, that model service
networking in Kubernetes. One of the main resources is a `Gateway`, which
declares the Gateway type (or class) to instantiate and its configuration. As
a Gateway Provider, you can implement Gateway API to model Kubernetes
service networking in an expressive, extensible, and role-oriented way.

Most Gateway API implementations are API Gateways to some extent, but not all
API Gateways are Gateway API implementations.
An [API gateway](https://glossary.cncf.io/api-gateway/) is a tool that
aggregates unique application APIs, making them all available in one place.
It allows organizations to move key functions, such as authentication and
authorization or limiting the number of requests between applications, to a
centrally managed location. An API gateway functions as a common interface to (often external) API consumers.

Gateway API is an interface, defined as a set of Kubernetes resources, that
models service networking in Kubernetes. One of the main resources is a `Gateway`,
which declares the Gateway type (or class) to instantiate and its configuration.
As a Gateway provider, you can implement Gateway API to model Kubernetes service
networking in an expressive, extensible, and role-oriented way.

Some API gateways can be programmed using the Gateway API.

## Who is working on Gateway API?

Expand Down