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
Copy file name to clipboardExpand all lines: content/en/blog/_posts/2023-10-18-gateway-api-time-to-switch-i2gw/index.md
+9-4Lines changed: 9 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,10 +32,16 @@ Gateway API employs a role-oriented approach that aligns with the conventional r
32
32
33
33
For instance, infrastructure engineers play a pivotal role in deploying GatewayClasses, cluster-scoped resources that act as templates to explicitly define behavior for Gateways derived from them, laying the groundwork for robust service networking.
34
34
35
-
<!-- TODO(liorlieberman) -->
36
-
<!-- Subsequently, cluster operators utilize these GatewayClasses to deploy gateways, brief whats gateways> -->
35
+
Subsequently, cluster operators utilize these GatewayClasses to deploy gateways.
36
+
A Gateway in Kubernetes' Gateway-API defines how external traffic can be directed to Services within the cluster, essentially bridging non-Kubernetes sources to Kubernetes-aware destinations.
37
+
It represents a request for a load balancer configuration aligned with a GatewayClass’ specification.
38
+
The Gateway spec may not be exhaustive as some details can be supplied by the GatewayClass controller, ensuring portability.
39
+
Additionally, a Gateway can be linked to multiple Route references to channel specific traffic subsets to designated services.
37
40
38
-
<!-- Lastly, application developers … -->
41
+
Lastly, application developers configure route resources (such as HTTPRoutes), to manage configuration (e.g. timeouts, request matching/filter) and Service composition (e.g. path routing to backends)
42
+
Route resources define protocol-specific rules for mapping requests from a Gateway to Kubernetes Services.
43
+
HTTPRoute is for multiplexing HTTP or terminated HTTPS connections.
44
+
It's intended for use in cases where you want to inspect the HTTP stream and use HTTP request data for either routing or modification, for example using HTTP Headers for routing, or modifying them in-flight.
39
45
40
46

41
47
@@ -52,7 +58,6 @@ Gateway API allows for custom resources to be linked at various layers of the AP
52
58
53
59
### Gateway API Quick Start
54
60
55
-
<!-- TODO(liorlieberman) - either put it here or provide links to reference on how to install and deploy a service exposed with a Gateway and HTTPRoute. -->
56
61
The first thing you will need is a Kubernetes cluster. You can set up a new cluster using [KinD](https://kind.sigs.k8s.io/) with the following command:
0 commit comments