@@ -9,25 +9,25 @@ slug: gateway-api-ga
9
9
10
10
We (the community developing [ Gateway API] [ gwapi ] ) are incredibly pleased and
11
11
proud to announce _ general availability_ of Gateway API for use with Kubernetes
12
- clusters ` v1 .24` and newer!
12
+ clusters (versions 1 .24 and newer) !
13
13
14
14
## Important Highlights
15
15
16
- Gateway API brings a lot of new networking possibilities to the table in your
16
+ Kubernetes' Gateway API brings a lot of new networking possibilities to the table in your
17
17
Kubernetes cluster. In this post we'll cover some of the most important
18
18
highlights.
19
19
20
20
For a complete list of changes for this specific release, please see our
21
21
[ v1.0.0 changelog entry] [ chlogv1 ] .
22
22
23
23
For a complete list of every feature for every release, or to review some of
24
- the releases leading up to ` v1.0.0 ` , please see our [ historical
24
+ the releases leading up to v1.0.0, please see our [ historical
25
25
changelog] [ clog ] .
26
26
27
27
### Version 1 APIs
28
28
29
29
This marks the ** first stable release** of Gateway API, where we are now
30
- publishing the following APIs as ` v1 ` (Version 1):
30
+ publishing the following APIs as ` v1 ` (version 1):
31
31
32
32
- [ GatewayClass] [ gwc ]
33
33
- [ Gateway] [ gw ]
@@ -64,10 +64,9 @@ such, this release is supported on Kubernetes clusters version `1.24` through
64
64
### Getting Started
65
65
66
66
If you want to try Gateway API features out for yourself but don't know where
67
- to get started you'll want to check out one of the 20+ implementations which
68
- we list on our website:
69
-
70
- https://gateway-api.sigs.k8s.io/implementations/
67
+ to get started you'll want to check out one of the 20+
68
+ [ implementations] ( https://gateway-api.sigs.k8s.io/implementations/ ) which
69
+ we list on the Gateway API website.
71
70
72
71
Gateway API itself is just an API for downstream projects to implement, so take
73
72
some time to peruse the implementations list above and find one that seems to
@@ -94,19 +93,19 @@ If you opt-in to the [experimental channel][expch] for this release, you'll find
94
93
that there are several experimental features available which are being
95
94
considered for inclusion as stable in future releases:
96
95
97
- - [ BackendTLSPolicy ] [ gep1897 ]
96
+ - [ Backend TLS policy ] [ gep1897 ]
98
97
- [ HTTPRoute Timeouts] [ gep1742 ]
99
98
- [ Gateway Infrastructure Labels] [ gep1762 ]
100
- - [ Websockets, HTTP/2 and More !] [ gep1911 ]
101
- - [ GWCTL , our new Gateway API CLI ] [ gwctl ]
99
+ - Support for [ Websockets, HTTP/2 and more !] [ gep1911 ]
100
+ - [ ` gwctl ` ] [ gwctl ] , our new Gateway API command line tool
102
101
103
102
We intend to have a blog post following up on this one which will cover these
104
103
(and potentially more) experimental and upcoming features where the authors of
105
104
the features themselves can provide a greater level of detail.
106
105
107
106
In future iterations we also intend to grow the maturity and work towards
108
- [ graduation] [ grad ] of APIs other than ` GatewayClass ` , ` Gateway ` , and
109
- ` HTTPRoute ` , which are not yet at version 1:
107
+ [ graduation] [ grad ] of APIs other than GatewayClass, Gateway, and
108
+ HTTPRoute. There are several APIs that are not yet at version 1:
110
109
111
110
- [ GRPCRoute] [ grpc ]
112
111
- [ TCPRoute] [ tcp ]
@@ -115,22 +114,22 @@ In future iterations we also intend to grow the maturity and work towards
115
114
- [ ReferenceGrant] [ refg ]
116
115
117
116
[ ReferenceGrant] [ refg ] is a slightly special case as we are considering what
118
- to do with this resource next : we've come to understand this might be a
117
+ to do with this: we've come to understand this might be a
119
118
feature applicable to the greater Kubernetes community and we're trying to
120
119
navigate potentially moving it somewhere more general to maximize benefit.
121
120
122
121
For those interested in service mesh, note that we continue to work on making
123
122
Gateway API resources available for use in service mesh contexts as part of the
124
- [ GAMMA project] [ gamma ] . Please see our recent blog post [ " Gateway API v0.8.0:
125
- Introducing Service Mesh Support" ] [ gammablog ] for more details.
123
+ [ GAMMA project] [ gamma ] . Please see our recent blog post [ Gateway API v0.8.0:
124
+ Introducing Service Mesh Support] [ gammablog ] for more details.
126
125
127
126
What you've seen here is _ not exhaustive_ ! Gateway API is a highly active
128
127
project, with dozens of people actively working on it. If you're hoping to see
129
128
one of the above routes graduated, or have ideas for features that we have yet
130
129
to account for, we _ strongly encourage_ you to [ join us in the community] [ com ]
131
130
and help us build!
132
131
133
- ## Kubecon North America: Chicago
132
+ ## Gateway API events at KubeCon + CloudNativeCon
134
133
135
134
At [ Kubecon North America (Chicago)] [ kna ] and the adjacent
136
135
[ Contributor Summit] [ csum ] there are several talks about or related to Gateway
@@ -157,7 +156,7 @@ give a huge shout out and thanks to them!
157
156
Thank you so much to our [ 170+ contributors] [ contribs ] who built this project
158
157
together with us, and made our GA release possible!
159
158
160
- A special thank you to our [ community members which agreed to take on an
159
+ A special thank you to our [ community members who agreed to take on an
161
160
official role in the project] [ roles ] , explicitly providing some time for reviews
162
161
and sharing the load of maintaining the project!
163
162
0 commit comments