v1.0.0 #2549
robscott
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
v1.0.0
On behalf of Kubernetes SIG Network, we are pleased to announce the v1.0 release!
This release marks a huge milestone for this project. Several key APIs are
graduating to GA (generally available), while other significant features have
been added to the Experimental channel.
It's been four years since this project began, and we would never have gotten
here without the support of a dedicated and active community. The maintainers
would like to thanks everyone who's contributed to Gateway API, whether in the
form of commits to the repo, discussion, ideas, or general support. We literally
couldn't have gotten this far without you.
This project is nowhere near finished, as you can see from the large amount of
features being added into the Experimental Channel. With such a big set of
things still to do, contributors and contributions are more vital than ever.
Please feel welcome to join our community!!
Gateway, GatewayClass, and HTTPRoute are GA 🎉
Gateway, GatewayClass, and HTTPRoute have all graduated to GA with a
v1APIversion. Although these APIs will continue to grow with future additions, the
versions of these resources available via the Standard Channel are stable and
recommended for use in production. Many implementations are fully passing
conformance tests that cover the functionality of each of these resources. These
APIs are graduating to GA with only minor spec clarifications since the v0.8.0
release.
CEL Migration
Starting in v0.8.0, Gateway API CRDs now include CEL validation. In this release
the validating webhook is no longer bundled with CRD installation. Instead we
include a separate
webhook-install.yamlfile as part of the release artifacts.If you're running Kubernetes 1.25+, we do not recommend installing the webhook
and additionally suggest that you uninstall any previously installed versions of
the webhook.
If you're still running Kubernetes 1.23 or 1.24, we recommend installing the
webhook until you can upgrade to Kubernetes 1.25 or newer.
New Experimental Features
There are several exciting new experimental features in this release:
BackendTLSPolicy
A new
BackendTLSPolicyresource has been introduced for configuring TLSconnections from Gateways to Backends. This allows you to configure the Gateway
to validate the certificates served by Backends. For more information, refer to
GEP 1897.
Primary Author: @candita
HTTPRoute Timeouts
HTTPRoute has a new
Timeoutsfield on Route Rules. This allows you toconfigure overall Request Timeouts as well as Backend Request Timeouts. For more
information, refer to GEP 1742.
Primary Authors: @frankbu, @SRodi
Gateway Infrastructure Labels
Gateway has a new
Infrastructurefield that allows you to specifyLabelsorAnnotationsthat you'd like to be propagated to each resource generated for aGateway. For example, these labels and annotations may be copied to Services and
Deployments provisioned for in-cluster Gateways, or to other
implementation-specific resources, such as Cloud Load Balancers. For more
information, refer to GEP 1762.
Primary Author: @howardjohn
WebSockets, HTTP/2, and More
Some coordinated work across both Gateway API and upstream Kubernetes has
defined 3 new values for the AppProtocol field on Service Ports:
kubernetes.io/h2c- HTTP/2 over cleartext as described inRFC7540
kubernetes.io/ws- WebSocket over cleartext as described inRFC6445
kubernetes.io/wss- WebSocket over TLS as described inRFC6455
These can now be used with Gateway API to describe the protocol to use for
connections to Kubernetes Services. For more information, refer to GEP 1911.
A new CLI tool: gwctl
An experimental new CLI tool and kubectl plugin, gwctl aims to improve the UX
when interacting with Gateway API. Initially it is focused on Policy Attachment,
making it easier to understand which policies are available in a cluster, and
which have been applied. In future releases, we hope to expand the scope of this
tool to provide more detailed responses when getting and describing Gateway API
resources. Note that this tool is still in very early stages and it's very
likely that future releases will include breaking changes for gwctl. For more
information, refer to the gwctl Readme.
Primary Author: @gauravkghildiyal
Everything Else
Of course there's a lot more in this release:
Spec Clarifications
the number of Routes associated with a Listener regardless of Gateway or Route
status. (Clarify Gateway Listener Status AttachedRoutes field #2396, @sunjayBhatia)
describe the recommendation that at most one Listener matches a request, and
only Routes attached to that Listener are used for routing. (Documenting Listener Isolation in Gateway Spec #2465, @robscott)
both need to specify a distinct SectionName, both need to specify a distinct
Port, or both. (Requiring SectionName or Port to be specified for distinct parents #2433, @robscott)
distinct(Add distinct concept to Listener definition #2436,@youngnick)
Status
supportedFeaturesfield has beenadded. Implementations should populate this with the features they support.
(Supported features implementation #2461, @LiorLieberman, @robscott)
be set when a GatewayClass is accepted. (Adding new SupportedVersion condition to GatewayClass #2384, @robscott)
types. This condition also includes guidance for how partially invalid states
should be handled with Gateway API. (Adding new PartiallyInvalid condition for Routes #2429, @robscott)
GatewayReasonUnsupportedAddressforAcceptednow ONLYapplies when an address type is provided for a
Gatewaywhich it does notsupport.
(Conformance tests for static Gateway addresses #2412 @shaneutt)
GatewayReasonAddressNotAssignedforProgrammednowONLY applies to problems with dynamic address allocation.
(Conformance tests for static Gateway addresses #2412 @shaneutt)
GatewayReasonAddressNotUsableforProgrammedhas beenadded to deal with situations where a static address has been provided for a
Gateway which is of a supported type, and is syntactically valid, but for some
reason it can not be used for this Gateway (e.g. the address is already in use
on the network).
(Conformance tests for static Gateway addresses #2412 @shaneutt)
Documentation
(Add implementer's guide #2454, @youngnick)
Standard and Experimental. New resources will start in the Experimental
Channel with an alpha API Version and then graduate to the Standard Channel
with a GA API version. Resources that already have Beta API versions will
continue to have them, but no additional Gateway API resources will get a Beta
API version. (Phasing out Beta from Versioning Guide #2446, @robscott)
Cleanup
Errorfinstead ofFatalf. (update signal error log #2361, @yylt)Bug Fixes
(BackendTLSPolicy cel tests #2491, @Ygnas)
ReferenceGrantfromv1tov1beta1in theGatewaySecretInvalidReferenceGrantconformance test YAML (conformance: revert ver to v1beta1 for RefGrant #2494, @arkodg)Conformance Tests
ExemptFeaturesfield for Experimental Conformance Profiles(implement exemptFeatures for conformance profile #2515, @arkodg)
Other (Cleanup or Flake)
gateway-systemnamespace and the
gateway-api-admission-serverdeployment have been removedfrom the installation manifests, in favor of CEL based Validations that are
built into the CRD definition. These are still available in
webhook-install.yamlin case you would like to optionally install them.(rm webhook resources from installation yaml #2401, @arkodg)
This discussion was created from the release v1.0.0.
Beta Was this translation helpful? Give feedback.
All reactions