You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The structured parameter allocation logic was written from scratch in
staging/src/k8s.io/dynamic-resource-allocation/structured. Besides the new
features (amount, admin access) and API it now supports backtracking when the
initial device selection doesn't lead to a complete allocation of all claims.
"make" works. A local cluster comes up and can run the DRA E2E tests.
pkg/scheduler/framework/plugins/dynamicresources unit tests pass.
test/integration/scheduler_perf unit tests pass for DRA.
Many other unit tests haven't been adapted yet and coverage of new code is
poor.
DRA: use VAP to control "admin access" permissions
The advantages of using a validation admission policy (VAP) are that no changes
are needed in Kubernetes and that admins have full flexibility if and how they
want to control which users are allowed to use "admin access" in their
requests.
The downside is that without admins taking actions, the feature is enabled
out-of-the-box in a cluster. Documentation for DRA will have to make it very
clear that something needs to be done in multi-tenant clusters.
The test/e2e/testing-manifests/dra/admin-access-policy.yaml shows how to do
this. The corresponding E2E tests ensures that it actually works as intended.
For some reason, adding the namespace to the message expression leads to a
type check errors, so it's currently commented out.
DRA kubelet: always call NodePrepareResources, even if not used
This could be useful for drivers where that call has some effect other than
injecting CDI device IDs into containers.
DRA: remove obsolete support for deterministic claim name
Now only the claim name as recorded in the pod status matters, which can be
looked up without listing claims.
DRA kubelet: extend and clean up logging
Because of a faulty E2E test, kubelet was told to contact the wrong driver for
a claim. This was not visible in the kubelet log output. Now changes to the
claim info cache are getting logged. While at it, naming of variables and some
existing log output gets harmonized.
Co-authored-by: Ed Bartosh <[email protected]>
Co-authored-by: Oksana Baranova <[email protected]>
0 commit comments