liveBook · Manning

Standard release channel

As explained in Kubernetes in Action, Second Edition

The standard release channel contains Gateway API resources and fields considered stable and not expected to change in future API versions.

The standard release channel contains Gateway API resources and fields considered stable and not expected to change in future API versions. When installing Gateway API Custom Resource Definitions (CRDs), choose either the standard or experimental channel. section 13.1.2

Distinguish release-channel stability from implementation support:

  • Standard contains stable resources and fields; experimental adds features that may change. section 13.1.2
  • A standard feature is not automatically supported by every Gateway API implementation; support is classified separately as core, extended, or implementation-specific. section 13.1.2

HTTPRoute in the standard channel

In the stated API snapshot, HTTPRoute is available in the standard channel, while other route kinds remain experimental until their APIs cover the relevant use cases. section 13.1.2

How Kubernetes in Action, Second Edition covers it

How deep it goes
Defines stability and contrasts experimental features, but stops short of detailing installation commands or individual field behavior.
Examples
Contrasts standard HTTPRoute availability with experimental status for other route kinds.
What it assumes
Assumes familiarity with Gateway API resources and Custom Resource Definitions at the terminology level.
What you can do after
Operate/configure Gateway API CRD installation by selecting a release channel based on feature stability.
How it connects
Links Gateway API resources, Custom Resource Definitions, HTTPRoute, experimental release channel, and implementation support levels.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Kubernetes in Action, Second Edition. The section links point to the parts of the book it draws on.