mirror of https://github.com/k3s-io/k3s
8371a778f6
Automatic merge from submit-queue CRI: Add Status into CRI. For https://github.com/kubernetes/kubernetes/issues/35701. Fixes https://github.com/kubernetes/kubernetes/issues/35701. This PR added a `Status` call in CRI, and the `RuntimeStatus` is defined as following: ``` protobuf message RuntimeCondition { // Type of runtime condition. optional string type = 1; // Status of the condition, one of true/false. optional bool status = 2; // Brief reason for the condition's last transition. optional string reason = 3; // Human readable message indicating details about last transition. optional string message = 4; } message RuntimeStatus { // Conditions is an array of current observed runtime conditions. repeated RuntimeCondition conditions = 1; } ``` Currently, only `conditions` is included in `RuntimeStatus`, and the definition is almost the same with `NodeCondition` and `PodCondition` in K8s api. @yujuhong @feiskyer @bprashanth If this makes sense, I'll send a follow up PR to let dockershim return `RuntimeStatus` and let kubelet make use of it. @yifan-gu @euank Does this make sense to rkt? /cc @kubernetes/sig-node |
||
|---|---|---|
| .. | ||
| testing | ||
| v1alpha1 | ||
| BUILD | ||
| services.go | ||