mirror of
https://github.com/k3s-io/kubernetes.git
synced 2026-01-05 23:47:50 +00:00
Rename Event.Status to Event.Condition to match v1beta3 agreement
Question - should this be a phase? Seems like no, since phase implies defined lifecycle and this field is explicitly not defined.
This commit is contained in:
@@ -953,18 +953,18 @@ type Event struct {
|
||||
// Required. The object that this event is about.
|
||||
InvolvedObject ObjectReference `json:"involvedObject,omitempty"`
|
||||
|
||||
// Should be a short, machine understandable string that describes the current status
|
||||
// Should be a short, machine understandable string that describes the current condition
|
||||
// of the referred object. This should not give the reason for being in this state.
|
||||
// Examples: "running", "cantStart", "cantSchedule", "deleted".
|
||||
// It's OK for components to make up statuses to report here, but the same string should
|
||||
// always be used for the same status.
|
||||
// Examples: "Running", "CantStart", "CantSchedule", "Deleted".
|
||||
// It's OK for components to make up conditions to report here, but the same string should
|
||||
// always be used for the same conditions.
|
||||
// TODO: define a way of making sure these are consistent and don't collide.
|
||||
// TODO: provide exact specification for format.
|
||||
Status string `json:"status,omitempty"`
|
||||
Condition string `json:"condition,omitempty"`
|
||||
|
||||
// Optional; this should be a short, machine understandable string that gives the reason
|
||||
// for the transition into the object's current status. For example, if ObjectStatus is
|
||||
// "cantStart", StatusReason might be "imageNotFound".
|
||||
// for the transition into the object's current condition. For example, if ObjectCondition is
|
||||
// "CantStart", StatusReason might be "ImageNotFound".
|
||||
// TODO: provide exact specification for format.
|
||||
Reason string `json:"reason,omitempty"`
|
||||
|
||||
|
||||
Reference in New Issue
Block a user