liveBook · Manning

Support level

As explained in Kubernetes in Action, Second Edition

A support level classifies how consistently a Gateway API feature is supported across implementations.

A support level classifies how consistently a Gateway API feature is supported across implementations. It addresses an implementation question that release channels do not answer: a feature can be stable without every implementation supporting it. section 13.1.2

Gateway API features use three support levels:

Do not confuse support with stability

The standard release channel contains stable resources and fields, but standard-channel status alone does not mean that every Gateway API implementation supports a feature. Check both the release channel and the feature’s support level. section 13.1.2

How Kubernetes in Action, Second Edition covers it

How deep it goes
Names core, extended, and implementation-specific levels, but does not define their individual guarantees.
Examples
Contrasts standard-channel stability with the separate question of whether implementations support a feature.
What it assumes
Assumes familiarity with Gateway API implementations and distinguishes support levels from release channels.
What you can do after
Evaluate Gateway API features using both release-channel status and implementation support level.
How it connects
Connects Gateway API support levels with implementations, release channels, standard features, experimental features, and CRDs.
Cover of Kubernetes in Action, Second Edition
liveBookmanning.com
Read Kubernetes in Action, Second Edition on liveBook Get the book at manning.com

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.