Skip to content

Commit 8786f80

Browse files
committed
KEP-3008: clarify goals
1 parent 871ec02 commit 8786f80

File tree

1 file changed

+10
-9
lines changed
  • keps/sig-node/3008-cri-class-based-resources

1 file changed

+10
-9
lines changed

keps/sig-node/3008-cri-class-based-resources/README.md

+10-9
Original file line numberDiff line numberDiff line change
@@ -230,10 +230,11 @@ List the specific goals of the KEP. What is it trying to achieve? How will we
230230
know that this has succeeded?
231231
-->
232232

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

239240
### Non-Goals
@@ -304,13 +305,13 @@ Go in to as much detail as necessary here.
304305
This might be a good place to talk about core concepts and how they relate.
305306
-->
306307

307-
This is only the first in getting class-based resources supported in
308+
This is only the first step in getting class-based resources supported in
308309
Kubernetes. Important pieces like resource status, resource disovery and
309310
permission control are [non-goals](#non-goals) not solved here. However, these
310-
aspects are briefly discussed in [future work](#future-work). However, the risk
311-
in this sort of piecemeal approach is finding devil in the details, resulting
312-
in inconsistent and/or crippled and/or cumbersome end result. However, there is
313-
a lot of experience in extending the API and understanding which sort of
311+
aspects are briefly discussed in [future work](#future-work). The risk in this
312+
sort of piecemeal approach is finding devil in the details, resulting in
313+
inconsistent and/or crippled and/or cumbersome end result. However, there is a
314+
lot of experience in extending the API and understanding which sort of
314315
solutions are functional and practical.
315316

316317
### Risks and Mitigations

0 commit comments

Comments
 (0)