Merge pull request #8052 from dkorn/PodConditions

Inconsistency in api terminology of pod conditions
This commit is contained in:
Brian Grant
2015-05-12 11:03:59 -07:00
2 changed files with 2 additions and 2 deletions

View File

@@ -832,7 +832,7 @@ type PodSpec struct {
// state of a system.
type PodStatus struct {
Phase PodPhase `json:"phase,omitempty"`
Conditions []PodCondition `json:"Condition,omitempty"`
Conditions []PodCondition `json:"conditions,omitempty"`
// A human readable message indicating details about why the pod is in this state.
Message string `json:"message,omitempty"`

View File

@@ -833,7 +833,7 @@ type PodSpec struct {
// state of a system.
type PodStatus struct {
Phase PodPhase `json:"phase,omitempty" description:"current condition of the pod."`
Conditions []PodCondition `json:"Condition,omitempty" description:"current service state of pod" patchStrategy:"merge" patchMergeKey:"type"`
Conditions []PodCondition `json:"conditions,omitempty" description:"current service state of pod" patchStrategy:"merge" patchMergeKey:"type"`
// A human readable message indicating details about why the pod is in this state.
Message string `json:"message,omitempty" description:"human readable message indicating details about why the pod is in this condition"`