workload-partitioning: describe warning annotation
Add details about the warning annotation used to communicate with the
user when their partitioning instructions are ignored.
@@ -260,6 +260,13 @@ unschedulable workloads, but we expect the resulting error message to
explain the problem well enough for admins to recover. Future work may
make this more flexible.
+In a failure situation, we want to try to keep the cluster
+operational. Therefore, when pods ask for workload partitioning but
+the feature is disabled the admission hook will strip the
+workload-related annotations and add an annotation
+`workload.openshift.io/warning` with a message warning the user that
+their partitioning instructions were ignored.
+
We are not prepared to commit to an installer API for this feature in
this initial implementation. Therefore, we will document how to create
the correct machine config manifests to enable it in `kubelet` and
@@ -524,9 +531,12 @@ Service](https://kubernetes.io/docs/tasks/configure-pod-container/quality-servic
class. So, we would not strip CPU requests unless they also have
memory requests, because if we mutate the pod so that it has no CPU or
memory requests the quality-of-service class of the pod would be
-changed automatically. Any pod that is already BestEffort
-would be annotated using `0` as the value so that CRI-O will have an
-indicator to configure the CPU shares as BestEffort.
+changed automatically. In this case, the
+`workload.openshift.io/warning` annotation will include a message
+explaining that the partitioning instructions were ignored. Any pod
+that is already BestEffort would be annotated using `0` as the value
+so that CRI-O will have an indicator to configure the CPU shares as
+BestEffort.
#### Kubelet Changes
