Skip to content

Commit

Permalink
KEP-3008: clarify goals
Browse files Browse the repository at this point in the history
  • Loading branch information
marquiz committed Feb 22, 2022
1 parent 871ec02 commit eefa0e3
Showing 1 changed file with 6 additions and 5 deletions.
11 changes: 6 additions & 5 deletions keps/sig-node/3008-cri-class-based-resources/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -230,10 +230,11 @@ List the specific goals of the KEP. What is it trying to achieve? How will we
know that this has succeeded?
-->

- Introduce RDT support comparable to the OCI runtime-spec to CRI protocol.
- Make it possible to specify the RDT class of containers on CRI level.
- Make it possible to specify the blockio class of containers on CRI level.
- Make the extensions flexible, enabling easy addition of other class-based
- Make it possible to request class resources
- Support RDT class assignment of containers. This is already supported by
the containerd and CRI-O runtime and part of the OCI runtime-spec
- Support blockio class assignment of containers.
- Make the extensions flexible, enabling simple addition of other class-based
resource types in the future.

### Non-Goals
Expand Down Expand Up @@ -304,7 +305,7 @@ Go in to as much detail as necessary here.
This might be a good place to talk about core concepts and how they relate.
-->

This is only the first in getting class-based resources supported in
This is only the first step in getting class-based resources supported in
Kubernetes. Important pieces like resource status, resource disovery and
permission control are [non-goals](#non-goals) not solved here. However, these
aspects are briefly discussed in [future work](#future-work). However, the risk
Expand Down

0 comments on commit eefa0e3

Please sign in to comment.