As suggested in
https://github.com/kubernetes/website/pull/48330#discussion_r1799302946, the
front matter gets extended to reference the API types. To make this work,
the necessary API reference files get created manually. They still need to be
updated via the usual automatic API generation.
The concepts are mostly the same as before. Support for parameters in a CRD was
removed in favor of storing selection and configuration parameters directly in
ResourceClaim and DeviceClass.
Several improvements under the hood which don't need to be documented here. API
changes (like storing generated resource claim names in the pod status) are
part of the generated API documentation.
What is worth mentioning because it was listed as "limitation" before is that
pre-scheduled pods are now supported better.
The documentation intentionally only gives an overview. The API documentation
and the KEP have more details. Specific examples will be provided by hardware
vendors that provide resource drivers.
The new page gets placed between "Scheduling Framework" (because that
introduces the concept of a scheduler plugin) and "Scheduler Performance
Tuning" (which seems like a more advanced topic).
Patrick Ohly
Lionel Jouin
Christopher Desiniotis
Michael
Zain Rizvi
Kubernetes Prow Robot
Alexis Boissiere
Tim Bannister
Vaibhav Goel
Kubernetes Prow Robot
Moshe Levi