liveBook · Manning

Core feature

As explained in Kubernetes in Action, Second Edition

A core feature is a portable Gateway API feature that every conforming implementation must support.

A core feature is a standard Gateway API feature that every conforming implementation must support. Core features are portable, so configurations using only them should transfer between Gateway API implementations without changes. section 13.1.2

Distinguish core features from the other Gateway API support levels:

  • Extended features remain portable and have consistent semantics, but an implementation may not support them. section 13.1.2
  • Implementation-specific features depend on the provider and may require configuration changes when switching implementations. section 13.1.2

A standard-channel example

HTTPRoute is identified as the only route kind available in the standard channel at the stated point in time; channel stability and implementation support are separate concerns. section 13.1.2

How Kubernetes in Action, Second Edition covers it

How deep it goes
Defines support levels and switching implications, but does not detail individual feature implementations.
Examples
Uses HTTPRoute as a standard-channel example while separating channel status from implementation support.
What you can do after
Evaluate Gateway API features for portability before switching implementations.
How it connects
Connects Gateway API with extended features and implementation-specific features.
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.