"description":"MinReadySeconds minimum number of seconds for which a newly created DaemonSet pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready).",
"type":"integer",
"format":"int32"
},
"selector":{
"description":"Selector is a label query over pods that are managed by the daemon set. Must match in order to be controlled. If empty, defaulted to labels on Pod template. More info: http://kubernetes.io/docs/user-guide/labels#label-selectors",
"description":"Template is the object that describes the pod that will be created. The DaemonSet will create exactly one copy of this pod on every node that matches the template's node selector (or on every node if no node selector is specified). More info: http://kubernetes.io/docs/user-guide/replication-controller#pod-template",
"description":"A sequence number representing a specific generation of the template. Populated by the system. It can be set only during the creation.",
"type":"integer",
"format":"int64"
},
"updateStrategy":{
"description":"UpdateStrategy to replace existing DaemonSet pods with new pods.",
"description":"NumberAvailable is the number of nodes that should be running the daemon pod and have one or more of the daemon pod running and available (ready for at least minReadySeconds)",
"type":"integer",
"format":"int32"
},
"numberMisscheduled":{
"description":"NumberMisscheduled is the number of nodes that are running the daemon pod, but are not supposed to run the daemon pod. More info: http://releases.k8s.io/HEAD/docs/admin/daemons.md",
"type":"integer",
...
...
@@ -41478,10 +41497,32 @@
"type":"integer",
"format":"int32"
},
"numberUnavailable":{
"description":"NumberUnavailable is the number of nodes that should be running the daemon pod and have none of the daemon pod running and available (ready for at least minReadySeconds)",
"type":"integer",
"format":"int32"
},
"observedGeneration":{
"description":"ObservedGeneration is the most recent generation observed by the daemon set controller.",
"type":"integer",
"format":"int64"
},
"updatedNumberScheduled":{
"description":"UpdatedNumberScheduled is the total number of nodes that are running updated daemon pod",
"description":"Spec to control the desired behavior of daemon set rolling update.",
"properties":{
"maxUnavailable":{
"description":"The maximum number of DaemonSet pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total number of DaemonSet pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up. This cannot be 0. Default value is 1. Example: when this is set to 30%, 30% of the currently running DaemonSet pods can be stopped for an update at any given time. The update starts by stopping at most 30% of the currently running DaemonSet pods and then brings up new DaemonSet pods in their place. Once the new pods are ready, it then proceeds onto other DaemonSet pods, thus ensuring that at least 70% of original number of DaemonSet pods are available at all times during the update.",
"description":"Template is the object that describes the pod that will be created. The DaemonSet will create exactly one copy of this pod on every node that matches the template's node selector (or on every node if no node selector is specified). More info: http://kubernetes.io/docs/user-guide/replication-controller#pod-template"
},
"updateStrategy":{
"$ref":"v1beta1.DaemonSetUpdateStrategy",
"description":"UpdateStrategy to replace existing DaemonSet pods with new pods."
},
"minReadySeconds":{
"type":"integer",
"format":"int32",
"description":"MinReadySeconds minimum number of seconds for which a newly created DaemonSet pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)."
},
"templateGeneration":{
"type":"integer",
"format":"int64",
"description":"A sequence number representing a specific generation of the template. Populated by the system. It can be set only during the creation."
}
}
},
...
...
@@ -8439,6 +8453,29 @@
}
}
},
"v1beta1.DaemonSetUpdateStrategy":{
"id":"v1beta1.DaemonSetUpdateStrategy",
"properties":{
"type":{
"type":"string",
"description":"Type of daemon set update. Can be \"RollingUpdate\" or \"OnDelete\". Default is OnDelete."
},
"rollingUpdate":{
"$ref":"v1beta1.RollingUpdateDaemonSet",
"description":"Rolling update config params. Present only if DaemonSetUpdateStrategy = RollingUpdate."
}
}
},
"v1beta1.RollingUpdateDaemonSet":{
"id":"v1beta1.RollingUpdateDaemonSet",
"description":"Spec to control the desired behavior of daemon set rolling update.",
"properties":{
"maxUnavailable":{
"type":"string",
"description":"The maximum number of DaemonSet pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total number of DaemonSet pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up. This cannot be 0. Default value is 1. Example: when this is set to 30%, 30% of the currently running DaemonSet pods can be stopped for an update at any given time. The update starts by stopping at most 30% of the currently running DaemonSet pods and then brings up new DaemonSet pods in their place. Once the new pods are ready, it then proceeds onto other DaemonSet pods, thus ensuring that at least 70% of original number of DaemonSet pods are available at all times during the update."
}
}
},
"v1beta1.DaemonSetStatus":{
"id":"v1beta1.DaemonSetStatus",
"description":"DaemonSetStatus represents the current status of a daemon set.",
...
...
@@ -8473,6 +8510,21 @@
"type":"integer",
"format":"int64",
"description":"ObservedGeneration is the most recent generation observed by the daemon set controller."
},
"updatedNumberScheduled":{
"type":"integer",
"format":"int32",
"description":"UpdatedNumberScheduled is the total number of nodes that are running updated daemon pod"
},
"numberAvailable":{
"type":"integer",
"format":"int32",
"description":"NumberAvailable is the number of nodes that should be running the daemon pod and have one or more of the daemon pod running and available (ready for at least minReadySeconds)"
},
"numberUnavailable":{
"type":"integer",
"format":"int32",
"description":"NumberUnavailable is the number of nodes that should be running the daemon pod and have none of the daemon pod running and available (ready for at least minReadySeconds)"
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">UpdatedNumberScheduled is the total number of nodes that are running updated daemon pod</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">NumberAvailable is the number of nodes that should be running the daemon pod and have one or more of the daemon pod running and available (ready for at least minReadySeconds)</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">NumberUnavailable is the number of nodes that should be running the daemon pod and have none of the daemon pod running and available (ready for at least minReadySeconds)</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">The maximum number of DaemonSet pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total number of DaemonSet pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up. This cannot be 0. Default value is 1. Example: when this is set to 30%, 30% of the currently running DaemonSet pods can be stopped for an update at any given time. The update starts by stopping at most 30% of the currently running DaemonSet pods and then brings up new DaemonSet pods in their place. Once the new pods are ready, it then proceeds onto other DaemonSet pods, thus ensuring that at least 70% of original number of DaemonSet pods are available at all times during the update.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">MinReadySeconds minimum number of seconds for which a newly created DaemonSet pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready).</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">A sequence number representing a specific generation of the template. Populated by the system. It can be set only during the creation.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">Type of daemon set update. Can be "RollingUpdate" or "OnDelete". Default is OnDelete.</p></td>
"description":"MinReadySeconds minimum number of seconds for which a newly created DaemonSet pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready).",
"type":"integer",
"format":"int32"
},
"selector":{
"description":"Selector is a label query over pods that are managed by the daemon set. Must match in order to be controlled. If empty, defaulted to labels on Pod template. More info: http://kubernetes.io/docs/user-guide/labels#label-selectors",
"description":"Template is the object that describes the pod that will be created. The DaemonSet will create exactly one copy of this pod on every node that matches the template's node selector (or on every node if no node selector is specified). More info: http://kubernetes.io/docs/user-guide/replication-controller#pod-template",
"description":"A sequence number representing a specific generation of the template. Populated by the system. It can be set only during the creation.",
"type":"integer",
"format":"int64"
},
"updateStrategy":{
"description":"UpdateStrategy to replace existing DaemonSet pods with new pods.",
"description":"NumberAvailable is the number of nodes that should be running the daemon pod and have one or more of the daemon pod running and available (ready for at least minReadySeconds)",
"type":"integer",
"format":"int32"
},
"numberMisscheduled":{
"description":"NumberMisscheduled is the number of nodes that are running the daemon pod, but are not supposed to run the daemon pod. More info: http://releases.k8s.io/HEAD/docs/admin/daemons.md",
"type":"integer",
...
...
@@ -13849,10 +13868,32 @@
"type":"integer",
"format":"int32"
},
"numberUnavailable":{
"description":"NumberUnavailable is the number of nodes that should be running the daemon pod and have none of the daemon pod running and available (ready for at least minReadySeconds)",
"type":"integer",
"format":"int32"
},
"observedGeneration":{
"description":"ObservedGeneration is the most recent generation observed by the daemon set controller.",
"type":"integer",
"format":"int64"
},
"updatedNumberScheduled":{
"description":"UpdatedNumberScheduled is the total number of nodes that are running updated daemon pod",
"description":"Spec to control the desired behavior of daemon set rolling update.",
"properties":{
"maxUnavailable":{
"description":"The maximum number of DaemonSet pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total number of DaemonSet pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up. This cannot be 0. Default value is 1. Example: when this is set to 30%, 30% of the currently running DaemonSet pods can be stopped for an update at any given time. The update starts by stopping at most 30% of the currently running DaemonSet pods and then brings up new DaemonSet pods in their place. Once the new pods are ready, it then proceeds onto other DaemonSet pods, thus ensuring that at least 70% of original number of DaemonSet pods are available at all times during the update.",
"":"DaemonSetSpec is the specification of a daemon set.",
"selector":"Selector is a label query over pods that are managed by the daemon set. Must match in order to be controlled. If empty, defaulted to labels on Pod template. More info: http://kubernetes.io/docs/user-guide/labels#label-selectors",
"template":"Template is the object that describes the pod that will be created. The DaemonSet will create exactly one copy of this pod on every node that matches the template's node selector (or on every node if no node selector is specified). More info: http://kubernetes.io/docs/user-guide/replication-controller#pod-template",
"":"DaemonSetSpec is the specification of a daemon set.",
"selector":"Selector is a label query over pods that are managed by the daemon set. Must match in order to be controlled. If empty, defaulted to labels on Pod template. More info: http://kubernetes.io/docs/user-guide/labels#label-selectors",
"template":"Template is the object that describes the pod that will be created. The DaemonSet will create exactly one copy of this pod on every node that matches the template's node selector (or on every node if no node selector is specified). More info: http://kubernetes.io/docs/user-guide/replication-controller#pod-template",
"updateStrategy":"UpdateStrategy to replace existing DaemonSet pods with new pods.",
"minReadySeconds":"MinReadySeconds minimum number of seconds for which a newly created DaemonSet pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready).",
"templateGeneration":"A sequence number representing a specific generation of the template. Populated by the system. It can be set only during the creation.",
}
func(DaemonSetSpec)SwaggerDoc()map[string]string{
...
...
@@ -93,12 +96,24 @@ var map_DaemonSetStatus = map[string]string{
"desiredNumberScheduled":"DesiredNumberScheduled is the total number of nodes that should be running the daemon pod (including nodes correctly running the daemon pod). More info: http://releases.k8s.io/HEAD/docs/admin/daemons.md",
"numberReady":"NumberReady is the number of nodes that should be running the daemon pod and have one or more of the daemon pod running and ready.",
"observedGeneration":"ObservedGeneration is the most recent generation observed by the daemon set controller.",
"updatedNumberScheduled":"UpdatedNumberScheduled is the total number of nodes that are running updated daemon pod",
"numberAvailable":"NumberAvailable is the number of nodes that should be running the daemon pod and have one or more of the daemon pod running and available (ready for at least minReadySeconds)",
"numberUnavailable":"NumberUnavailable is the number of nodes that should be running the daemon pod and have none of the daemon pod running and available (ready for at least minReadySeconds)",
"":"Spec to control the desired behavior of daemon set rolling update.",
"maxUnavailable":"The maximum number of DaemonSet pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total number of DaemonSet pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up. This cannot be 0. Default value is 1. Example: when this is set to 30%, 30% of the currently running DaemonSet pods can be stopped for an update at any given time. The update starts by stopping at most 30% of the currently running DaemonSet pods and then brings up new DaemonSet pods in their place. Once the new pods are ready, it then proceeds onto other DaemonSet pods, thus ensuring that at least 70% of original number of DaemonSet pods are available at all times during the update.",
"":"Spec to control the desired behavior of rolling update.",
"maxUnavailable":"The maximum number of pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). Absolute number is calculated from percentage by rounding down. This can not be 0 if MaxSurge is 0. By default, a fixed value of 1 is used. Example: when this is set to 30%, the old RC can be scaled down to 70% of desired pods immediately when the rolling update starts. Once new pods are ready, old RC can be scaled down further, followed by scaling up the new RC, ensuring that the total number of pods available at all times during the update is at least 70% of desired pods.",
Description:"MinReadySeconds minimum number of seconds for which a newly created DaemonSet pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready).",
Type:[]string{"integer"},
Format:"int32",
},
},
"templateGeneration":{
SchemaProps:spec.SchemaProps{
Description:"A sequence number representing a specific generation of the template. Populated by the system. It can be set only during the creation.",
Description:"UpdatedNumberScheduled is the total number of nodes that are running updated daemon pod",
Type:[]string{"integer"},
Format:"int32",
},
},
"numberAvailable":{
SchemaProps:spec.SchemaProps{
Description:"NumberAvailable is the number of nodes that should be running the daemon pod and have one or more of the daemon pod running and available (ready for at least minReadySeconds)",
Type:[]string{"integer"},
Format:"int32",
},
},
"numberUnavailable":{
SchemaProps:spec.SchemaProps{
Description:"NumberUnavailable is the number of nodes that should be running the daemon pod and have none of the daemon pod running and available (ready for at least minReadySeconds)",
Description:"Spec to control the desired behavior of daemon set rolling update.",
Properties:map[string]spec.Schema{
"maxUnavailable":{
SchemaProps:spec.SchemaProps{
Description:"The maximum number of DaemonSet pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total number of DaemonSet pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up. This cannot be 0. Default value is 1. Example: when this is set to 30%, 30% of the currently running DaemonSet pods can be stopped for an update at any given time. The update starts by stopping at most 30% of the currently running DaemonSet pods and then brings up new DaemonSet pods in their place. Once the new pods are ready, it then proceeds onto other DaemonSet pods, thus ensuring that at least 70% of original number of DaemonSet pods are available at all times during the update.",
