+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Patch
@@ -559,24 +589,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified CronJob
HTTP Request
@@ -651,24 +685,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified CronJob
HTTP Request
@@ -747,24 +785,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a CronJob
HTTP Request
@@ -851,24 +893,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of CronJob
HTTP Request
@@ -926,8 +972,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -958,24 +1012,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
read the specified CronJob
HTTP Request
@@ -1043,24 +1101,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
list or watch objects of kind CronJob
HTTP Request
@@ -1118,8 +1180,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -1148,24 +1218,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
list or watch objects of kind CronJob
HTTP Request
@@ -1208,8 +1282,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -1238,24 +1320,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch changes to an object of kind CronJob
HTTP Request
@@ -1317,8 +1403,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -1347,24 +1441,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch individual changes to a list of CronJob
HTTP Request
@@ -1422,8 +1520,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -1452,24 +1558,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch individual changes to a list of CronJob
HTTP Request
@@ -1512,8 +1622,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of DaemonSet
HTTP Request
@@ -2651,8 +2804,16 @@ orphanDependents: false
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -2683,23 +2844,29 @@ orphanDependents: false
$ kubectl get daemonset daemonset-example -o json
+
curl Command (requires kubectl proxy to be running)
-$ kubectl proxy
-$ curl -X GET http://127.0.0.1:8001/apis/apps/v1/namespaces/default/daemonsets/daemonset-example
+$ kubectl proxy
+$ curl -X GET http://127.0.0.1:8001/apis/apps/v1/namespaces/default/daemonsets/daemonset-example
+
Output
+
+
Response Body
+
+
read the specified DaemonSet
HTTP Request
@@ -2767,24 +2934,28 @@ $ curl -X GET http://
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
list or watch objects of kind DaemonSet
HTTP Request
@@ -2842,8 +3013,16 @@ $ curl -X GET http://
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -2872,24 +3051,28 @@ $ curl -X GET http://
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
list or watch objects of kind DaemonSet
HTTP Request
@@ -2932,8 +3115,16 @@ $ curl -X GET http://
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -2962,24 +3153,28 @@ $ curl -X GET http://
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch changes to an object of kind DaemonSet
HTTP Request
@@ -3041,8 +3236,16 @@ $ curl -X GET http://
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -3071,24 +3274,28 @@ $ curl -X GET http://
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch individual changes to a list of DaemonSet
HTTP Request
@@ -3146,8 +3353,16 @@ $ curl -X GET http://
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -3176,24 +3391,28 @@ $ curl -X GET http://
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch individual changes to a list of DaemonSet
HTTP Request
@@ -3236,8 +3455,16 @@ $ curl -X GET http://
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. Defaults to 25%. Example: when this is set to 30%, the new RC can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new RC can be scaled up further, ensuring that total number of pods running at any time during the update is at most 130% of desired pods.
+||||||| merged common ancestors
+
maxSurge
+
The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. Defaults to 25%. Example: when this is set to 30%, the new RC can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new RC can be scaled up further, ensuring that total number of pods running at any time during the update is atmost 130% of desired pods.
+=======
+
maxSurge
+
The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. Defaults to 25%. Example: when this is set to 30%, the new RC can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new RC can be scaled up further, ensuring that total number of pods running at any time during the update is at most 130% of desired pods.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of Deployment
HTTP Request
@@ -4566,8 +4840,16 @@ orphanDependents: false
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
curl Command (requires kubectl proxy to be running)
@@ -4827,6 +5116,7 @@ $ kubectl get deployment -o json
$ kubectl proxy$ curl -X GET 'http://127.0.0.1:8001/apis/apps/v1/namespaces/default/deployments'
+
Output
@@ -4973,6 +5263,8 @@ $
kubectl proxy
}
]
}
+
+
Response Body
@@ -5119,6 +5411,8 @@ $ kubectl proxy
}
]
}
+
+
list or watch objects of kind Deployment
HTTP Request
@@ -5176,8 +5470,16 @@ $ kubectl proxy
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -5206,24 +5508,28 @@ $ kubectl proxy
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
list or watch objects of kind Deployment
HTTP Request
@@ -5266,8 +5572,16 @@ $ kubectl proxy
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -5296,6 +5610,7 @@ $ kubectl proxy
$ kubectl get deployment deployment-example --watch -o json
+
curl Command (requires kubectl proxy to be running)
@@ -5303,6 +5618,7 @@ $ kubectl get deployment deployment-example
$ kubectl proxy$ curl -X GET 'http://127.0.0.1:8001/apis/apps/v1/watch/namespaces/default/deployments/deployment-example'
+
Output
@@ -5382,6 +5698,7 @@ $ kubectl proxy
}
}
}
+
Response Body
@@ -5461,6 +5778,7 @@ $ kubectl proxy
}
}
}
+
watch changes to an object of kind Deployment
HTTP Request
@@ -5522,8 +5840,16 @@ $ kubectl proxy
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -5552,24 +5878,28 @@ $ kubectl proxy
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch individual changes to a list of Deployment
HTTP Request
@@ -5627,8 +5957,16 @@ $ kubectl proxy
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -5657,24 +5995,28 @@ $ kubectl proxy
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch individual changes to a list of Deployment
HTTP Request
@@ -5717,8 +6059,16 @@ $ kubectl proxy
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -5749,24 +6099,28 @@ $ kubectl proxy
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update status of the specified Deployment
HTTP Request
@@ -5841,24 +6195,28 @@ $ kubectl proxy
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
read status of the specified Deployment
HTTP Request
@@ -6094,24 +6452,28 @@ $ kubectl proxy
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace scale of the specified Deployment
HTTP Request
@@ -6290,24 +6652,28 @@ $ kubectl proxy
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
read scale of the specified Deployment
HTTP Request
@@ -6367,24 +6733,28 @@ $ kubectl proxy
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace scale of the specified Deployment
HTTP Request
@@ -6463,24 +6833,28 @@ $ kubectl proxy
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update scale of the specified Deployment
HTTP Request
@@ -6572,6 +6946,8 @@ apiVersion: batch/v1
args: ["-Mbignum=bpi", "-wle", "print bpi(2000)"]
# Do not restart containers after they exit restartPolicy: Never
+
+
Job Config to print pi up to 2000 digits (then exit).
@@ -6594,6 +6970,8 @@ apiVersion: batch/v1
args: ["-Mbignum=bpi", "-wle", "print bpi(2000)"]
# Do not restart containers after they exit restartPolicy: Never
+
+
=======
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+=======
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of Job
HTTP Request
@@ -7353,8 +7768,16 @@ orphanDependents: false
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-$ kubectl get job -o json
+$ kubectl get job -o json
+
curl Command (requires kubectl proxy to be running)
@@ -7588,6 +8016,7 @@ $ kubectl get job -o json
$ kubectl proxy$ curl -X GET 'http://127.0.0.1:8001/apis/batch/v1/namespaces/default/jobs'
+
Output
@@ -7657,6 +8086,7 @@ $ kubectl proxy
}
]
}
+
Response Body
@@ -7726,6 +8156,7 @@ $ kubectl proxy
}
]
}
+
list or watch objects of kind Job
HTTP Request
@@ -7783,8 +8214,16 @@ $ kubectl proxy
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -7813,24 +8252,28 @@ $ kubectl proxy
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
list or watch objects of kind Job
HTTP Request
@@ -7873,8 +8316,16 @@ $ kubectl proxy
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -7902,7 +8353,8 @@ $ kubectl proxy
kubectl Command
-$ kubectl get job example-job --watch -o json
+$ kubectl get job example-job --watch -o json
+
curl Command (requires kubectl proxy to be running)
@@ -7910,6 +8362,7 @@ $ kubectl get job example-job
$ kubectl proxy$ curl -X GET 'http://127.0.0.1:8001/apis/batch/v1/watch/namespaces/default/jobs/example-job'
+
Output
@@ -7976,6 +8429,7 @@ $
kubectl proxy
}
}
}
+
Response Body
@@ -8042,6 +8496,7 @@ $ kubectl proxy
}
}
}
+
watch changes to an object of kind Job
HTTP Request
@@ -8103,8 +8558,16 @@ $ kubectl proxy
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -8133,24 +8596,28 @@ $ kubectl proxy
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch individual changes to a list of Job
HTTP Request
@@ -8208,8 +8675,16 @@ $ kubectl proxy
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -8238,24 +8713,28 @@ $ kubectl proxy
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch individual changes to a list of Job
HTTP Request
@@ -8298,8 +8777,16 @@ $ kubectl proxy
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
List of containers belonging to the pod. Containers cannot currently be added or removed. There must be at least one container in a Pod. Cannot be updated.
Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy. This is an alpha feature introduced in v1.9 and CustomPodDNS feature gate must be enabled to use it.
Set DNS policy for the pod. Defaults to "ClusterFirst". Valid values are 'ClusterFirstWithHostNet', 'ClusterFirst', 'Default' or 'None'. DNS parameters given in DNSConfig will be merged with the policy selected with DNSPolicy. To have DNS options set along with hostNetwork, you have to specify DNS policy explicitly to 'ClusterFirstWithHostNet'.
+||||||| merged common ancestors
+
dnsPolicy string
+
Set DNS policy for the pod. Defaults to "ClusterFirst". Valid values are 'ClusterFirstWithHostNet', 'ClusterFirst', 'Default' or 'None'. DNS parameters given in DNSConfig will be merged with the policy selected with DNSPolicy. To have DNS options set along with hostNetwork, you have to specify DNS policy explicitly to 'ClusterFirstWithHostNet'. Note that 'None' policy is an alpha feature introduced in v1.9 and CustomPodDNS feature gate must be enabled to use it.
+=======
+
dnsPolicy string
+
Set DNS policy for the pod. Defaults to "ClusterFirst". Valid values are 'ClusterFirstWithHostNet', 'ClusterFirst', 'Default' or 'None'. DNS parameters given in DNSConfig will be merged with the policy selected with DNSPolicy. To have DNS options set along with hostNetwork, you have to specify DNS policy explicitly to 'ClusterFirstWithHostNet'.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
hostAliases HostAlias array patch type: merge patch merge key: ip
@@ -8763,8 +9282,16 @@ Appears In:
The priority value. Various system components use this field to find the priority of the pod. When Priority Admission Controller is enabled, it prevents users from setting this field. The admission controller populates this field from PriorityClassName. The higher the value, the higher the priority.
If specified, indicates the pod's priority. "system-node-critical" and "system-cluster-critical" are two special keywords which indicate the highest priorities with the former being the highest priority. Any other name must be defined by creating a PriorityClass object with that name. If not specified, the pod priority will be default or zero if there is no default.
+||||||| merged common ancestors
+
priorityClassName string
+
If specified, indicates the pod's priority. "SYSTEM" is a special keyword which indicates the highest priority. Any other name must be defined by creating a PriorityClass object with that name. If not specified, the pod priority will be default or zero if there is no default.
+=======
+
priorityClassName string
+
If specified, indicates the pod's priority. "system-node-critical" and "system-cluster-critical" are two special keywords which indicate the highest priorities with the former being the highest priority. Any other name must be defined by creating a PriorityClass object with that name. If not specified, the pod priority will be default or zero if there is no default.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Share a single process namespace between all of the containers in a pod. When this is set containers will be able to view and signal processes from other containers in the same pod, and the first process in each container will not be assigned PID 1. HostPID and ShareProcessNamespace cannot both be set. Optional: Default to false. This field is alpha-level and is honored only by servers that enable the PodShareProcessNamespace feature.
subdomain string
+||||||| merged common ancestors
+
subdomain string
+=======
+
shareProcessNamespace boolean
+
Share a single process namespace between all of the containers in a pod. When this is set containers will be able to view and signal processes from other containers in the same pod, and the first process in each container will not be assigned PID 1. HostPID and ShareProcessNamespace cannot both be set. Optional: Default to false. This field is alpha-level and is honored only by servers that enable the PodShareProcessNamespace feature.
+
+
+
subdomain string
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
If specified, the fully qualified Pod hostname will be "<hostname>.<subdomain>.<pod namespace>.svc.<cluster domain>". If not specified, the pod will not have a domainname at all.
@@ -8845,11 +9382,21 @@ Appears In:
A human readable message indicating details about why the pod is in this condition.
nominatedNodeName is set only when this pod preempts other pods on the node, but it cannot be scheduled right away as preemption victims receive their graceful termination periods. This field does not guarantee that the pod will be scheduled on this node. Scheduler may decide to place the pod elsewhere if other nodes become available sooner. Scheduler may also decide to give the resources on this node to a higher priority pod that is created after preemption. As a result, this field may be different than PodSpec.nodeName when the pod is scheduled.
phase string
+||||||| merged common ancestors
+
phase string
+=======
+
nominatedNodeName string
+
nominatedNodeName is set only when this pod preempts other pods on the node, but it cannot be scheduled right away as preemption victims receive their graceful termination periods. This field does not guarantee that the pod will be scheduled on this node. Scheduler may decide to place the pod elsewhere if other nodes become available sooner. Scheduler may also decide to give the resources on this node to a higher priority pod that is created after preemption. As a result, this field may be different than PodSpec.nodeName when the pod is scheduled.
+
+
+
phase string
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Replace
@@ -9331,24 +9918,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified Pod
HTTP Request
@@ -9461,24 +10052,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a Pod
HTTP Request
@@ -9547,8 +10142,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
+
+
list or watch objects of kind Pod
+
HTTP Request
+
GET /api/v1/namespaces/{namespace}/pods
+
Path Parameters
+
+
+
+
Parameter
+
Description
+
+
+
+
+
namespace
+
object name and auth scope, such as for teams and projects
+
+
+
+
Query Parameters
+
+
+
+
Parameter
+
Description
+
+
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -9633,7 +10464,7 @@ Appears In:
timeoutSeconds
-
Timeout for the list/watch call.
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
watch
@@ -9664,24 +10495,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
export
@@ -9783,24 +10634,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of Pod
HTTP Request
@@ -9858,8 +10713,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
list or watch objects of kind Pod
HTTP Request
@@ -10148,8 +11025,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Path is the URL path to use for the current proxy request to pod.
+||||||| merged common ancestors
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -12990,24 +14819,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
connect PUT requests to proxy of Pod
HTTP Request
@@ -13074,24 +14907,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
object name and auth scope, such as for teams and projects
+
+
+
+
Query Parameters
+
+
+
+
Parameter
+
Description
+
+
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
namespace
+
object name and auth scope, such as for teams and projects
+
+
+
+
Query Parameters
+
+
+
+
Parameter
+
Description
+
+
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
namespace
@@ -13136,24 +15067,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
object name and auth scope, such as for teams and projects
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
path
@@ -13335,24 +15290,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
read log of the specified Pod
HTTP Request
@@ -13410,8 +15369,16 @@ Appears In:
A relative time in seconds before the current time from which to show logs. If this value precedes the time a pod was started, only logs since the pod start will be returned. If this value is in the future, no logs will be returned. Only one of sinceSeconds or sinceTime may be specified.
If set, the number of lines from the end of the logs to show. If not specified, logs are shown from the creation of the container or sinceSeconds or sinceTime
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Minimum number of seconds for which a newly created 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)
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update status of the specified ReplicaSet
HTTP Request
@@ -14824,24 +17001,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
read status of the specified ReplicaSet
HTTP Request
@@ -14878,6 +17059,74 @@ Appears In:
pretty
If 'true', then the output is pretty printed.
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
+=======
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Response
@@ -14901,24 +17150,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace status of the specified ReplicaSet
HTTP Request
@@ -14955,20 +17208,15 @@ Appears In:
pretty
If 'true', then the output is pretty printed.
-
-
-
Body Parameters
-
-
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
-
Parameter
-
Description
+
exact
+
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
List All Namespaces
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
Output
+
+
+Coming Soon
+
+
+
Response Body
+
+
+Coming Soon
+
+
list or watch objects of kind ReplicationController
+
HTTP Request
+
GET /api/v1/replicationcontrollers
+
Query Parameters
+
+
+
+
Parameter
+
Description
+
+
+
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
+
+
+
Response
+
+
+
+
Code
+
Description
+
+
+
+=======
+
+
+
List All Namespaces
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
+
+
list or watch objects of kind ReplicationController
+
HTTP Request
+
GET /api/v1/replicationcontrollers
+
Query Parameters
+
+
+
+
Parameter
+
Description
+
+
+
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
read scale of the specified ReplicaSet
HTTP Request
@@ -15053,6 +17702,34 @@ Appears In:
pretty
If 'true', then the output is pretty printed.
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
+=======
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Response
@@ -15076,24 +17753,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace scale of the specified ReplicaSet
HTTP Request
@@ -15130,9 +17811,133 @@ Appears In:
pretty
If 'true', then the output is pretty printed.
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+=======
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -15172,24 +18049,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update scale of the specified ReplicaSet
HTTP Request
@@ -15266,24 +18147,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
read scale of the specified ReplicaSet
HTTP Request
@@ -15343,24 +18228,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace scale of the specified ReplicaSet
HTTP Request
@@ -15439,24 +18328,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update scale of the specified ReplicaSet
HTTP Request
@@ -15530,6 +18423,7 @@ Appears In:
ReplicationController Config to run 3 nginx instances.
+=======
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Patch
@@ -15838,24 +18995,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified ReplicationController
HTTP Request
@@ -15930,24 +19091,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified ReplicationController
HTTP Request
@@ -16026,24 +19191,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a ReplicationController
HTTP Request
@@ -16130,24 +19299,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of ReplicationController
HTTP Request
@@ -16205,8 +19378,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -16237,24 +19418,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
read the specified ReplicationController
HTTP Request
@@ -16322,24 +19507,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
list or watch objects of kind ReplicationController
HTTP Request
@@ -16397,8 +19586,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -16427,24 +19624,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
list or watch objects of kind ReplicationController
HTTP Request
@@ -16487,8 +19688,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -16517,24 +19726,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch changes to an object of kind ReplicationController
HTTP Request
@@ -16596,8 +19809,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -16626,24 +19847,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch individual changes to a list of ReplicationController
HTTP Request
@@ -16701,8 +19926,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
watch
@@ -16731,24 +19964,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch individual changes to a list of ReplicationController
HTTP Request
@@ -16791,8 +20028,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
Write Operations
+
See supported operations below...
+
Create
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
Output
+
+
+Coming Soon
+
+
+
Response Body
+
+
+Coming Soon
+
+
create Endpoints
+
HTTP Request
+
POST /api/v1/namespaces/{namespace}/endpoints
+
Path Parameters
+
+
+=======
+
+
+
Write Operations
+
See supported operations below...
+
Create
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
+
+
create Endpoints
+
HTTP Request
+
POST /api/v1/namespaces/{namespace}/endpoints
+
Path Parameters
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
serviceName string
serviceName is the name of the service that governs this StatefulSet. This service must exist before the StatefulSet, and is responsible for the network identity of the set. Pods get DNS/hostnames that follow the pattern: pod-specific-string.serviceName.default.svc.cluster.local where "pod-specific-string" is managed by the StatefulSet controller.
@@ -17759,24 +21106,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
read scale of the specified ReplicationController
HTTP Request
@@ -17842,24 +21193,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace scale of the specified ReplicationController
volumeClaimTemplates is a list of claims that pods are allowed to reference. The StatefulSet controller is responsible for mapping network identities to claims in a way that maintains the identity of a pod. Every claim in this list must have at least one matching (by name) volumeMount in one container in the template. A claim in this list takes precedence over any volumes in the template, with the same name.
@@ -18219,6 +21597,13 @@ Appears In:
Field
Description
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -18301,24 +21686,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a StatefulSet
HTTP Request
@@ -18407,24 +21796,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -18505,24 +21954,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -18607,24 +22076,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -18717,24 +22198,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of StatefulSet
HTTP Request
@@ -18792,8 +22277,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
export
@@ -19093,24 +22606,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -19617,6 +23250,7 @@ Workloads can be accessed via proxy through the api master using the kubec
Discovery and Load Balancing resources are responsible for stitching your workloads together into an accessible Loadbalanced Service. By default,
Workloads are only accessible within the cluster, and they must be exposed externally using a either
@@ -19631,6 +23265,75 @@ Workloads can be accessed via proxy through the api master using the kubec
Endpoints v1 core
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
Read Operations
+
See supported operations below...
+
Read
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
Output
+
+
+Coming Soon
+
+
+
Response Body
+
+
+Coming Soon
+
+
read the specified Ingress
+
HTTP Request
+
GET /apis/extensions/v1beta1/namespaces/{namespace}/ingresses/{name}
+
Path Parameters
+=======
+
Read Operations
+
See supported operations below...
+
Read
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
+
+
read the specified Ingress
+
HTTP Request
+
GET /apis/extensions/v1beta1/namespaces/{namespace}/ingresses/{name}
+
Path Parameters
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -19723,24 +23426,28 @@ Workloads can be accessed via proxy through the api master using the kubec
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch individual changes to a list of StatefulSet
HTTP Request
@@ -19783,8 +23490,16 @@ Workloads can be accessed via proxy through the api master using the kubec
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -19955,24 +23690,28 @@ Workloads can be accessed via proxy through the api master using the kubec
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
read status of the specified StatefulSet
HTTP Request
@@ -20009,6 +23748,34 @@ Workloads can be accessed via proxy through the api master using the kubec
pretty
If 'true', then the output is pretty printed.
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
+=======
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Response
@@ -20038,24 +23805,28 @@ Workloads can be accessed via proxy through the api master using the kubec
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace status of the specified StatefulSet
HTTP Request
@@ -20098,8 +23869,24 @@ Workloads can be accessed via proxy through the api master using the kubec
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -20142,24 +23929,28 @@ Workloads can be accessed via proxy through the api master using the kubec
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
read scale of the specified StatefulSet
HTTP Request
@@ -20196,6 +23987,34 @@ Workloads can be accessed via proxy through the api master using the kubec
pretty
If 'true', then the output is pretty printed.
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
+=======
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Response
@@ -20229,24 +24048,28 @@ Workloads can be accessed via proxy through the api master using the kubec
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace scale of the specified StatefulSet
HTTP Request
@@ -20316,24 +24139,28 @@ Workloads can be accessed via proxy through the api master using the kubec
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
list or watch objects of kind Endpoints
HTTP Request
@@ -20383,24 +24210,28 @@ Workloads can be accessed via proxy through the api master using the kubec
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
list or watch objects of kind Endpoints
HTTP Request
@@ -20459,14 +24290,106 @@ Workloads can be accessed via proxy through the api master using the kubec
+kind: Service
+apiVersion: v1
+metadata:
+ # Unique key of the Service instance
+ name: service-example
+spec:
+ ports:
+ # Accept traffic sent to port 80
+ - name: http
+ port: 80
+ targetPort: 80
+ selector:
+ # Loadbalance traffic across Pods matching
+ # this label selector
+ app: nginx
+ # Create an HA proxy in the cloud provider
+ # with an External IP address - *Only supported
+ # by some cloud providers*
+ type: LoadBalancer
+=======
+
+kind: Service
+apiVersion: v1
+metadata:
+ # Unique key of the Service instance
+ name: service-example
+spec:
+ ports:
+ # Accept traffic sent to port 80
+ - name: http
+ port: 80
+ targetPort: 80
+ selector:
+ # Loadbalance traffic across Pods matching
+ # this label selector
+ app: nginx
+ # Create an HA proxy in the cloud provider
+ # with an External IP address - *Only supported
+ # by some cloud providers*
+ type: LoadBalancer
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
curl Command (requires kubectl proxy to be running)
+kind: Service
+apiVersion: v1
+metadata:
+ # Unique key of the Service instance
+ name: service-example
+spec:
+ ports:
+ # Accept traffic sent to port 80
+ - name: http
+ port: 80
+ targetPort: 80
+ selector:
+ # Loadbalance traffic across Pods matching
+ # this label selector
+ app: nginx
+ # Create an HA proxy in the cloud provider
+ # with an External IP address - *Only supported
+ # by some cloud providers*
+ type: LoadBalancer
+=======
+
+kind: Service
+apiVersion: v1
+metadata:
+ # Unique key of the Service instance
+ name: service-example
+spec:
+ ports:
+ # Accept traffic sent to port 80
+ - name: http
+ port: 80
+ targetPort: 80
+ selector:
+ # Loadbalance traffic across Pods matching
+ # this label selector
+ app: nginx
+ # Create an HA proxy in the cloud provider
+ # with an External IP address - *Only supported
+ # by some cloud providers*
+ type: LoadBalancer
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Output
@@ -20642,25 +24565,169 @@ Workloads can be accessed via proxy through the api master using the kubec
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
@@ -20983,6 +25414,36 @@ Workloads can be accessed via proxy through the api master using the kubec
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+||||||| merged common ancestors
+=======
+
+
gracePeriodSeconds
+
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
+
+
+
orphanDependents
+
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+
+
+
propagationPolicy
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
Coming Soon
+||||||| merged common ancestors
+$ kubectl get service -o json
+=======
+$ kubectl get service -o json
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
curl Command (requires kubectl proxy to be running)
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -21282,24 +26007,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -21373,25 +26118,217 @@ Appears In:
kubectl Command
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
Coming Soon
+||||||| merged common ancestors
+$ kubectl get service deployment-example --watch -o json
+=======
+$ kubectl get service deployment-example --watch -o json
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
curl Command (requires kubectl proxy to be running)
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -21470,24 +26423,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -21574,24 +26539,28 @@ Appears In:
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of Endpoints
HTTP Request
@@ -21649,8 +26618,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
Get Proxy
+=======
+
CONFIG & STORAGE
+
Config and Storage resources are responsible for injecting data into your applications and persisting data externally to your container.
+
Common resource types:
+
+
ConfigMaps for providing text key value pairs injected into the application through environment variables, command line arguments, or files
+
Secrets for providing binary data injected into the application through files
+
Volumes for providing a filesystem external to the Container. Maybe shared across Containers within the same Pod and have a lifetime persisting beyond a Container or Pod.
+
+
+
+
ConfigMap v1 core
+
+
+
+
Group
+
Version
+
Kind
+
+
+
+
+
Core
+
v1
+
ConfigMap
+
+
+
+
ConfigMap holds configuration data for pods to consume.
BinaryData contains the binary data. Each key must consist of alphanumeric characters, '-', '_' or '.'. BinaryData can contain byte sequences that are not in the UTF-8 range. The keys stored in BinaryData must not overlap with the ones in the Data field, this is enforced during validation process. Using this field will require 1.10+ apiserver and kubelet.
+
+
+
data object
+
Data contains the configuration data. Each key must consist of alphanumeric characters, '-', '_' or '.'. Values with non-UTF-8 byte sequences must use the BinaryData field. The keys stored in Data must not overlap with the keys in the BinaryData field, this is enforced during validation process.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -23227,74 +28585,17 @@ Appears In:
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
@@ -23566,6 +29110,28 @@ $ kubectl get
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
object name and auth scope, such as for teams and projects
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
path
+
path to the resource
+
+=======
Query Parameters
@@ -23643,6 +29262,35 @@ $ kubectl get
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
gracePeriodSeconds
+
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
+
+
+
orphanDependents
+
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+
+
+
propagationPolicy
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -23677,6 +29325,13 @@ $ kubectl get
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+||||||| merged common ancestors
+
name
+
name of the Service
+
+
+
namespace
+
object name and auth scope, such as for teams and projects
+=======
+
namespace
+
object name and auth scope, such as for teams and projects
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
includeUninitialized
If true, partially initialized resources are included in the response.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
object name and auth scope, such as for teams and projects
+||||||| merged common ancestors
+
namespace
+
object name and auth scope, such as for teams and projects
+=======
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
path
+
path to the resource
+
+=======
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+
Config and Storage resources are responsible for injecting data into your applications and persisting data externally to your container.
+
Common resource types:
+
+
ConfigMaps for providing text key value pairs injected into the application through environment variables, command line arguments, or files
+
Secrets for providing binary data injected into the application through files
+
Volumes for providing a filesystem external to the Container. Maybe shared across Containers within the same Pod and have a lifetime persisting beyond a Container or Pod.
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
+
+
watch changes to an object of kind ConfigMap
+
HTTP Request
+
GET /api/v1/watch/namespaces/{namespace}/configmaps/{name}
+
Path Parameters
@@ -24018,11 +30088,11 @@ $ kubectl get
-
name
-
name of the Ingress
+
name
+
name of the ConfigMap
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -24037,23 +30107,40 @@ $ kubectl get
-
pretty
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
If 'true', then the output is pretty printed.
-
-
-
Body Parameters
-
-
-
Parameter
-
Description
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
curl Command (requires kubectl proxy to be running)
Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
+
+
watch individual changes to a list of ConfigMap
+
HTTP Request
+
GET /api/v1/watch/namespaces/{namespace}/configmaps
+
Path Parameters
+
+
+
+
Parameter
+
Description
+
+
+
+
+
namespace
+
object name and auth scope, such as for teams and projects
+
+
+
+
Query Parameters
+
+
+
+
Parameter
+
Description
+
+
+
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
+
+
watch individual changes to a list of ConfigMap
+
HTTP Request
+
GET /api/v1/watch/configmaps
+
Query Parameters
+
+
+
+
Parameter
+
Description
+
+
+
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Data contains the secret data. Each key must consist of alphanumeric characters, '-', '_' or '.'. The serialized form of the secret data is a base64 encoded string, representing the arbitrary (possibly non-string) data value here. Described in https://tools.ietf.org/html/rfc4648#section-4
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+
+
stringData object
+
stringData allows specifying non-binary secret data in string form. It is provided as a write-only convenience method. All keys and values are merged into the data field on write, overwriting any existing values. It is never output when reading from the API.
+
+
+
type string
+
Used to facilitate programmatic handling of secret data.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
=======
Status Operations
@@ -24104,13 +30555,16 @@ $ kubectl get
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
Service Config to load balance traffic across all Pods with the app=nginx label. Receives on and sends to port 80. Exposes an externally accessible endpoint.
@@ -24160,6 +30614,47 @@ spec:
# by some cloud providers*
type: LoadBalancer
+||||||| merged common ancestors
+
create a ConfigMap
+
HTTP Request
+
POST /api/v1/namespaces/{namespace}/configmaps
+
Path Parameters
+
+
+
+
Parameter
+
Description
+
+
+
+
+
namespace
+
object name and auth scope, such as for teams and projects
+
+
+
+
Query Parameters
+=======
+
create a Secret
+
HTTP Request
+
POST /api/v1/namespaces/{namespace}/secrets
+
Path Parameters
+
+
+
+
Parameter
+
Description
+
+
+
+
+
namespace
+
object name and auth scope, such as for teams and projects
+
+
+
+
Query Parameters
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
AutomountServiceAccountToken indicates whether pods running as this service account should have an API token automatically mounted. Can be overridden at the pod level.
ImagePullSecrets is a list of references to secrets in the same namespace to use for pulling any images in pods that reference this ServiceAccount. ImagePullSecrets are distinct from Secrets because Secrets can be mounted in the pod, but ImagePullSecrets are only accessed by the kubelet. More info: https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod
List of egress rules to be applied to the selected pods. Outgoing traffic is allowed if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic matches at least one egress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy limits all outgoing traffic (and serves solely to ensure that the pods it selects are isolated by default). This field is beta-level in 1.8
List of ingress rules to be applied to the selected pods. Traffic is allowed to a pod if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic source is the pod's local node, OR if the traffic matches at least one ingress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy does not allow any traffic (and serves solely to ensure that the pods it selects are isolated by default)
Selects the pods to which this NetworkPolicy object applies. The array of ingress rules is applied to any pods selected by this field. Multiple network policies can select the same set of pods. In this case, the ingress rules for each are combined additively. This field is NOT optional and follows standard label selector semantics. An empty podSelector matches all pods in this namespace.
+
+
+
policyTypes string array
+
List of rule types that the NetworkPolicy relates to. Valid options are Ingress, Egress, or Ingress,Egress. If this field is not specified, it will default based on the existence of Ingress or Egress rules; policies that contain an Egress section are assumed to affect Egress, and all policies (whether or not they contain an Ingress section) are assumed to affect Ingress. If you want to write an egress-only policy, you must explicitly specify policyTypes [ "Egress" ]. Likewise, if you want to write a policy that specifies that no egress is allowed, you must specify a policyTypes value that include "Egress" (since such a policy would not include an Egress section and would otherwise default to just [ "Ingress" ]). This field is beta-level in 1.8
+
+
+
+
NetworkPolicyList v1 networking
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Path Parameters
@@ -60650,8 +95562,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
GET /api/v1/namespaces/{namespace}/serviceaccounts
+=======
+
GET /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Path Parameters
@@ -60860,8 +95844,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Query Parameters
@@ -60956,8 +95976,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
namespace
@@ -61071,8 +96135,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
GET /api/v1/watch/namespaces/{namespace}/resourcequotas
+||||||| merged common ancestors
+
GET /api/v1/watch/namespaces/{namespace}/serviceaccounts
+=======
+
GET /apis/networking.k8s.io/v1/watch/namespaces/{namespace}/networkpolicies
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Path Parameters
@@ -61182,8 +96276,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
GET /apis/networking.k8s.io/v1/watch/networkpolicies
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Query Parameters
@@ -61278,8 +96402,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
a map of client CIDR to server address that is serving this group. This is to help clients reach servers in the most network-efficient way possible. Clients can use the appropriate server address as per the CIDR that they match. In case of multiple matches, clients should use the longest matching CIDR. The server returns only those CIDRs that it thinks that the client can match. For example: the master will return an internal IP CIDR only, if the client reaches the server using an internal IP. Server looks at X-Forwarded-For header or X-Real-Ip header or request.RemoteAddr (in that order) to get the client IP.
NonResourceAttributes describes information for a non-resource access request
+=======
+
categories string array
+
categories is a list of the grouped resources this resource belongs to (e.g. 'all')
+
+
+
group string
+
group is the preferred group of the resource. Empty implies the group of the containing resource list. For subresources, this may have a different value, for example: Scale".
+
+
+
kind string
+
kind is the kind for the resource (e.g. 'Foo' is the kind for a resource 'foo')
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
object name and auth scope, such as for teams and projects
+||||||| merged common ancestors
+
user string
+
User is the user you're testing for. If you specify "User" but not "Groups", then is it interpreted as "What if User were not a member of any groups
+=======
+
shortNames string array
+
shortNames is a list of suggested short names of the resource.
+
+
+
singularName string
+
singularName is the singular name of the resource. This allows clients to handle plural and singular opaquely. The singularName is more correct for reporting status on a single item and both singular and plural are allowed from the kubectl CLI interface.
+
+
+
verbs string array
+
verbs is a list of supported kube verbs (this includes get, list, watch, create, update, patch, delete, deletecollection, and proxy)
+
+
+
version string
+
version is the preferred version of the resource. Empty implies the version of the containing resource list For subresources, this may have a different value, for example: v1 (while inside a v1beta1 version of the core resource's group)".
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Allowed is required. True if the action would be allowed, false otherwise.
+
+
+
denied boolean
+
Denied is optional. True if the action would be denied, otherwise false. If both allowed is false and denied is false, then the authorizer has no opinion on whether to authorize the action. Denied may not be true if Allowed is true.
EvaluationError is an indication that some error occurred during the authorization check. It is entirely possible to get an error and be able to continue determine authorization status in spite of it. For instance, RBAC can be missing a role, but enough roles are still present and bound to reason about the request.
Role is a namespaced, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding.
+
TokenReview attempts to authenticate a token to a known user. Note: TokenReview requests may be cached by the webhook token authenticator plugin in the kube-apiserver.
a map of client CIDR to server address that is serving this group. This is to help clients reach servers in the most network-efficient way possible. Clients can use the appropriate server address as per the CIDR that they match. In case of multiple matches, clients should use the longest matching CIDR. The server returns only those CIDRs that it thinks that the client can match. For example: the master will return an internal IP CIDR only, if the client reaches the server using an internal IP. Server looks at X-Forwarded-For header or X-Real-Ip header or request.RemoteAddr (in that order) to get the client IP.
+
+
+
versions string array
+
versions are the api versions that are available.
+
+
+
+
AWSElasticBlockStoreVolumeSource v1 core
+
+
+
+
Group
+
Version
+
Kind
+
+
+
+
+
Core
+
v1
+
AWSElasticBlockStoreVolumeSource
+
+
+
+
Represents a Persistent Disk resource in AWS.
+
An AWS EBS disk must exist before mounting to a container. The disk must also be in the same AWS zone as the kubelet. An AWS EBS disk can only be mounted as read/write once. AWS EBS volumes support ownership management and SELinux relabeling.
+
+
+
+
+
+
Field
+
Description
+
+
+
+
+
fsType string
+
Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
User is the UserInfo associated with the provided token.
+=======
+
partition integer
+
The partition in the volume that you want to mount. If omitted, the default is to mount by volume name. Examples: For volume /dev/sda1, you specify the partition as "1". Similarly, the volume partition for /dev/sda is "0" (or you can leave the property empty).
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
ClusterRoleSelectors holds a list of selectors which will be used to find ClusterRoles and create the rules. If any of the selectors match, then the ClusterRole's permissions will be added
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
List of egress rules to be applied to the selected pods. Outgoing traffic is allowed if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic matches at least one egress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy limits all outgoing traffic (and serves solely to ensure that the pods it selects are isolated by default). This field is beta-level in 1.8
List of ingress rules to be applied to the selected pods. Traffic is allowed to a pod if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic source is the pod's local node, OR if the traffic matches at least one ingress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy does not allow any traffic (and serves solely to ensure that the pods it selects are isolated by default)
Selects the pods to which this NetworkPolicy object applies. The array of ingress rules is applied to any pods selected by this field. Multiple network policies can select the same set of pods. In this case, the ingress rules for each are combined additively. This field is NOT optional and follows standard label selector semantics. An empty podSelector matches all pods in this namespace.
+=======
+
Group
+
Version
+
Kind
+
+
+
+
+
extensions
+
v1beta1
+
AllowedFlexVolume
+
+
+
+
AllowedFlexVolume represents a single Flexvolume that is allowed to be used.
+
+
+
+
+
+
Field
+
Description
+
+
+
+
+
driver string
+
Driver is the name of the Flexvolume driver.
+
+
+
+
AllowedHostPath v1beta1 extensions
+
+
+
+
Group
+
Version
+
Kind
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
List of rule types that the NetworkPolicy relates to. Valid options are Ingress, Egress, or Ingress,Egress. If this field is not specified, it will default based on the existence of Ingress or Egress rules; policies that contain an Egress section are assumed to affect Egress, and all policies (whether or not they contain an Ingress section) are assumed to affect Ingress. If you want to write an egress-only policy, you must explicitly specify policyTypes [ "Egress" ]. Likewise, if you want to write a policy that specifies that no egress is allowed, you must specify a policyTypes value that include "Egress" (since such a policy would not include an Egress section and would otherwise default to just [ "Ingress" ]). This field is beta-level in 1.8
+=======
+
extensions
+
v1beta1
+
AllowedHostPath
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
is the path prefix that the host volume must match. It does not support *. Trailing slashes are trimmed when validating the path prefix with a host path. Examples: /foo would allow /foo, /foo/ and /foo/bar/foo would not allow /food or /etc/foo
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+=======
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
-
Parameter
-
Description
+
fsType string
+
Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified.
Expected values Shared: multiple blob disks per storage account Dedicated: single blob disk per storage account Managed: azure managed data disk (only in managed availability set). defaults to shared
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
ControllerPublishSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI ControllerPublishVolume and ControllerUnpublishVolume calls. This field is optional, and may be empty if no secret is required. If the secret object contains more than one secret, all secrets are passed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
-
-
-
Response
-
-
-
Code
-
Description
+
driver string
+
Driver is the name of the driver to use for this volume. Required.
Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
NodePublishSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodePublishVolume and NodeUnpublishVolume calls. This field is optional, and may be empty if no secret is required. If the secret object contains more than one secret, all secrets are passed.
NodeStageSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodeStageVolume and NodeStageVolume and NodeUnstageVolume calls. This field is optional, and may be empty if no secret is required. If the secret object contains more than one secret, all secrets are passed.
+
+
+
readOnly boolean
+
Optional: The value to pass to ControllerPublishVolumeRequest. Defaults to false (read/write).
+
+
+
volumeAttributes object
+
Attributes of the volume to publish.
+
+
+
volumeHandle string
+
VolumeHandle is the unique volume name returned by the CSI volume plugin’s CreateVolume to refer to the volume on all subsequent calls. Required.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+||||||| merged common ancestors
+
pretty
+
If 'true', then the output is pretty printed.
+
gracePeriodSeconds
+
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
+
+
+
orphanDependents
+
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+=======
+
add string array
+
Added capabilities
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+||||||| merged common ancestors
+
propagationPolicy
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+=======
+
drop string array
+
Removed capabilities
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+||||||| merged common ancestors
+
pretty
+
If 'true', then the output is pretty printed.
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
-
-
timeoutSeconds
-
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
-
-
watch
-
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
object name and auth scope, such as for teams and projects
+||||||| merged common ancestors
+
name
+
name of the NetworkPolicy
+
+
+
namespace
+
object name and auth scope, such as for teams and projects
+=======
+
Core
+
v1
+
CinderVolumeSource
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
-
Query Parameters
+
Represents a cinder volume resource in Openstack. A Cinder volume must exist before mounting to a container. The volume must also be in the same region as the kubelet. Cinder volumes support ownership management and SELinux relabeling.
object name and auth scope, such as for teams and projects
+||||||| merged common ancestors
+
namespace
+
object name and auth scope, such as for teams and projects
+=======
+
timeoutSeconds integer
+
timeoutSeconds specifies the seconds of ClientIP type session sticky time. The value must be >0 && <=86400(for 1 day) if ServiceAffinity == "ClientIP". Default value is 10800(for 3 hours).
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
If true, partially initialized resources are included in the response.
+||||||| merged common ancestors
+
pretty
+
If 'true', then the output is pretty printed.
-
labelSelector
-
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
limit
-
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
resourceVersion
-
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
-
-
timeoutSeconds
-
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
-
-
watch
-
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+=======
+
Core
+
v1
+
ComponentCondition
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+=======
+
error string
+
Condition error code for a component. For example, a health check error code.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+=======
+
message string
+
Message about the condition for a component. For example, information about a health check.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+||||||| merged common ancestors
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
If true, partially initialized resources are included in the response.
-
-
-
labelSelector
-
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
-
-
limit
-
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
-
-
pretty
-
If 'true', then the output is pretty printed.
-
-
-
resourceVersion
-
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
-
-
timeoutSeconds
-
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
-
-
watch
-
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+||||||| merged common ancestors
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+=======
+
optional boolean
+
Specify whether the ConfigMap must be defined
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+=======
+
Core
+
v1
+
ConfigMapKeySelector
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+=======
+
key string
+
The key to select.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
||||||| merged common ancestors
@@ -62571,87 +99505,254 @@ Appears In:
HTTP Request
GET /apis/rbac.authorization.k8s.io/v1/watch/namespaces/{namespace}/roles/{name}
Path Parameters
+||||||| merged common ancestors
+
Watch
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
Output
+
+
+Coming Soon
+
+
+
Response Body
+
+
+Coming Soon
+
+
watch changes to an object of kind NetworkPolicy
+
HTTP Request
+
GET /apis/networking.k8s.io/v1/watch/namespaces/{namespace}/networkpolicies/{name}
+
Path Parameters
+=======
+
Adapts a ConfigMap into a projected volume.
+
The contents of the target ConfigMap's Data field will be presented in a projected volume as files using the keys in the Data field as the file names, unless the items element is populated with specific mappings of keys to paths. Note that this is identical to a configmap volume source without the default mode.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
If unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+||||||| merged common ancestors
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
includeUninitialized
-
If true, partially initialized resources are included in the response.
-
-
-
labelSelector
-
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
-
-
limit
-
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
-
-
pretty
-
If 'true', then the output is pretty printed.
-
-
-
resourceVersion
-
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
-
-
timeoutSeconds
-
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
-
-
watch
-
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+=======
+
Core
+
v1
+
ConfigMapVolumeSource
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
-
Response
+
Adapts a ConfigMap into a volume.
+
The contents of the target ConfigMap's Data field will be presented in a volume as files using the keys in the Data field as the file names, unless the items element is populated with specific mappings of keys to paths. ConfigMap volumes support ownership management and SELinux relabeling.
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+||||||| merged common ancestors
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+=======
+
defaultMode integer
+
Optional: mode bits to use on created files by default. Must be a value between 0 and 0777. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
If unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+=======
+
optional boolean
+
Specify whether the ConfigMap or it's keys must be defined
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+||||||| merged common ancestors
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+=======
+
containerPort integer
+
Number of port to expose on the pod's IP address. This must be a valid port number, 0 < x < 65536.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
If true, partially initialized resources are included in the response.
@@ -62736,33 +99904,75 @@ Appears In:
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+=======
+
hostPort integer
+
Number of port to expose on the host. If specified, this must be a valid port number, 0 < x < 65536. If HostNetwork is specified, this must match ContainerPort. Most containers do not need this.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
name string
+
If specified, this must be an IANA_SVC_NAME and unique within the pod. Each named port in a pod must have a unique name. Name for the port that can be referred to by services.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
GET /apis/rbac.authorization.k8s.io/v1/watch/roles
Query Parameters
+||||||| merged common ancestors
+
Watch List All Namespaces
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
Output
+
+
+Coming Soon
+
+
+
Response Body
+
+
+Coming Soon
+
+
watch individual changes to a list of NetworkPolicy
+
HTTP Request
+
GET /apis/networking.k8s.io/v1/watch/networkpolicies
+
Query Parameters
+=======
+
ContainerState holds a possible state of container. Only one of its members may be specified. If none of them is specified, the default one is ContainerStateWaiting.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -62824,42 +100075,121 @@ Appears In:
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
-
-
timeoutSeconds
-
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
-
-
watch
-
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
RoleBinding references a role, but does not contain it. It can reference a Role in the same namespace or a ClusterRole in the global namespace. It adds who information via Subjects and namespace information by which namespace it exists in. RoleBindings in a given namespace only have effect in that namespace.
+||||||| merged common ancestors
+
APIGroup contains the name, the supported versions, and the preferred version of a group.
+=======
+
ContainerStateTerminated is a terminated state of a container.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
a map of client CIDR to server address that is serving this group. This is to help clients reach servers in the most network-efficient way possible. Clients can use the appropriate server address as per the CIDR that they match. In case of multiple matches, clients should use the longest matching CIDR. The server returns only those CIDRs that it thinks that the client can match. For example: the master will return an internal IP CIDR only, if the client reaches the server using an internal IP. Server looks at X-Forwarded-For header or X-Real-Ip header or request.RemoteAddr (in that order) to get the client IP.
RoleRef can reference a Role in the current namespace or a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.
categories is a list of the grouped resources this resource belongs to (e.g. 'all')
+
+
+
group string
+
group is the preferred group of the resource. Empty implies the group of the containing resource list. For subresources, this may have a different value, for example: Scale".
+
+
+
kind string
+
kind is the kind for the resource (e.g. 'Foo' is the kind for a resource 'foo')
+
+
+
name string
+
name is the plural name of the resource.
+
+
+
namespaced boolean
+
namespaced indicates if a resource is namespaced or not.
+
+
+
shortNames string array
+
shortNames is a list of suggested short names of the resource.
+
+
+
singularName string
+
singularName is the singular name of the resource. This allows clients to handle plural and singular opaquely. The singularName is more correct for reporting status on a single item and both singular and plural are allowed from the kubectl CLI interface.
+
+
+
verbs string array
+
verbs is a list of supported kube verbs (this includes get, list, watch, create, update, patch, delete, deletecollection, and proxy)
+=======
+
message string
+
Message regarding why the container is not yet running.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
version is the preferred version of the resource. Empty implies the version of the containing resource list For subresources, this may have a different value, for example: v1 (while inside a v1beta1 version of the core resource's group)".
+=======
+
reason string
+
(brief) reason the container is not yet running.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
a map of client CIDR to server address that is serving this group. This is to help clients reach servers in the most network-efficient way possible. Clients can use the appropriate server address as per the CIDR that they match. In case of multiple matches, clients should use the longest matching CIDR. The server returns only those CIDRs that it thinks that the client can match. For example: the master will return an internal IP CIDR only, if the client reaches the server using an internal IP. Server looks at X-Forwarded-For header or X-Real-Ip header or request.RemoteAddr (in that order) to get the client IP.
An AWS EBS disk must exist before mounting to a container. The disk must also be in the same AWS zone as the kubelet. An AWS EBS disk can only be mounted as read/write once. AWS EBS volumes support ownership management and SELinux relabeling.
+
+
+=======
+
CustomResourceDefinitionNames indicates the names to serve this CustomResourceDefinition
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore
+
+
+
partition integer
+
The partition in the volume that you want to mount. If omitted, the default is to mount by volume name. Examples: For volume /dev/sda1, you specify the partition as "1". Similarly, the volume partition for /dev/sda is "0" (or you can leave the property empty).
Categories is a list of grouped resources custom resources belong to (e.g. 'all')
+
+
+
kind string
+
Kind is the serialized kind of the resource. It is normally CamelCase and singular.
+
+
+
listKind string
+
ListKind is the serialized kind of the list for this resource. Defaults to <kind>List.
+
+
+
plural string
+
Plural is the plural name of the resource to serve. It must match the name of the CustomResourceDefinition-registration too: plural.group and it must be all lowercase.
+
+
+
shortNames string array
+
ShortNames are short names for the resource. It must be all lowercase.
+
+
+
singular string
+
Singular is the singular name of the resource. It must be all lowercase Defaults to lowercased <kind>
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Describes pod affinity scheduling rules (e.g. co-locate this pod in the same node, zone, etc. as some other pod(s)).
+=======
+
labelSelectorPath string
+
LabelSelectorPath defines the JSON path inside of a CustomResource that corresponds to Scale.Status.Selector. Only JSON paths without the array notation are allowed. Must be a JSON Path under .status. Must be set to work with HPA. If there is no value under the given path in the CustomResource, the status label selector value in the /scale subresource will default to the empty string.
+
+
+
specReplicasPath string
+
SpecReplicasPath defines the JSON path inside of a CustomResource that corresponds to Scale.Spec.Replicas. Only JSON paths without the array notation are allowed. Must be a JSON Path under .spec. If there is no value under the given path in the CustomResource, the /scale subresource will return an error on GET.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
Describes pod anti-affinity scheduling rules (e.g. avoid putting this pod in the same node, zone, etc. as some other pod(s)).
+=======
+
statusReplicasPath string
+
StatusReplicasPath defines the JSON path inside of a CustomResource that corresponds to Scale.Status.Replicas. Only JSON paths without the array notation are allowed. Must be a JSON Path under .status. If there is no value under the given path in the CustomResource, the status replica value in the /scale subresource will default to 0.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
AggregationRule describes how to locate ClusterRoles to aggregate into the ClusterRole
+
+
+=======
+
CustomResourceSubresourceStatus defines how to serve the status subresource for CustomResources. Status is represented by the .status JSON path inside of a CustomResource. When set, exposes a /status subresource for the custom resource PUT requests to the /status subresource take a custom resource object, and ignore changes to anything except the status stanza * PUT/POST/PATCH requests to the custom resource ignore changes to the status stanza
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
ClusterRoleSelectors holds a list of selectors which will be used to find ClusterRoles and create the rules. If any of the selectors match, then the ClusterRole's permissions will be added
+=======
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+||||||| merged common ancestors
+
extensions
+
v1beta1
+
AllowedHostPath
+=======
+
apiextensions
+
v1beta1
+
CustomResourceValidation
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
is the path prefix that the host volume must match. It does not support *. Trailing slashes are trimmed when validating the path prefix with a host path. Examples: /foo would allow /foo, /foo/ and /foo/bar/foo would not allow /food or /etc/foo
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
AzureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.
+
+
+
+
+=======
+
+
+
+
+
DaemonSetCondition describes the state of a DaemonSet at a certain point.
+
+
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
fsType string
+
Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified.
+=======
+
reason string
+
The reason for the condition's last transition.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
kind string
+
Expected values Shared: multiple blob disks per storage account Dedicated: single blob disk per storage account Managed: azure managed data disk (only in managed availability set). defaults to shared
+=======
+
status string
+
Status of the condition, one of True, False, Unknown.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
Must be fulfilled before a deletion is carried out. If not possible, a 409 Conflict status will be returned.
+
+
+
propagationPolicy string
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+||||||| merged common ancestors
+
readOnly boolean
+
Optional: The value to pass to ControllerPublishVolumeRequest. Defaults to false (read/write).
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+||||||| merged common ancestors
+
Core
+
v1
+
Capabilities
+=======
+
Core
+
v1
+
DownwardAPIProjection
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
Adds and removes POSIX capabilities from running containers.
+
+
+
+
+=======
+
+
+
Represents downward API info for projecting into a projected volume. Note that this is identical to a downwardAPI volume source without the default mode.
+
+
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
@@ -63685,10 +101999,27 @@ Appears In:
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -63757,16 +102120,48 @@ Appears In:
includeUninitialized
If true, partially initialized resources are included in the response.
Optional: mode bits to use on this file, must be a value between 0 and 0777. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
Required: Path is the relative path name of the file to be created. Must not be absolute or contain the '..' path. Must be utf-8 encoded. The first item of the relative path must not start with '..'
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, requests.cpu and requests.memory) are currently supported.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Optional: mode bits to use on created files by default. Must be a value between 0 and 0777. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+||||||| merged common ancestors
+
certificates
+
v1beta1
+
CertificateSigningRequestCondition
+=======
+
Core
+
v1
+
EmptyDirVolumeSource
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
+
+
+
+=======
+
+
+
Represents an empty directory for a pod. Empty directory volumes support ownership management and SELinux relabeling.
+
+
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
If true, partially initialized resources are included in the response.
@@ -63880,8 +102394,24 @@ Appears In:
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
Total amount of local storage required for this EmptyDir volume. The size limit is also applicable for memory medium. The maximum usage on memory medium EmptyDir would be the minimum value between the SizeLimit specified here and the sum of memory limits of all containers in a pod. The default is nil which means that the limit is undefined. More info: http://kubernetes.io/docs/user-guide/volumes#emptydir
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
GET /apis/rbac.authorization.k8s.io/v1/watch/namespaces/{namespace}/rolebindings
Path Parameters
+||||||| merged common ancestors
+
Represents a cinder volume resource in Openstack. A Cinder volume must exist before mounting to a container. The volume must also be in the same region as the kubelet. Cinder volumes support ownership management and SELinux relabeling.
+
+
+=======
+
EndpointAddress is a tuple that describes single IP address.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The IP of this endpoint. May not be loopback (127.0.0.0/8), link-local (169.254.0.0/16), or link-local multicast ((224.0.0.0/24). IPv6 is also accepted but not fully supported on all platforms. Also, certain kubernetes components, like kube-proxy, are not IPv6 ready.
+
+
+
nodeName string
+
Optional: Node hosting this endpoint. This can be used to determine endpoints local to a node.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+||||||| merged common ancestors
+
Core
+
v1
+
ClientIPConfig
+=======
+
Core
+
v1
+
EndpointPort
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
ClientIPConfig represents the configurations of Client IP based session affinity.
+
+
+
+
+
Field
+
Description
+
+
+
+=======
+
+
+
EndpointPort is a tuple that describes a single port.
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+||||||| merged common ancestors
+
timeoutSeconds integer
+
timeoutSeconds specifies the seconds of ClientIP type session sticky time. The value must be >0 && <=86400(for 1 day) if ServiceAffinity == "ClientIP". Default value is 10800(for 3 hours).
+=======
+
name string
+
The name of this port (corresponds to ServicePort.Name). Must be a DNS_LABEL. Optional only if one port is defined.
+
port integer
+
The port number of the endpoint.
+
+
+
protocol string
+
The IP protocol for this port. Must be UDP or TCP. Default is TCP.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
ComponentCondition v1 core
+
+
+=======
+
+
+
EndpointSubset v1 core
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
includeUninitialized
If true, partially initialized resources are included in the response.
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+||||||| merged common ancestors
+
Core
+
v1
+
ComponentCondition
+=======
+
Core
+
v1
+
EndpointSubset
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
Information about the condition of a component.
+
+
+
+
+=======
+
+
+
EndpointSubset is a group of addresses with a common set of ports. The expanded set of endpoints is the Cartesian product of Addresses x Ports. For example, given:
+ {
+ Addresses: [{"ip": "10.10.1.1"}, {"ip": "10.10.2.2"}],
+ Ports: [{"name": "a", "port": 8675}, {"name": "b", "port": 309}]
+ }
+The resulting set of endpoints can be viewed as:
+ a: [ 10.10.1.1:8675, 10.10.2.2:8675 ],
+ b: [ 10.10.1.1:309, 10.10.2.2:309 ]
+
+
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
error string
+
Condition error code for a component. For example, a health check error code.
+
message string
+
Message about the condition for a component. For example, information about a health check.
IP addresses which offer the related ports that are marked as ready. These endpoints should be considered safe for load balancers and clients to utilize.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
IP addresses which offer the related ports but are not currently marked as ready because they have not yet finished starting, have recently failed a readiness check, or have recently failed a liveness check.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
Specify whether the ConfigMap or it's key must be defined
+=======
+
name string
+
Name of the environment variable. Must be a C_IDENTIFIER.
+
+
+
value string
+
Variable references $(VAR_NAME) are expanded using the previous defined environment variables in the container and any service environment variables. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Defaults to "".
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
Adapts a ConfigMap into a projected volume.
+
The contents of the target ConfigMap's Data field will be presented in a projected volume as files using the keys in the Data field as the file names, unless the items element is populated with specific mappings of keys to paths. Note that this is identical to a configmap volume source without the default mode.
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
SelfSubjectAccessReview checks whether or the current user can perform an action. Not filling in a spec.namespace means "in all namespaces". Self is a special case, because users should always be able to check whether they can perform an action
If unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'.
Selects a field of the pod: supports metadata.name, metadata.namespace, metadata.labels, metadata.annotations, spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, limits.ephemeral-storage, requests.cpu, requests.memory and requests.ephemeral-storage) are currently supported.
The contents of the target ConfigMap's Data field will be presented in a volume as files using the keys in the Data field as the file names, unless the items element is populated with specific mappings of keys to paths. ConfigMap volumes support ownership management and SELinux relabeling.
+=======
+
+
+
EventSeries contain information on series of events, i.e. thing that was/is happening continuously for some time.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
NonResourceAttributes describes information for a non-resource access request
+||||||| merged common ancestors
+
defaultMode integer
+
Optional: mode bits to use on created files by default. Must be a value between 0 and 0777. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.
If unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'.
ContainerPort represents a network port in a single container.
+
+
+=======
+
Eviction evicts a pod from its node subject to certain policies and safety constraints. This is a subresource of Pod. A request to cause such an eviction is created by POSTing to .../pods/<pod name>/evictions.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Number of port to expose on the host. If specified, this must be a valid port number, 0 < x < 65536. If HostNetwork is specified, this must match ContainerPort. Most containers do not need this.
If specified, this must be an IANA_SVC_NAME and unique within the pod. Each named port in a pod must have a unique name. Name for the port that can be referred to by services.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
ContainerState holds a possible state of container. Only one of its members may be specified. If none of them is specified, the default one is ContainerStateWaiting.
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
SelfSubjectRulesReview enumerates the set of actions the current user can perform within a namespace. The returned list of actions may be incomplete depending on the server's authorization mode, and any errors experienced during the evaluation. SelfSubjectRulesReview should be used by UIs to show/hide actions, or to quickly let an end user reason about their permissions. It should NOT Be used by external systems to drive authorization decisions as this raises confused deputy, cache lifetime/revocation, and correctness concerns. SubjectAccessReview, and LocalAccessReview are the correct way to defer authorization decisions to the API server.
Command is the command line to execute inside the container, the working directory for the command is root ('/') in the container's filesystem. The command is simply exec'd, it is not run inside a shell, so traditional shell instructions ('
+
', etc) won't work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
ContainerStateRunning v1 core
+
+
+=======
+
+
+
ExternalDocumentation v1beta1 apiextensions
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
ContainerStateTerminated is a terminated state of a container.
+
+
+=======
+
ExternalMetricSource indicates how to scale on a metric not associated with any Kubernetes object (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster). Exactly one "target" type should be set.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
ServiceAccount binds together: a name, understood by users, and perhaps by peripheral systems, for an identity a principal that can be authenticated and authorized * a set of secrets
+||||||| merged common ancestors
+
ContainerStateWaiting is a waiting state of a container.
+=======
+
ExternalMetricStatus indicates the current value of a global metric not associated with any Kubernetes object.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
AutomountServiceAccountToken indicates whether pods running as this service account should have an API token automatically mounted. Can be overridden at the pod level.
ImagePullSecrets is a list of references to secrets in the same namespace to use for pulling any images in pods that reference this ServiceAccount. ImagePullSecrets are distinct from Secrets because Secrets can be mounted in the pod, but ImagePullSecrets are only accessed by the kubelet. More info: https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod
CrossVersionObjectReference contains enough information to let you identify the referred resource.
+
+
+=======
+
Represents a Fibre Channel volume. Fibre Channel volumes can only be mounted as read/write once. Fibre Channel volumes support ownership management and SELinux relabeling.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Kind is the serialized kind of the resource. It is normally CamelCase and singular.
+
listKind string
+
ListKind is the serialized kind of the list for this resource. Defaults to <kind>List.
+
+
+
plural string
+
Plural is the plural name of the resource to serve. It must match the name of the CustomResourceDefinition-registration too: plural.group and it must be all lowercase.
+=======
+
driver string
+
Driver is the name of the driver to use for this volume.
+
+
+
fsType string
+
Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". The default filesystem depends on FlexVolume script.
+
+
+
options object
+
Optional: Extra command options if any.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
Optional: SecretRef is reference to the secret object containing sensitive information to pass to the plugin scripts. This may be empty if no secret object is specified. If the secret object contains more than one secret, all secrets are passed to the plugin scripts.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
OpenAPIV3Schema is the OpenAPI v3 schema to be validated against.
+=======
+
driver string
+
Driver is the name of the driver to use for this volume.
+
+
+
fsType string
+
Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". The default filesystem depends on FlexVolume script.
+
+
+
options object
+
Optional: Extra command options if any.
+
+
+
readOnly boolean
+
Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.
Optional: SecretRef is reference to the secret object containing sensitive information to pass to the plugin scripts. This may be empty if no secret object is specified. If the secret object contains more than one secret, all secrets are passed to the plugin scripts.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
DaemonEndpoint contains information about a single Daemon endpoint.
+
+
+=======
+
Represents a Flocker volume mounted by the Flocker agent. One and only one of datasetName and datasetUUID should be set. Flocker volumes do not support ownership management or SELinux relabeling.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
DaemonSetCondition describes the state of a DaemonSet at a certain point.
+
+
+=======
+
Represents a Persistent Disk resource in Google Compute Engine.
+
A GCE PD must exist before mounting to a container. The disk must also be in the same GCE project and zone as the kubelet. A GCE PD can only be mounted as read/write once or read-only many times. GCE PDs support ownership management and SELinux relabeling.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Last time the condition transitioned from one status to another.
+
+
+
message string
+
A human readable message indicating details about the transition.
+
+
+
reason string
+
The reason for the condition's last transition.
+
+
+
status string
+
Status of the condition, one of True, False, Unknown.
+
+
+
type string
+
Type of DaemonSet condition.
+=======
+
fsType string
+
Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk
+
+
+
partition integer
+
The partition in the volume that you want to mount. If omitted, the default is to mount by volume name. Examples: For volume /dev/sda1, you specify the partition as "1". Similarly, the volume partition for /dev/sda is "0" (or you can leave the property empty). More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk
DaemonSetUpdateStrategy is a struct used to control the update strategy for a DaemonSet.
+
+
+=======
+
Represents a volume that is populated with the contents of a git repository. Git repo volumes do not support ownership management. Git repo volumes support SELinux relabeling.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Rolling update config params. Present only if type = "RollingUpdate".
+=======
+
directory string
+
Target directory name. Must not contain or start with '..'. If '.' is supplied, the volume directory will be the git repository. Otherwise, if specified, the volume will contain the git repository in the subdirectory with the given name.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+||||||| merged common ancestors
+
propagationPolicy string
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
Represents downward API info for projecting into a projected volume. Note that this is identical to a downwardAPI volume source without the default mode.
+
+
+=======
+
HTTPGetAction describes an action based on HTTP Get requests.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Custom headers to set in the request. HTTP allows repeated headers.
+
+
+
path string
+
Path to access on the HTTP server.
+
+
+
port
+
Name or number of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.
+
+
+
scheme string
+
Scheme to use for connecting to the host. Defaults to HTTP.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
DownwardAPIVolumeFile v1 core
+
+
+=======
+
+
+
HTTPHeader v1 core
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
A selector to restrict the list of returned objects by their labels. Defaults to everything.
@@ -65089,18 +105204,47 @@ Appears In:
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Required: Selects a field of the pod: only annotations, labels, name and namespace are supported.
+
mode integer
+
Optional: mode bits to use on this file, must be a value between 0 and 0777. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.
+
+
+
path string
+
Required: Path is the relative path name of the file to be created. Must not be absolute or contain the '..' path. Must be utf-8 encoded. The first item of the relative path must not start with '..'
+=======
+
name string
+
The header field name
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, requests.cpu and requests.memory) are currently supported.
+=======
+
value string
+
The header field value
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Optional: mode bits to use on created files by default. Must be a value between 0 and 0777. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.
Path is an extended POSIX regex as defined by IEEE Std 1003.1, (i.e this follows the egrep/unix syntax, not the perl syntax) matched against the path of an incoming request. Currently it can contain characters disallowed from the conventional "path" part of a URL as defined by RFC 3986. Paths must begin with a '/'. If unspecified, the path defaults to a catch all sending traffic to the backend.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Represents an empty directory for a pod. Empty directory volumes support ownership management and SELinux relabeling.
+
+
+=======
+
HTTPIngressRuleValue is a list of http selectors pointing to backends. In the example: http://<host>/<path>?<searchpart> -> backend where where parts of the url correspond to RFC 3986, this resource will be used to match against everything after the last '/' and before the first '?' or '#'.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Total amount of local storage required for this EmptyDir volume. The size limit is also applicable for memory medium. The maximum usage on memory medium EmptyDir would be the minimum value between the SizeLimit specified here and the sum of memory limits of all containers in a pod. The default is nil which means that the limit is undefined. More info: http://kubernetes.io/docs/user-guide/volumes#emptydir
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+||||||| merged common ancestors
+
hostname string
+
The Hostname of this endpoint
+
ip string
+
The IP of this endpoint. May not be loopback (127.0.0.0/8), link-local (169.254.0.0/16), or link-local multicast ((224.0.0.0/24). IPv6 is also accepted but not fully supported on all platforms. Also, certain kubernetes components, like kube-proxy, are not IPv6 ready.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+||||||| merged common ancestors
+
name string
+
The name of this port (corresponds to ServicePort.Name). Must be a DNS_LABEL. Optional only if one port is defined.
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
Core
+
v1
+
EndpointSubset
+=======
+
Core
+
v1
+
HostAlias
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
EndpointSubset is a group of addresses with a common set of ports. The expanded set of endpoints is the Cartesian product of Addresses x Ports. For example, given:
+ {
+ Addresses: [{"ip": "10.10.1.1"}, {"ip": "10.10.2.2"}],
+ Ports: [{"name": "a", "port": 8675}, {"name": "b", "port": 309}]
+ }
+The resulting set of endpoints can be viewed as:
+ a: [ 10.10.1.1:8675, 10.10.2.2:8675 ],
+ b: [ 10.10.1.1:309, 10.10.2.2:309 ]
+
+
+
+
+=======
+
+
+
HostAlias holds the mapping between IP and hostnames that will be injected as an entry in the pod's hosts file.
+
+
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
IP addresses which offer the related ports that are marked as ready. These endpoints should be considered safe for load balancers and clients to utilize.
IP addresses which offer the related ports but are not currently marked as ready because they have not yet finished starting, have recently failed a readiness check, or have recently failed a liveness check.
+=======
+
hostnames string array
+
Hostnames for the above IP address.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -65518,10 +106032,40 @@ Appears In:
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+||||||| merged common ancestors
+
Core
+
v1
+
EnvVar
+=======
+
extensions
+
v1beta1
+
HostPortRange
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Name of the environment variable. Must be a C_IDENTIFIER.
+
+
+
value string
+
Variable references $(VAR_NAME) are expanded using the previous defined environment variables in the container and any service environment variables. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Defaults to "".
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -65605,8 +106208,24 @@ Appears In:
includeUninitialized
If true, partially initialized resources are included in the response.
Selects a field of the pod: supports metadata.name, metadata.namespace, metadata.labels, metadata.annotations, spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP.
Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, limits.ephemeral-storage, requests.cpu, requests.memory and requests.ephemeral-storage) are currently supported.
+=======
+
max integer
+
Max is the end of the range, inclusive.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
EventSeries contain information on series of events, i.e. thing that was/is happening continuously for some time.
+
+
+=======
+
+
+
IPBlock describes a particular CIDR (Ex. "192.168.1.1/24") that is allowed to the pods matched by a NetworkPolicySpec's podSelector. The except entry describes CIDRs that should not be included within this rule.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+||||||| merged common ancestors
+
count integer
+
Number of occurrences in this series up to the last heartbeat time
If true, partially initialized resources are included in the response.
+||||||| merged common ancestors
+
state string
+
State of this Series: Ongoing or Finished
+=======
+
except string array
+
Except is a slice of CIDRs that should not be included within an IP Block Valid examples are "192.168.1.1/24" Except values will be rejected if they are outside the CIDR range
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
EventSource v1 core
+
+
+=======
+
+
+
ISCSIPersistentVolumeSource v1 core
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
@@ -65725,10 +106426,40 @@ Appears In:
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+||||||| merged common ancestors
+
Core
+
v1
+
EventSource
+=======
+
Core
+
v1
+
ISCSIPersistentVolumeSource
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
ISCSIPersistentVolumeSource represents an ISCSI disk. ISCSI volumes can only be mounted as read/write once. ISCSI volumes support ownership management and SELinux relabeling.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+=======
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
-
Group
-
Version
-
Kind
+
fsType string
+
Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#iscsi
Custom iSCSI Initiator Name. If initiatorName is specified with iscsiInterface simultaneously, new iSCSI interface <target portal>:<volume name> will be created for the connection.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
SubjectAccessReview checks whether or not a user or group can perform an action.
+||||||| merged common ancestors
+
+
+
Eviction evicts a pod from its node subject to certain policies and safety constraints. This is a subresource of Pod. A request to cause such an eviction is created by POSTing to .../pods/<pod name>/evictions.
+
+
+=======
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Extra corresponds to the user.Info.GetExtra() method from the authenticator. Since that is input to the authorizer it needs a reflection here.
+||||||| merged common ancestors
+
command string array
+
Command is the command line to execute inside the container, the working directory for the command is root ('/') in the container's filesystem. The command is simply exec'd, it is not run inside a shell, so traditional shell instructions ('
+
', etc) won't work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy.
+=======
+
chapAuthDiscovery boolean
+
whether support iSCSI Discovery CHAP authentication
+
chapAuthSession boolean
+
whether support iSCSI Session CHAP authentication
+
+
+
fsType string
+
Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#iscsi
+
+
+
initiatorName string
+
Custom iSCSI Initiator Name. If initiatorName is specified with iscsiInterface simultaneously, new iSCSI interface <target portal>:<volume name> will be created for the connection.
+
+
+
iqn string
+
Target iSCSI Qualified Name.
+
+
+
iscsiInterface string
+
iSCSI Interface Name that uses an iSCSI transport. Defaults to 'default' (tcp).
+
+
+
lun integer
+
iSCSI Target Lun number.
+
+
+
portals string array
+
iSCSI Target Portal List. The portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260).
+
+
+
readOnly boolean
+
ReadOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false.
Denied is optional. True if the action would be denied, otherwise false. If both allowed is false and denied is false, then the authorizer has no opinion on whether to authorize the action. Denied may not be true if Allowed is true.
+||||||| merged common ancestors
+
url string
+
+=======
+
servicePort
+
Specifies the port of the referenced service.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
FCVolumeSource v1 core
+
+
+=======
+
+
+
IngressRule v1beta1 extensions
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
evaluationError string
EvaluationError is an indication that some error occurred during the authorization check. It is entirely possible to get an error and be able to continue determine authorization status in spite of it. For instance, RBAC can be missing a role, but enough roles are still present and bound to reason about the request.
POST /apis/authorization.k8s.io/v1/subjectaccessreviews
Query Parameters
+||||||| merged common ancestors
+
Represents a Fibre Channel volume. Fibre Channel volumes can only be mounted as read/write once. Fibre Channel volumes support ownership management and SELinux relabeling.
+
+
+=======
+
IngressRule represents the rules mapping the paths under a specified host to the related backend services. Incoming requests are first evaluated for a host match, then routed to the backend associated with the matching IngressRuleValue.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified.
+
+
+
lun integer
+
Optional: FC target lun number
+
+
+
readOnly boolean
+
Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.
+
+
+
targetWWNs string array
+
Optional: FC target worldwide names (WWNs)
+
+
+
wwids string array
+
Optional: FC volume world wide identifiers (wwids) Either wwids or combination of targetWWNs and lun must be set, but not both simultaneously.
+=======
+
host string
+
Host is the fully qualified domain name of a network host, as defined by RFC 3986. Note the following deviations from the "host" part of the URI as defined in the RFC: 1. IPs are not allowed. Currently an IngressRuleValue can only apply to the IP in the Spec of the parent Ingress. 2. The : delimiter is not respected because ports are not allowed. Currently the port of an Ingress is implicitly :80 for http and :443 for https. Both these may change in the future. Incoming requests are matched against the host before the IngressRuleValue. If the host is unspecified, the Ingress routes all traffic based on the specified IngressRuleValue.
Ranges are the allowed ranges of fs groups. If you would like to force a single fs group then supply a single range with the same start and end.
+=======
+
hosts string array
+
Hosts are a list of hosts included in the TLS certificate. The values in this list must match the name/s used in the tlsSecret. Defaults to the wildcard host setting for the loadbalancer controller fulfilling this Ingress, if left unspecified.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Rule is the strategy that will dictate what FSGroup is used in the SecurityContext.
+=======
+
secretName string
+
SecretName is the name of the secret used to terminate SSL traffic on 443. Field is left optional to allow SSL routing based on SNI hostname alone. If the SNI host in a listener conflicts with the "Host" header field used by an IngressRule, the SNI host is used for termination and value of the Host header is used for routing.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
TokenReview attempts to authenticate a token to a known user. Note: TokenReview requests may be cached by the webhook token authenticator plugin in the kube-apiserver.
Status is filled in by the server and indicates whether the request can be authenticated.
+||||||| merged common ancestors
+
driver string
+
Driver is the name of the driver to use for this volume.
+
+
+
fsType string
+
Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". The default filesystem depends on FlexVolume script.
+
+
+
options object
+
Optional: Extra command options if any.
+
+
+
readOnly boolean
+
Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.
Optional: SecretRef is reference to the secret object containing sensitive information to pass to the plugin scripts. This may be empty if no secret object is specified. If the secret object contains more than one secret, all secrets are passed to the plugin scripts.
+=======
+
name string
+
name of the process that is responsible for initializing this object.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Represents a Flocker volume mounted by the Flocker agent. One and only one of datasetName and datasetUUID should be set. Flocker volumes do not support ownership management or SELinux relabeling.
+=======
+
Initializers tracks the progress of initialization.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Authenticated indicates that the token was associated with a known user.
+||||||| merged common ancestors
+
datasetName string
+
Name of the dataset stored as metadata -> name on the dataset for Flocker should be considered as deprecated
+=======
+
pending Initializer array patch type: merge patch merge key: name
+
Pending is a list of initializers that must execute in order before this object is visible. When the last pending initializer is removed, and no failing result is set, the initializers struct will be set to nil and the object is considered as initialized and visible to all clients.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
If result is set with the Failure field, the object will be persisted to storage and then deleted, ensuring that other clients can observe the deletion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Represents a Persistent Disk resource in Google Compute Engine.
+
A GCE PD must exist before mounting to a container. The disk must also be in the same GCE project and zone as the kubelet. A GCE PD can only be mounted as read/write once or read-only many times. GCE PDs support ownership management and SELinux relabeling.
+
+
+=======
+
JSON represents any valid JSON value. These types are supported: bool, int64, float64, string, []interface{}, map[string]interface{} and nil.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk
+
+
+
partition integer
+
The partition in the volume that you want to mount. If omitted, the default is to mount by volume name. Examples: For volume /dev/sda1, you specify the partition as "1". Similarly, the volume partition for /dev/sda is "0" (or you can leave the property empty). More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
Represents a volume that is populated with the contents of a git repository. Git repo volumes do not support ownership management. Git repo volumes support SELinux relabeling.
Target directory name. Must not contain or start with '..'. If '.' is supplied, the volume directory will be the git repository. Otherwise, if specified, the volume will contain the git repository in the subdirectory with the given name.
+=======
+
$ref string
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
List of egress rules to be applied to the selected pods. Outgoing traffic is allowed if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic matches at least one egress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy limits all outgoing traffic (and serves solely to ensure that the pods it selects are isolated by default). This field is beta-level in 1.8
+||||||| merged common ancestors
+
groupVersion string
+
groupVersion specifies the API group and version in the form "group/version"
+=======
+
Allows boolean
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
List of ingress rules to be applied to the selected pods. Traffic is allowed to a pod if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic source is the pod's local node, OR if the traffic matches at least one ingress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy does not allow any traffic (and serves solely to ensure that the pods it selects are isolated by default)
+||||||| merged common ancestors
+
version string
+
version specifies the version in the form of "version". This is to save the clients the trouble of splitting the GroupVersion.
Selects the pods to which this NetworkPolicy object applies. The array of ingress rules is applied to any pods selected by this field. Multiple network policies can select the same set of pods. In this case, the ingress rules for each are combined additively. This field is NOT optional and follows standard label selector semantics. An empty podSelector matches all pods in this namespace.
List of rule types that the NetworkPolicy relates to. Valid options are Ingress, Egress, or Ingress,Egress. If this field is not specified, it will default based on the existence of Ingress or Egress rules; policies that contain an Egress section are assumed to affect Egress, and all policies (whether or not they contain an Ingress section) are assumed to affect Ingress. If you want to write an egress-only policy, you must explicitly specify policyTypes [ "Egress" ]. Likewise, if you want to write a policy that specifies that no egress is allowed, you must specify a policyTypes value that include "Egress" (since such a policy would not include an Egress section and would otherwise default to just [ "Ingress" ]). This field is beta-level in 1.8
+||||||| merged common ancestors
+
Core
+
v1
+
HTTPGetAction
+=======
+
batch
+
v1
+
JobCondition
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Backend defines the referenced service endpoint to which the traffic will be forwarded to.
+=======
+
key string
+
The key to project.
+
mode integer
+
Optional: mode bits to use on this file, must be a value between 0 and 0777. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
Created
+||||||| merged common ancestors
+
path string
+
Path is an extended POSIX regex as defined by IEEE Std 1003.1, (i.e this follows the egrep/unix syntax, not the perl syntax) matched against the path of an incoming request. Currently it can contain characters disallowed from the conventional "path" part of a URL as defined by RFC 3986. Paths must begin with a '/'. If unspecified, the path defaults to a catch all sending traffic to the backend.
+=======
+
path string
+
The relative path of the file to map the key to. May not be an absolute path. May not contain the path element '..'. May not start with the string '..'.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
HTTPIngressRuleValue v1beta1 extensions
+
+
+=======
+
+
+
LabelSelector v1 meta
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
HTTPIngressRuleValue is a list of http selectors pointing to backends. In the example: http://<host>/<path>?<searchpart> -> backend where where parts of the url correspond to RFC 3986, this resource will be used to match against everything after the last '/' and before the first '?' or '#'.
+
+
+=======
+
A label selector is a label query over a set of resources. The result of matchLabels and matchExpressions are ANDed. An empty label selector matches all objects. A null label selector matches no objects.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
matchExpressions is a list of label selector requirements. The requirements are ANDed.
+
+
+
matchLabels object
+
matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is "key", the operator is "In", and the values array contains only "value". The requirements are ANDed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
TCPSocket specifies an action involving a TCP port. TCP hooks not yet supported
+=======
+
key string patch type: merge patch merge key: key
+
key is the label key that the selector applies to.
+
+
+
operator string
+
operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.
+
+
+
values string array
+
values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
PUT /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}
Path Parameters
+||||||| merged common ancestors
+
HorizontalPodAutoscalerCondition describes the state of a HorizontalPodAutoscaler at a certain point.
+
+
+=======
+
Lifecycle describes actions that the management system should take in response to container lifecycle events. For the PostStart and PreStop lifecycle handlers, management of the container blocks until the action is complete, unless the container process fails, in which case the handler is aborted.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
PreStop is called immediately before a container is terminated. The container is terminated after the handler completes. The reason for termination is passed to the handler. Regardless of the outcome of the handler, the container is eventually terminated. Other management of the container blocks until the hook completes. More info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks
+
+
+
+
LimitRangeItem v1 core
+
+
+
+
Group
+
Version
+
Kind
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
Default resource requirement limit value by resource name if resource limit is omitted.
+
+
+
defaultRequest object
+
DefaultRequest is the default resource requirement request value by resource name if resource request is omitted.
+
+
+
max object
+
Max usage constraints on this kind by resource name.
+
+
+
maxLimitRequestRatio object
+
MaxLimitRequestRatio if specified, the named resource must have a request and limit that are both non-zero where limit divided by request is less than or equal to the enumerated value; this represents the max burst for the named resource.
+
+
+
min object
+
Min usage constraints on this kind by resource name.
+
+
+
type string
+
Type of resource that this limit applies to.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Represents a host path mapped into a pod. Host path volumes do not support ownership management or SELinux relabeling.
+
+
+=======
+
ListMeta describes metadata that synthetic resources must have, including lists and various status objects. A resource may have only one of {ObjectMeta, ListMeta}.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
continue may be set if the user set a limit on the number of items returned, and indicates that the server has more data available. The value is opaque and may be used to issue another request to the endpoint that served this list to retrieve the next set of available objects. Continuing a list may not be possible if the server configuration has changed or more than a few minutes have passed. The resourceVersion field returned when using this continue value will be identical to the value in the first response.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
ID Range provides a min/max of an allowed range of IDs.
+
+
+
+
+=======
+
+
+
LoadBalancerStatus represents the status of a load-balancer.
+
+
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
IPBlock describes a particular CIDR (Ex. "192.168.1.1/24") that is allowed to the pods matched by a NetworkPolicySpec's podSelector. The except entry describes CIDRs that should not be included within this rule.
+
+
+=======
+
LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
CIDR is a string representing the IP Block Valid examples are "192.168.1.1/24"
+
+
+
except string array
+
Except is a slice of CIDRs that should not be included within an IP Block Valid examples are "192.168.1.1/24" Except values will be rejected if they are outside the CIDR range
ISCSIPersistentVolumeSource represents an ISCSI disk. ISCSI volumes can only be mounted as read/write once. ISCSI volumes support ownership management and SELinux relabeling.
+
+
+=======
+
Local represents directly-attached storage with node affinity
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+||||||| merged common ancestors
+
chapAuthDiscovery boolean
+
whether support iSCSI Discovery CHAP authentication
+
+
+
chapAuthSession boolean
+
whether support iSCSI Session CHAP authentication
+
+
+
fsType string
+
Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#iscsi
+
+
+
initiatorName string
+
Custom iSCSI Initiator Name. If initiatorName is specified with iscsiInterface simultaneously, new iSCSI interface <target portal>:<volume name> will be created for the connection.
+
+
+
iqn string
+
Target iSCSI Qualified Name.
+
+
+
iscsiInterface string
+
iSCSI Interface Name that uses an iSCSI transport. Defaults to 'default' (tcp).
+
+
+
lun integer
+
iSCSI Target Lun number.
+
+
+
portals string array
+
iSCSI Target Portal List. The Portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260).
+
+
+
readOnly boolean
+
ReadOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false.
CHAP Secret for iSCSI target and initiator authentication
+
+
+
targetPortal string
+
iSCSI Target Portal. The Portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260).
+=======
+
path string
+
The full path to the volume on the node For alpha, this path must be a directory Once block as a source is supported, then this path can point to a block device
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
object name and auth scope, such as for teams and projects
+||||||| merged common ancestors
+
chapAuthDiscovery boolean
+
whether support iSCSI Discovery CHAP authentication
+
+
+
chapAuthSession boolean
+
whether support iSCSI Session CHAP authentication
+
+
+
fsType string
+
Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#iscsi
+
+
+
initiatorName string
+
Custom iSCSI Initiator Name. If initiatorName is specified with iscsiInterface simultaneously, new iSCSI interface <target portal>:<volume name> will be created for the connection.
+
+
+
iqn string
+
Target iSCSI Qualified Name.
+
+
+
iscsiInterface string
+
iSCSI Interface Name that uses an iSCSI transport. Defaults to 'default' (tcp).
external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second). The values will be averaged together before being compared to the target value.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the "pods" source.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).
pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second). The values will be averaged together before being compared to the target value.
resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the "pods" source.
+
+
+
type string
+
type is the type of metric source. It will be one of "Object", "Pods" or "Resource", each corresponds to a matching field in the object.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
IngressRule represents the rules mapping the paths under a specified host to the related backend services. Incoming requests are first evaluated for a host match, then routed to the backend associated with the matching IngressRuleValue.
+
+
+
+
+=======
+
+
+
+
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
A selector to restrict the list of returned objects by their fields. Defaults to everything.
includeUninitialized
If true, partially initialized resources are included in the response.
+||||||| merged common ancestors
+
host string
+
Host is the fully qualified domain name of a network host, as defined by RFC 3986. Note the following deviations from the "host" part of the URI as defined in the RFC: 1. IPs are not allowed. Currently an IngressRuleValue can only apply to the IP in the Spec of the parent Ingress. 2. The : delimiter is not respected because ports are not allowed. Currently the port of an Ingress is implicitly :80 for http and :443 for https. Both these may change in the future. Incoming requests are matched against the host before the IngressRuleValue. If the host is unspecified, the Ingress routes all traffic based on the specified IngressRuleValue.
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
extensions
+
v1beta1
+
IngressTLS
+=======
+
Core
+
v1
+
NFSVolumeSource
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
IngressTLS describes the transport layer security associated with an Ingress.
+
+
+
+
+=======
+
+
+
Represents an NFS mount that lasts the lifetime of a pod. NFS volumes do not support ownership management or SELinux relabeling.
+
+
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
hosts string array
+
Hosts are a list of hosts included in the TLS certificate. The values in this list must match the name/s used in the tlsSecret. Defaults to the wildcard host setting for the loadbalancer controller fulfilling this Ingress, if left unspecified.
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+||||||| merged common ancestors
+
secretName string
+
SecretName is the name of the secret used to terminate SSL traffic on 443. Field is left optional to allow SSL routing based on SNI hostname alone. If the SNI host in a listener conflicts with the "Host" header field used by an IngressRule, the SNI host is used for termination and value of the Host header is used for routing.
Initializer is information about an initializer that has not yet completed.
+
+
+=======
+
+
+
NetworkPolicyEgressRule describes a particular set of traffic that is allowed out of pods matched by a NetworkPolicySpec's podSelector. The traffic must match both ports and to. This type is beta-level in 1.8
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+||||||| merged common ancestors
+
name string
+
name of the process that is responsible for initializing this object.
List of destination ports for outgoing traffic. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.
List of destinations for outgoing traffic of pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all destinations (traffic not restricted by destination). If this field is present and contains at least one item, this rule allows traffic only if the traffic matches at least one item in the to list.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
Initializers v1 meta
+
+
+=======
+
+
+
NetworkPolicyIngressRule v1 networking
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
If true, partially initialized resources are included in the response.
+||||||| merged common ancestors
+
meta
+
v1
+
Initializers
+=======
+
networking
+
v1
+
NetworkPolicyIngressRule
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
Initializers tracks the progress of initialization.
+
+
+
+
+=======
+
+
+
+
+
NetworkPolicyIngressRule describes a particular set of traffic that is allowed to the pods matched by a NetworkPolicySpec's podSelector. The traffic must match both ports and from.
+
+
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
pending Initializer array patch type: merge patch merge key: name
+
Pending is a list of initializers that must execute in order before this object is visible. When the last pending initializer is removed, and no failing result is set, the initializers struct will be set to nil and the object is considered as initialized and visible to all clients.
List of sources which should be able to access the pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all sources (traffic not restricted by source). If this field is present and contains at least on item, this rule allows traffic only if the traffic matches at least one item in the from list.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
If result is set with the Failure field, the object will be persisted to storage and then deleted, ensuring that other clients can observe the deletion.
List of ports which should be made accessible on the pods selected for this rule. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
JSON v1beta1 apiextensions
+
+
+=======
+
+
+
NetworkPolicyPeer v1 networking
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Selects Namespaces using cluster scoped-labels. This matches all pods in all namespaces selected by this label selector. This field follows standard label selector semantics. If present but empty, this selector selects all namespaces.
This is a label selector which selects Pods in this namespace. This field follows standard label selector semantics. If present but empty, this selector selects all pods in this namespace.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
The port on the given protocol. This can either be a numerical or named port on a pod. If this field is not provided, this matches all port names and numbers.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The scheduler will prefer to schedule pods to nodes that satisfy the affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding "weight" to the sum if the node matches the corresponding matchExpressions; the node(s) with the highest sum are the most preferred.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
group is the preferred group of the resource. Empty implies the group of the containing resource list. For subresources, this may have a different value, for example: Scale".
@@ -67624,10 +110809,23 @@ Appears In:
version string
version is the preferred version of the resource. Empty implies the version of the containing resource list For subresources, this may have a different value, for example: v1 (while inside a v1beta1 version of the core resource's group)".
If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to an update), the system may or may not try to eventually evict the pod from its node.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
An AWS EBS disk must exist before mounting to a container. The disk must also be in the same AWS zone as the kubelet. An AWS EBS disk can only be mounted as read/write once. AWS EBS volumes support ownership management and SELinux relabeling.
+||||||| merged common ancestors
+
Maps a string key to a path within a volume.
+=======
+
NodeDaemonEndpoints lists ports opened by daemons running on the Node.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore
Optional: mode bits to use on this file, must be a value between 0 and 0777. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.
+
+
+
path string
+
The relative path of the file to map the key to. May not be an absolute path. May not contain the path element '..'. May not start with the string '..'.
A label selector is a label query over a set of resources. The result of matchLabels and matchExpressions are ANDed. An empty label selector matches all objects. A null label selector matches no objects.
+=======
+
A node selector represents the union of the results of one or more label queries over a set of nodes; that is, it represents the OR of the selectors represented by the node selector terms.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
matchExpressions is a list of label selector requirements. The requirements are ANDed.
+
+
+
matchLabels object
+
matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is "key", the operator is "In", and the values array contains only "value". The requirements are ANDed.
ClusterRoleSelectors holds a list of selectors which will be used to find ClusterRoles and create the rules. If any of the selectors match, then the ClusterRole's permissions will be added
+||||||| merged common ancestors
+
key string patch type: merge patch merge key: key
+
key is the label key that the selector applies to.
+
+
+
operator string
+
operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.
+
+
+
values string array
+
values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.
+=======
+
key string
+
The label key that the selector applies to.
+
+
+
operator string
+
Represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist. Gt, and Lt.
+
+
+
values string array
+
An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. If the operator is Gt or Lt, the values array must have a single element, which will be interpreted as an integer. This array is replaced during a strategic merge patch.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
AllowedFlexVolume represents a single Flexvolume that is allowed to be used.
+||||||| merged common ancestors
+
Lifecycle describes actions that the management system should take in response to container lifecycle events. For the PostStart and PreStop lifecycle handlers, management of the container blocks until the action is complete, unless the container process fails, in which case the handler is aborted.
+=======
+
A null or empty node selector term matches no objects.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
PreStop is called immediately before a container is terminated. The container is terminated after the handler completes. The reason for termination is passed to the handler. Regardless of the outcome of the handler, the container is eventually terminated. Other management of the container blocks until the hook completes. More info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks
is the path prefix that the host volume must match. It does not support *. Trailing slashes are trimmed when validating the path prefix with a host path. Examples: /foo would allow /foo, /foo/ and /foo/bar/foo would not allow /food or /etc/foo
+||||||| merged common ancestors
+
default object
+
Default resource requirement limit value by resource name if resource limit is omitted.
+
+
+
defaultRequest object
+
DefaultRequest is the default resource requirement request value by resource name if resource request is omitted.
+
+
+
max object
+
Max usage constraints on this kind by resource name.
+
+
+
maxLimitRequestRatio object
+
MaxLimitRequestRatio if specified, the named resource must have a request and limit that are both non-zero where limit divided by request is less than or equal to the enumerated value; this represents the max burst for the named resource.
+
+
+
min object
+
Min usage constraints on this kind by resource name.
+
+
+
type string
+
Type of resource that this limit applies to.
+=======
+
architecture string
+
The Architecture reported by the node
+
+
+
bootID string
+
Boot ID reported by the node.
+
+
+
containerRuntimeVersion string
+
ContainerRuntime Version reported by the node through runtime remote API (e.g. docker://1.5.0).
+
+
+
kernelVersion string
+
Kernel Version reported by the node from 'uname -r' (e.g. 3.16.0-0.bpo.4-amd64).
AttachedVolume describes a volume attached to a node
+||||||| merged common ancestors
+
ListMeta describes metadata that synthetic resources must have, including lists and various status objects. A resource may have only one of {ObjectMeta, ListMeta}.
+=======
+
+
+
NonResourceAttributes includes the authorization attributes available for non-resource requests to the Authorizer interface
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
DevicePath represents the device path where the volume should be available
name string
Name of the attached volume
+||||||| merged common ancestors
+
continue string
+
continue may be set if the user set a limit on the number of items returned, and indicates that the server has more data available. The value is opaque and may be used to issue another request to the endpoint that served this list to retrieve the next set of available objects. Continuing a list may not be possible if the server configuration has changed or more than a few minutes have passed. The resourceVersion field returned when using this continue value will be identical to the value in the first response.
Annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects. More info: http://kubernetes.io/docs/user-guide/annotations
+
+
+
clusterName string
+
The name of the cluster which the object belongs to. This is used to distinguish resources with same name and namespace in different clusters. This field is not set anywhere right now and apiserver is going to ignore it if set in create or update request.
CreationTimestamp is a timestamp representing the server time when this object was created. It is not guaranteed to be set in happens-before order across separate operations. Clients may not set this value. It is represented in RFC3339 form and is in UTC. Populated by the system. Read-only. Null for lists. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata
+
+
+
deletionGracePeriodSeconds integer
+
Number of seconds allowed for this object to gracefully terminate before it will be removed from the system. Only set when deletionTimestamp is also set. May only be shortened. Read-only.
DeletionTimestamp is RFC 3339 date and time at which this resource will be deleted. This field is set by the server when a graceful deletion is requested by the user, and is not directly settable by a client. The resource is expected to be deleted (no longer visible from resource lists, and not reachable by name) after the time in this field, once the finalizers list is empty. As long as the finalizers list contains items, deletion is blocked. Once the deletionTimestamp is set, this value may not be unset or be set further into the future, although it may be shortened or the resource may be deleted prior to this time. For example, a user may request that a pod is deleted in 30 seconds. The Kubelet will react by sending a graceful termination signal to the containers in the pod. After that 30 seconds, the Kubelet will send a hard termination signal (SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after this timestamp, until an administrator or automated process can determine the resource is fully terminated. If not set, graceful deletion of the object has not been requested. Populated by the system when a graceful deletion is requested. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata
+
+
+
finalizers string array patch type: merge
+
Must be empty before the object is deleted from the registry. Each entry is an identifier for the responsible component that will remove the entry from the list. If the deletionTimestamp of the object is non-nil, entries in this list can only be removed.
+
+
+
generateName string
+
GenerateName is an optional prefix, used by the server, to generate a unique name ONLY IF the Name field has not been provided. If this field is used, the name returned to the client will be different than the name passed. This value will also be combined with a unique suffix. The provided value has the same validation rules as the Name field, and may be truncated by the length of the suffix required to make the value unique on the server. If this field is specified and the generated name exists, the server will NOT return a 409 - instead, it will either return 201 Created or 500 with Reason ServerTimeout indicating a unique name could not be found in the time allotted, and the client should retry (optionally after the time indicated in the Retry-After header). Applied only if Name is not specified. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#idempotency
+
+
+
generation integer
+
A sequence number representing a specific generation of the desired state. Populated by the system. Read-only.
An initializer is a controller which enforces some system invariant at object creation time. This field is a list of initializers that have not yet acted on this object. If nil or empty, this object has been completely initialized. Otherwise, the object is considered uninitialized and is hidden (in list/watch and get calls) from clients that haven't explicitly asked to observe uninitialized objects. When an object is created, the system will populate this list with the current set of initializers. Only privileged users may set or modify this list. Once it is empty, it may not be modified further by any user.
+
+
+
labels object
+
Map of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services. More info: http://kubernetes.io/docs/user-guide/labels
+
+
+
name string
+
Name must be unique within a namespace. Is required when creating resources, although some resources may allow a client to request the generation of an appropriate name automatically. Name is primarily intended for creation idempotence and configuration definition. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/identifiers#names
+
+
+
namespace string
+
Namespace defines the space within each name must be unique. An empty namespace is equivalent to the "default" namespace, but "default" is the canonical representation. Not all objects are required to be scoped to a namespace - the value of this field for those objects will be empty. Must be a DNS_LABEL. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/namespaces
List of objects depended by this object. If ALL objects in the list have been deleted, this object will be garbage collected. If this object is managed by a controller, then an entry in this list will point to this controller, with the controller field set to true. There cannot be more than one managing controller.
+
+
+
resourceVersion string
+
An opaque value that represents the internal version of this object that can be used by clients to determine when objects have changed. May be used for optimistic concurrency, change detection, and the watch operation on a resource or set of resources. Clients must treat these values as opaque and passed unmodified back to the server. They may only be valid for a particular resource or set of resources. Populated by the system. Read-only. Value must be treated as opaque by clients and . More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#concurrency-control-and-consistency
+
+
+
selfLink string
+
SelfLink is a URL representing this object. Populated by the system. Read-only.
+
+
+
uid string
+
UID is the unique in time and space value for this object. It is typically generated by the server on successful creation of a resource and is not allowed to change on PUT operations. Populated by the system. Read-only. More info: http://kubernetes.io/docs/user-guide/identifiers#uids
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
ControllerPublishSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI ControllerPublishVolume and ControllerUnpublishVolume calls. This field is optional, and may be empty if no secret is required. If the secret object contains more than one secret, all secrets are passed.
+||||||| merged common ancestors
+
path string
+
The full path to the volume on the node For alpha, this path must be a directory Once block as a source is supported, then this path can point to a block device
Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified.
+||||||| merged common ancestors
+
autoscaling
+
v2beta1
+
MetricSpec
+=======
+
autoscaling
+
v2beta1
+
ObjectMetricStatus
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
MetricSpec specifies how to scale based on a single metric (only type and one other matching field should be set at once).
+
+
+
+
+=======
+
+
+
ObjectMetricStatus indicates the current value of a metric describing a kubernetes object (for example, hits-per-second on an Ingress object).
+
+
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
NodePublishSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodePublishVolume and NodeUnpublishVolume calls. This field is optional, and may be empty if no secret is required. If the secret object contains more than one secret, all secrets are passed.
NodeStageSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodeStageVolume and NodeStageVolume and NodeUnstageVolume calls. This field is optional, and may be empty if no secret is required. If the secret object contains more than one secret, all secrets are passed.
readOnly boolean
Optional: The value to pass to ControllerPublishVolumeRequest. Defaults to false (read/write).
pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second). The values will be averaged together before being compared to the target value.
resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the "pods" source.
+=======
+
metricName string
+
metricName is the name of the metric in question.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second). The values will be averaged together before being compared to the target value.
resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the "pods" source.
+=======
+
apiVersion string
+
API version of the referent.
+
+
+
fieldPath string
+
If referring to a piece of an object instead of an entire object, this string should contain a valid JSON/Go field access statement, such as desiredState.manifest.containers[2]. For example, if the object reference is to a container within a pod, this would take on a value like: "spec.containers{name}" (where "name" refers to the name of the container that triggered the event) or if no container name is specified "spec.containers[2]" (container with index 2 in this pod). This syntax is chosen only to have some well-defined way of referencing a part of an object.
Represents a Ceph Filesystem mount that lasts the lifetime of a pod Cephfs volumes do not support ownership management or SELinux relabeling.
+||||||| merged common ancestors
+=======
+
OwnerReference contains enough information to let you identify an owning object. Currently, an owning object must be in the same namespace, so there is no namespace field.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
If true, AND if the owner has the "foregroundDeletion" finalizer, then the owner cannot be deleted from the key-value store until this reference is removed. Defaults to false. To set this field, a user needs "delete" permission of the owner, otherwise 422 (Unprocessable Entity) will be returned.
+
+
+
controller boolean
+
If true, this reference points to the managing controller.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
NetworkPolicyEgressRule describes a particular set of traffic that is allowed out of pods matched by a NetworkPolicySpec's podSelector. The traffic must match both ports and to. This type is beta-level in 1.8
+=======
+
PersistentVolumeClaimCondition contails details about state of pvc
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
List of destination ports for outgoing traffic. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.
List of destinations for outgoing traffic of pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all destinations (traffic not restricted by destination). If this field is present and contains at least one item, this rule allows traffic only if the traffic matches at least one item in the to list.
Last time the condition transitioned from one status to another.
+
+
+
message string
+
Human-readable message indicating details about last transition.
+
+
+
reason string
+
Unique, this should be a short, machine understandable string that gives the reason for condition's last transition. If it reports "ResizeStarted" that means the underlying persistent volume is being resized.
+
+
+
status string
+
+
+
+
type string
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Represents a cinder volume resource in Openstack. A Cinder volume must exist before mounting to a container. The volume must also be in the same region as the kubelet. Cinder volumes support ownership management and SELinux relabeling.
+||||||| merged common ancestors
+
+
+
NetworkPolicyIngressRule describes a particular set of traffic that is allowed to the pods matched by a NetworkPolicySpec's podSelector. The traffic must match both ports and from.
+=======
+
PersistentVolumeClaimVolumeSource references the user's PVC in the same namespace. This volume finds the bound PV and mounts that volume for the pod. A PersistentVolumeClaimVolumeSource is, essentially, a wrapper around another type of volume that is owned by someone else (the system).
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
List of sources which should be able to access the pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all sources (traffic not restricted by source). If this field is present and contains at least on item, this rule allows traffic only if the traffic matches at least one item in the from list.
List of ports which should be made accessible on the pods selected for this rule. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.
+=======
+
readOnly boolean
+
Will force the ReadOnly setting in VolumeMounts. Default false.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
timeoutSeconds specifies the seconds of ClientIP type session sticky time. The value must be >0 && <=86400(for 1 day) if ServiceAffinity == "ClientIP". Default value is 10800(for 3 hours).
Selects Namespaces using cluster scoped-labels. This matches all pods in all namespaces selected by this label selector. This field follows standard label selector semantics. If present but empty, this selector selects all namespaces.
This is a label selector which selects Pods in this namespace. This field follows standard label selector semantics. If present but empty, this selector selects all pods in this namespace.
+=======
+
fsType string
+
Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified.
+
+
+
pdID string
+
ID that identifies Photon Controller persistent disk
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Condition error code for a component. For example, a health check error code.
+||||||| merged common ancestors
+
port
+
The port on the given protocol. This can either be a numerical or named port on a pod. If this field is not provided, this matches all port names and numbers.
The scheduler will prefer to schedule pods to nodes that satisfy the affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding "weight" to the sum if the node has pods which matches the corresponding podAffinityTerm; the node(s) with the highest sum are the most preferred.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
ConfigMapEnvSource selects a ConfigMap to populate the environment variables with.
The contents of the target ConfigMap's Data field will represent the key-value pairs as environment variables.
+||||||| merged common ancestors
+
NodeAddress contains information for the node's address.
+=======
+
Defines a set of pods (namely those matching the labelSelector relative to the given namespace(s)) that this pod should be co-located (affinity) or not co-located (anti-affinity) with, where co-located is defined as running on a node whose value of the label with key <topologyKey> matches that of any node on which a pod of the set of pods is running
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Node address type, one of Hostname, ExternalIP or InternalIP.
+=======
+
namespaces string array
+
namespaces specifies which namespaces the labelSelector applies to (matches against); null or empty list means "this pod's namespace"
+
+
+
topologyKey string
+
This pod should be co-located (affinity) or not co-located (anti-affinity) with the pods matching the labelSelector in the specified namespaces, where co-located is defined as running on a node whose value of the label with key topologyKey matches that of any node on which any of the selected pods is running. Empty topologyKey is not allowed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The contents of the target ConfigMap's Data field will be presented in a projected volume as files using the keys in the Data field as the file names, unless the items element is populated with specific mappings of keys to paths. Note that this is identical to a configmap volume source without the default mode.
+||||||| merged common ancestors
+
NodeCondition contains condition information for a node.
+=======
+
PodCondition contains details for the current condition of this pod.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
If unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'.
The contents of the target ConfigMap's Data field will be presented in a volume as files using the keys in the Data field as the file names, unless the items element is populated with specific mappings of keys to paths. ConfigMap volumes support ownership management and SELinux relabeling.
+||||||| merged common ancestors
+
NodeConfigSource specifies a source of node configuration. Exactly one subfield (excluding metadata) must be non-nil.
+=======
+
PodDNSConfig defines the DNS parameters of a pod in addition to those generated from DNSPolicy.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Optional: mode bits to use on created files by default. Must be a value between 0 and 0777. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.
A list of DNS name server IP addresses. This will be appended to the base nameservers generated from DNSPolicy. Duplicated nameservers will be removed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
If unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'.
A list of DNS resolver options. This will be merged with the base options generated from DNSPolicy. Duplicated entries will be removed. Resolution options given in Options will override those that appear in the base DNSPolicy.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
A list of DNS search domains for host-name lookup. This will be appended to the base search paths generated from DNSPolicy. Duplicated search paths will be removed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
ContainerPort represents a network port in a single container.
+||||||| merged common ancestors
+
A node selector represents the union of the results of one or more label queries over a set of nodes; that is, it represents the OR of the selectors represented by the node selector terms.
+=======
+
PodSecurityContext holds pod-level security attributes and common container settings. Some fields are also present in container.securityContext. Field values of container.securityContext take precedence over field values of PodSecurityContext.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Required. A list of node selector terms. The terms are ORed.
+=======
+
fsGroup integer
+
A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to change the ownership of that volume to be owned by the pod: 1. The owning GID will be the FSGroup 2. The setgid bit is set (new files created in the volume will be owned by FSGroup) 3. The permission bits are OR'd with rw-rw---- If unset, the Kubelet will not modify the ownership and permissions of any volume.
+
+
+
runAsGroup integer
+
The GID to run the entrypoint of the container process. Uses runtime default if unset. May also be set in SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container.
+
+
+
runAsNonRoot boolean
+
Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed. May also be set in SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.
+
+
+
runAsUser integer
+
The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified. May also be set in SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container.
The SELinux context to be applied to all containers. If unspecified, the container runtime will allocate a random SELinux context for each container. May also be set in SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container.
+
+
+
supplementalGroups integer array
+
A list of groups applied to the first process run in each container, in addition to the container's primary GID. If unspecified, no groups will be added to any container.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
ContainerState holds a possible state of container. Only one of its members may be specified. If none of them is specified, the default one is ContainerStateWaiting.
+||||||| merged common ancestors
+
A node selector requirement is a selector that contains values, a key, and an operator that relates the key and values.
+=======
+
PodsMetricSource indicates how to scale on a metric describing each pod in the current scale target (for example, transactions-processed-per-second). The values will be averaged together before being compared to the target value.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. If the operator is Gt or Lt, the values array must have a single element, which will be interpreted as an integer. This array is replaced during a strategic merge patch.
ContainerStateRunning is a running state of a container.
+||||||| merged common ancestors
+
A null or empty node selector term matches no objects.
+=======
+
PodsMetricStatus indicates the current value of a metric describing each pod in the current scale target (for example, transactions-processed-per-second).
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
ContainerStateTerminated is a terminated state of a container.
+||||||| merged common ancestors
+
NodeSystemInfo is a set of ids/uuids to uniquely identify the node.
+=======
+
+
+
PolicyRule holds information that describes a policy rule, but does not contain information about who the rule applies to or which namespace the rule applies to.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
ContainerRuntime Version reported by the node through runtime remote API (e.g. docker://1.5.0).
+
+
+
kernelVersion string
+
Kernel Version reported by the node from 'uname -r' (e.g. 3.16.0-0.bpo.4-amd64).
+
+
+
kubeProxyVersion string
+
KubeProxy Version reported by the node.
+
+
+
kubeletVersion string
+
Kubelet Version reported by the node.
+=======
+
apiGroups string array
+
APIGroups is the name of the APIGroup that contains the resources. If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
NonResourceURLs is a set of partial urls that a user should have access to. *s are allowed, but only as the full, final step in the path Since non-resource URLs are not namespaced, this field is only applicable for ClusterRoles referenced from a ClusterRoleBinding. Rules can either apply to API resources (such as "pods" or "secrets") or non-resource URL paths (such as "/api"), but not both.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Message regarding why the container is not yet running.
+||||||| merged common ancestors
+
path string
+
Path is the URL path of the request
+=======
+
fsType string
+
FSType represents the filesystem type to mount Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs". Implicitly inferred to be "ext4" if unspecified.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
CustomResourceDefinitionCondition contains details for the current condition of this pod.
+||||||| merged common ancestors
+
ObjectFieldSelector selects an APIVersioned field of an object.
+=======
+
An empty preferred scheduling term matches all objects with implicit weight 0 (i.e. it's a no-op). A null preferred scheduling term matches no objects (i.e. is also a no-op).
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Categories is a list of grouped resources custom resources belong to (e.g. 'all')
+||||||| merged common ancestors
+
annotations object
+
Annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects. More info: http://kubernetes.io/docs/user-guide/annotations
+
clusterName string
+
The name of the cluster which the object belongs to. This is used to distinguish resources with same name and namespace in different clusters. This field is not set anywhere right now and apiserver is going to ignore it if set in create or update request.
CreationTimestamp is a timestamp representing the server time when this object was created. It is not guaranteed to be set in happens-before order across separate operations. Clients may not set this value. It is represented in RFC3339 form and is in UTC. Populated by the system. Read-only. Null for lists. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata
+
+
+
deletionGracePeriodSeconds integer
+
Number of seconds allowed for this object to gracefully terminate before it will be removed from the system. Only set when deletionTimestamp is also set. May only be shortened. Read-only.
DeletionTimestamp is RFC 3339 date and time at which this resource will be deleted. This field is set by the server when a graceful deletion is requested by the user, and is not directly settable by a client. The resource is expected to be deleted (no longer visible from resource lists, and not reachable by name) after the time in this field, once the finalizers list is empty. As long as the finalizers list contains items, deletion is blocked. Once the deletionTimestamp is set, this value may not be unset or be set further into the future, although it may be shortened or the resource may be deleted prior to this time. For example, a user may request that a pod is deleted in 30 seconds. The Kubelet will react by sending a graceful termination signal to the containers in the pod. After that 30 seconds, the Kubelet will send a hard termination signal (SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after this timestamp, until an administrator or automated process can determine the resource is fully terminated. If not set, graceful deletion of the object has not been requested. Populated by the system when a graceful deletion is requested. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata
+
+
+
finalizers string array patch type: merge
+
Must be empty before the object is deleted from the registry. Each entry is an identifier for the responsible component that will remove the entry from the list. If the deletionTimestamp of the object is non-nil, entries in this list can only be removed.
+
+
+
generateName string
+
GenerateName is an optional prefix, used by the server, to generate a unique name ONLY IF the Name field has not been provided. If this field is used, the name returned to the client will be different than the name passed. This value will also be combined with a unique suffix. The provided value has the same validation rules as the Name field, and may be truncated by the length of the suffix required to make the value unique on the server. If this field is specified and the generated name exists, the server will NOT return a 409 - instead, it will either return 201 Created or 500 with Reason ServerTimeout indicating a unique name could not be found in the time allotted, and the client should retry (optionally after the time indicated in the Retry-After header). Applied only if Name is not specified. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#idempotency
+
+
+
generation integer
+
A sequence number representing a specific generation of the desired state. Populated by the system. Read-only.
An initializer is a controller which enforces some system invariant at object creation time. This field is a list of initializers that have not yet acted on this object. If nil or empty, this object has been completely initialized. Otherwise, the object is considered uninitialized and is hidden (in list/watch and get calls) from clients that haven't explicitly asked to observe uninitialized objects. When an object is created, the system will populate this list with the current set of initializers. Only privileged users may set or modify this list. Once it is empty, it may not be modified further by any user.
+
+
+
labels object
+
Map of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services. More info: http://kubernetes.io/docs/user-guide/labels
+
+
+
name string
+
Name must be unique within a namespace. Is required when creating resources, although some resources may allow a client to request the generation of an appropriate name automatically. Name is primarily intended for creation idempotence and configuration definition. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/identifiers#names
Kind is the serialized kind of the resource. It is normally CamelCase and singular.
+||||||| merged common ancestors
+
namespace string
+
Namespace defines the space within each name must be unique. An empty namespace is equivalent to the "default" namespace, but "default" is the canonical representation. Not all objects are required to be scoped to a namespace - the value of this field for those objects will be empty. Must be a DNS_LABEL. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/namespaces
List of objects depended by this object. If ALL objects in the list have been deleted, this object will be garbage collected. If this object is managed by a controller, then an entry in this list will point to this controller, with the controller field set to true. There cannot be more than one managing controller.
+=======
+
periodSeconds integer
+
How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Plural is the plural name of the resource to serve. It must match the name of the CustomResourceDefinition-registration too: plural.group and it must be all lowercase.
+||||||| merged common ancestors
+
resourceVersion string
+
An opaque value that represents the internal version of this object that can be used by clients to determine when objects have changed. May be used for optimistic concurrency, change detection, and the watch operation on a resource or set of resources. Clients must treat these values as opaque and passed unmodified back to the server. They may only be valid for a particular resource or set of resources. Populated by the system. Read-only. Value must be treated as opaque by clients and . More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#concurrency-control-and-consistency
+=======
+
successThreshold integer
+
Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness. Minimum value is 1.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Singular is the singular name of the resource. It must be all lowercase Defaults to lowercased <kind>
+||||||| merged common ancestors
+
uid string
+
UID is the unique in time and space value for this object. It is typically generated by the server on successful creation of a resource and is not allowed to change on PUT operations. Populated by the system. Read-only. More info: http://kubernetes.io/docs/user-guide/identifiers#uids
LabelSelectorPath defines the JSON path inside of a CustomResource that corresponds to Scale.Status.Selector. Only JSON paths without the array notation are allowed. Must be a JSON Path under .status. Must be set to work with HPA. If there is no value under the given path in the CustomResource, the status label selector value in the /scale subresource will default to the empty string.
specReplicasPath string
SpecReplicasPath defines the JSON path inside of a CustomResource that corresponds to Scale.Spec.Replicas. Only JSON paths without the array notation are allowed. Must be a JSON Path under .spec. If there is no value under the given path in the CustomResource, the /scale subresource will return an error on GET.
Mode bits to use on created files by default. Must be a value between 0 and 0777. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
StatusReplicasPath defines the JSON path inside of a CustomResource that corresponds to Scale.Status.Replicas. Only JSON paths without the array notation are allowed. Must be a JSON Path under .status. If there is no value under the given path in the CustomResource, the status replica value in the /scale subresource will default to 0.
CustomResourceSubresourceStatus defines how to serve the status subresource for CustomResources. Status is represented by the .status JSON path inside of a CustomResource. When set, exposes a /status subresource for the custom resource PUT requests to the /status subresource take a custom resource object, and ignore changes to anything except the status stanza * PUT/POST/PATCH requests to the custom resource ignore changes to the status stanza
+||||||| merged common ancestors
+
ObjectMetricStatus indicates the current value of a metric describing a kubernetes object (for example, hits-per-second on an Ingress object).
+=======
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Scale denotes the scale subresource for CustomResources
+||||||| merged common ancestors
+
apiVersion string
+
API version of the referent.
+
fieldPath string
+
If referring to a piece of an object instead of an entire object, this string should contain a valid JSON/Go field access statement, such as desiredState.manifest.containers[2]. For example, if the object reference is to a container within a pod, this would take on a value like: "spec.containers{name}" (where "name" refers to the name of the container that triggered the event) or if no container name is specified "spec.containers[2]" (container with index 2 in this pod). This syntax is chosen only to have some well-defined way of referencing a part of an object.
ReadOnly here will force the Quobyte volume to be mounted with read-only permissions. Defaults to false.
+
+
+
registry string
+
Registry represents a single or multiple Quobyte Registry services specified as a string as host:port pair (multiple entries are separated with commas) which acts as the central registry for volumes
+
+
+
user string
+
User to map volume access to Defaults to serivceaccount user
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
CustomResourceValidation is a list of validation methods for CustomResources.
+||||||| merged common ancestors
+
OwnerReference contains enough information to let you identify an owning object. Currently, an owning object must be in the same namespace, so there is no namespace field.
+=======
+
Represents a Rados Block Device mount that lasts the lifetime of a pod. RBD volumes support ownership management and SELinux relabeling.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
OpenAPIV3Schema is the OpenAPI v3 schema to be validated against.
+||||||| merged common ancestors
+
apiVersion string
+
API version of the referent.
+
+
+
blockOwnerDeletion boolean
+
If true, AND if the owner has the "foregroundDeletion" finalizer, then the owner cannot be deleted from the key-value store until this reference is removed. Defaults to false. To set this field, a user needs "delete" permission of the owner, otherwise 422 (Unprocessable Entity) will be returned.
+
+
+
controller boolean
+
If true, this reference points to the managing controller.
Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#rbd
Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#rbd
Unique, this should be a short, machine understandable string that gives the reason for condition's last transition. If it reports "ResizeStarted" that means the underlying persistent volume is being resized.
+=======
+
reason string
+
The reason for the condition's last transition.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
DaemonSetUpdateStrategy is a struct used to control the update strategy for a DaemonSet.
+||||||| merged common ancestors
+
PersistentVolumeClaimVolumeSource references the user's PVC in the same namespace. This volume finds the bound PV and mounts that volume for the pod. A PersistentVolumeClaimVolumeSource is, essentially, a wrapper around another type of volume that is owned by someone else (the system).
+=======
+
ReplicationControllerCondition describes the state of a replication controller at a certain point.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified.
+=======
+
group string
+
Group is the API Group of the Resource. "*" means all.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
@@ -69574,10 +115399,43 @@ Appears In:
propagationPolicy string
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+||||||| merged common ancestors
+
pdID string
+
ID that identifies Photon Controller persistent disk
+=======
+
name string
+
Name is the name of the resource being requested for a "get" or deleted for a "delete". "" (empty) means all.
+
+
+
namespace string
+
Namespace is the namespace of the action being requested. Currently, there is no distinction between no namespace and all namespaces "" (empty) is defaulted for LocalSubjectAccessReviews "" (empty) is empty for cluster-scoped resources "" (empty) means "all" for namespace scoped resources from a SubjectAccessReview or SelfSubjectAccessReview
+
+
+
resource string
+
Resource is one of the existing resource types. "*" means all.
+
+
+
subresource string
+
Subresource is one of the existing resource types. "" means none.
+
+
+
verb string
+
Verb is a kubernetes resource API verb, like: get, list, watch, create, update, delete, proxy. "*" means all.
+
+
+
version string
+
Version is the API Version of the Resource. "*" means all.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The scheduler will prefer to schedule pods to nodes that satisfy the affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding "weight" to the sum if the node has pods which matches the corresponding podAffinityTerm; the node(s) with the highest sum are the most preferred.
+=======
+
containerName string
+
Container name: required for volumes, optional for env vars
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.
Represents downward API info for projecting into a projected volume. Note that this is identical to a downwardAPI volume source without the default mode.
+||||||| merged common ancestors
+
Defines a set of pods (namely those matching the labelSelector relative to the given namespace(s)) that this pod should be co-located (affinity) or not co-located (anti-affinity) with, where co-located is defined as running on a node whose value of the label with key <topologyKey> matches that of any node on which a pod of the set of pods is running
+=======
+
ResourceMetricSource indicates how to scale on a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory). The values will be averaged together before being compared to the target. Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the "pods" source. Only one "target" type should be set.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
A label query over a set of resources, in this case pods.
+
+
+
namespaces string array
+
namespaces specifies which namespaces the labelSelector applies to (matches against); null or empty list means "this pod's namespace"
+
+
+
topologyKey string
+
This pod should be co-located (affinity) or not co-located (anti-affinity) with the pods matching the labelSelector in the specified namespaces, where co-located is defined as running on a node whose value of the label with key topologyKey matches that of any node on which any of the selected pods is running. Empty topologyKey is not allowed.
+=======
+
name string
+
name is the name of the resource in question.
+
+
+
targetAverageUtilization integer
+
targetAverageUtilization is the target value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.
targetAverageValue is the target value of the average of the resource metric across all relevant pods, as a raw value (instead of as a percentage of the request), similar to the "pods" metric source type.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
DownwardAPIVolumeFile represents information to create the file containing the pod field
+||||||| merged common ancestors
+
Pod anti affinity is a group of inter pod anti affinity scheduling rules.
+=======
+
ResourceMetricStatus indicates the current value of a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the "pods" source.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The scheduler will prefer to schedule pods to nodes that satisfy the anti-affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling anti-affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding "weight" to the sum if the node has pods which matches the corresponding podAffinityTerm; the node(s) with the highest sum are the most preferred.
+=======
+
currentAverageUtilization integer
+
currentAverageUtilization is the current value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods. It will only be present if targetAverageValue was set in the corresponding metric specification.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Optional: mode bits to use on this file, must be a value between 0 and 0777. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.
Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, requests.cpu and requests.memory) are currently supported.
If the anti-affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the anti-affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.
currentAverageValue is the current value of the average of the resource metric across all relevant pods, as a raw value (instead of as a percentage of the request), similar to the "pods" metric source type. It will always be set, regardless of the corresponding metric specification.
+
+
+
name string
+
name is the name of the resource in question.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Optional: mode bits to use on created files by default. Must be a value between 0 and 0777. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.
Represents an empty directory for a pod. Empty directory volumes support ownership management and SELinux relabeling.
+||||||| merged common ancestors
+
PodDNSConfig defines the DNS parameters of a pod in addition to those generated from DNSPolicy.
+=======
+
+
+
ResourceRule is the list of actions the subject is allowed to perform on resources. The list ordering isn't significant, may contain duplicates, and possibly be incomplete.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
A list of DNS name server IP addresses. This will be appended to the base nameservers generated from DNSPolicy. Duplicated nameservers will be removed.
A list of DNS resolver options. This will be merged with the base options generated from DNSPolicy. Duplicated entries will be removed. Resolution options given in Options will override those that appear in the base DNSPolicy.
+=======
+
apiGroups string array
+
APIGroups is the name of the APIGroup that contains the resources. If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed. "*" means all.
+
+
+
resourceNames string array
+
ResourceNames is an optional white list of names that the rule applies to. An empty set means that everything is allowed. "*" means all.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
Total amount of local storage required for this EmptyDir volume. The size limit is also applicable for memory medium. The maximum usage on memory medium EmptyDir would be the minimum value between the SizeLimit specified here and the sum of memory limits of all containers in a pod. The default is nil which means that the limit is undefined. More info: http://kubernetes.io/docs/user-guide/volumes#emptydir
+||||||| merged common ancestors
+
searches string array
+
A list of DNS search domains for host-name lookup. This will be appended to the base search paths generated from DNSPolicy. Duplicated search paths will be removed.
+=======
+
resources string array
+
Resources is a list of resources this rule applies to. "" means all in the specified apiGroups. "/foo" represents the subresource 'foo' for all resources in the specified apiGroups.
+
+
+
verbs string array
+
Verb is a list of kubernetes resource API verbs, like: get, list, watch, create, update, delete, proxy. "*" means all.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The IP of this endpoint. May not be loopback (127.0.0.0/8), link-local (169.254.0.0/16), or link-local multicast ((224.0.0.0/24). IPv6 is also accepted but not fully supported on all platforms. Also, certain kubernetes components, like kube-proxy, are not IPv6 ready.
EndpointPort is a tuple that describes a single port.
+||||||| merged common ancestors
+
PodSecurityContext holds pod-level security attributes and common container settings. Some fields are also present in container.securityContext. Field values of container.securityContext take precedence over field values of PodSecurityContext.
+=======
+
DEPRECATED.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The name of this port (corresponds to ServicePort.Name). Must be a DNS_LABEL. Optional only if one port is defined.
@@ -69910,10 +116113,39 @@ Appears In:
protocol string
The IP protocol for this port. Must be UDP or TCP. Default is TCP.
+||||||| merged common ancestors
+
fsGroup integer
+
A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to change the ownership of that volume to be owned by the pod: 1. The owning GID will be the FSGroup 2. The setgid bit is set (new files created in the volume will be owned by FSGroup) 3. The permission bits are OR'd with rw-rw---- If unset, the Kubelet will not modify the ownership and permissions of any volume.
+
+
+
runAsNonRoot boolean
+
Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed. May also be set in SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.
+
+
+
runAsUser integer
+
The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified. May also be set in SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container.
The SELinux context to be applied to all containers. If unspecified, the container runtime will allocate a random SELinux context for each container. May also be set in SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container.
+
+
+
supplementalGroups integer array
+
A list of groups applied to the first process run in each container, in addition to the container's primary GID. If unspecified, no groups will be added to any container.
+=======
+
revision integer
+
The revision to rollback to. If set to 0, rollback to the last revision.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
EndpointSubset is a group of addresses with a common set of ports. The expanded set of endpoints is the Cartesian product of Addresses x Ports. For example, given:
{
Addresses: [{"ip": "10.10.1.1"}, {"ip": "10.10.2.2"}],
@@ -69938,11 +116181,24 @@ Appears In:
The resulting set of endpoints can be viewed as:
a: [ 10.10.1.1:8675, 10.10.2.2:8675 ],
b: [ 10.10.1.1:309, 10.10.2.2:309 ]
+||||||| merged common ancestors
+
PodsMetricSource indicates how to scale on a metric describing each pod in the current scale target (for example, transactions-processed-per-second). The values will be averaged together before being compared to the target value.
+=======
+
+
+
RollingUpdateStatefulSetStrategy is used to communicate parameter for RollingUpdateStatefulSetStrategyType.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
IP addresses which offer the related ports that are marked as ready. These endpoints should be considered safe for load balancers and clients to utilize.
EnvFromSource represents the source of a set of ConfigMaps
+||||||| merged common ancestors
+
PodsMetricStatus indicates the current value of a metric describing each pod in the current scale target (for example, transactions-processed-per-second).
+=======
+
Rule is a tuple of APIGroups, APIVersion, and Resources.It is recommended to make sure that all the tuple expansions are valid.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
APIVersions is the API versions the resources belong to. '' is all versions. If '' is present, the length of the slice must be one. Required.
+
+
+
resources string array
+
Resources is a list of resources this rule applies to. For example: 'pods' means pods. 'pods/log' means the log subresource of pods. '' means all resources, but not subresources. 'pods/' means all subresources of pods. '/scale' means all scale subresources. '/*' means all resources and their subresources. If wildcard is present, the validation rule will ensure resources do not overlap with each other. Depending on the enclosing object, subresources might not be allowed. Required.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
EnvVar represents an environment variable present in a Container.
+||||||| merged common ancestors
+
+
+
PolicyRule holds information that describes a policy rule, but does not contain information about who the rule applies to or which namespace the rule applies to.
+=======
+
RuleWithOperations is a tuple of Operations and Resources. It is recommended to make sure that all the tuple expansions are valid.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Name of the environment variable. Must be a C_IDENTIFIER.
+||||||| merged common ancestors
+
apiGroups string array
+
APIGroups is the name of the APIGroup that contains the resources. If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed.
+
nonResourceURLs string array
+
NonResourceURLs is a set of partial urls that a user should have access to. *s are allowed, but only as the full, final step in the path Since non-resource URLs are not namespaced, this field is only applicable for ClusterRoles referenced from a ClusterRoleBinding. Rules can either apply to API resources (such as "pods" or "secrets") or non-resource URL paths (such as "/api"), but not both.
+
+
+
resourceNames string array
+
ResourceNames is an optional white list of names that the rule applies to. An empty set means that everything is allowed.
+=======
+
apiGroups string array
+
APIGroups is the API groups the resources belong to. '' is all groups. If '' is present, the length of the slice must be one. Required.
+
+
+
apiVersions string array
+
APIVersions is the API versions the resources belong to. '' is all versions. If '' is present, the length of the slice must be one. Required.
+
+
+
operations string array
+
Operations is the operations the admission hook cares about - CREATE, UPDATE, or for all operations. If '' is present, the length of the slice must be one. Required.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
Variable references $(VAR_NAME) are expanded using the previous defined environment variables in the container and any service environment variables. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Defaults to "".
Source for the environment variable's value. Cannot be used if value is not empty.
+||||||| merged common ancestors
+
resources string array
+
Resources is a list of resources this rule applies to. ResourceAll represents all resources.
+
+
+
verbs string array
+
Verbs is a list of Verbs that apply to ALL the ResourceKinds and AttributeRestrictions contained in this rule. VerbAll represents all kinds.
+=======
+
resources string array
+
Resources is a list of resources this rule applies to. For example: 'pods' means pods. 'pods/log' means the log subresource of pods. '' means all resources, but not subresources. 'pods/' means all subresources of pods. '/scale' means all scale subresources. '/*' means all resources and their subresources. If wildcard is present, the validation rule will ensure resources do not overlap with each other. Depending on the enclosing object, subresources might not be allowed. Required.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Selects a field of the pod: supports metadata.name, metadata.namespace, metadata.labels, metadata.annotations, spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP.
+||||||| merged common ancestors
+
fsType string
+
FSType represents the filesystem type to mount Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs". Implicitly inferred to be "ext4" if unspecified.
+
readOnly boolean
+
Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.
Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, limits.ephemeral-storage, requests.cpu, requests.memory and requests.ephemeral-storage) are currently supported.
An empty preferred scheduling term matches all objects with implicit weight 0 (i.e. it's a no-op). A null preferred scheduling term matches no objects (i.e. is also a no-op).
+=======
+
SELinux Strategy Options defines the strategy type and any options used to create the strategy.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Eviction evicts a pod from its node subject to certain policies and safety constraints. This is a subresource of Pod. A request to cause such an eviction is created by POSTing to .../pods/<pod name>/evictions.
+||||||| merged common ancestors
+
Probe describes a health check to be performed against a container to determine whether it is alive or ready to receive traffic.
+
+
+=======
+
+
+
Scale represents a scaling request for a resource.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness. Minimum value is 1.
Command is the command line to execute inside the container, the working directory for the command is root ('/') in the container's filesystem. The command is simply exec'd, it is not run inside a shell, so traditional shell instructions ('
', etc) won't work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy.
Mode bits to use on created files by default. Must be a value between 0 and 0777. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.
+=======
+
fsType string
+
Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
ExternalMetricSource indicates how to scale on a metric not associated with any Kubernetes object (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster). Exactly one "target" type should be set.
+||||||| merged common ancestors
+=======
+
ScaleIOVolumeSource represents a persistent ScaleIO volume
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
targetValue is the target value of the metric (as a quantity). Mutually exclusive with TargetAverageValue.
+||||||| merged common ancestors
+
+=======
+
fsType string
+
Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified.
+
+
+
gateway string
+
The host address of the ScaleIO API Gateway.
+
+
+
protectionDomain string
+
The name of the ScaleIO Protection Domain for the configured storage.
+
+
+
readOnly boolean
+
Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.
currentAverageValue is the current value of metric averaged over autoscaled pods.
@@ -70446,14 +117240,47 @@ Appears In:
metricName string
metricName is the name of a metric used for autoscaling in metric system.
+||||||| merged common ancestors
+
group string
+
Group to map volume access to Default is no group
+
readOnly boolean
+
ReadOnly here will force the Quobyte volume to be mounted with read-only permissions. Defaults to false.
+
+
+
registry string
+
Registry represents a single or multiple Quobyte Registry services specified as a string as host:port pair (multiple entries are separated with commas) which acts as the central registry for volumes
+
+
+
user string
+
User to map volume access to Defaults to serivceaccount user
Represents a Fibre Channel volume. Fibre Channel volumes can only be mounted as read/write once. Fibre Channel volumes support ownership management and SELinux relabeling.
+||||||| merged common ancestors
+
Represents a Rados Block Device mount that lasts the lifetime of a pod. RBD volumes support ownership management and SELinux relabeling.
+=======
+
SecretKeySelector selects a key of a Secret.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified.
@@ -70498,18 +117348,67 @@ Appears In:
readOnly boolean
Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.
+||||||| merged common ancestors
+
fsType string
+
Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#rbd
FSGroupStrategyOptions defines the strategy type and options used to create the strategy.
+||||||| merged common ancestors
+
Represents a Rados Block Device mount that lasts the lifetime of a pod. RBD volumes support ownership management and SELinux relabeling.
+=======
+
Adapts a secret into a projected volume.
+
The contents of the target Secret's Data field will be presented in a projected volume as files using the keys in the Data field as the file names. Note that this is identical to a secret volume source without the default mode.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Ranges are the allowed ranges of fs groups. If you would like to force a single fs group then supply a single range with the same start and end.
+||||||| merged common ancestors
+
fsType string
+
Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#rbd
If unspecified, each key-value pair in the Data field of the referenced Secret will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the Secret, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'.
Optional: SecretRef is reference to the secret object containing sensitive information to pass to the plugin scripts. This may be empty if no secret object is specified. If the secret object contains more than one secret, all secrets are passed to the plugin scripts.
+||||||| merged common ancestors
+
type string
+
Type of replica set condition.
+=======
+
namespace string
+
Namespace defines the space within which the secret name must be unique.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.
+||||||| merged common ancestors
+
ReplicationControllerCondition describes the state of a replication controller at a certain point.
+=======
+
Adapts a Secret into a volume.
+
The contents of the target Secret's Data field will be presented in a volume as files using the keys in the Data field as the file names. Secret volumes support ownership management and SELinux relabeling.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+=======
+
Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified.
+
readOnly boolean
+
Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.
PreStop is called immediately before a container is terminated. The container is terminated after the handler completes. The reason for termination is passed to the handler. Regardless of the outcome of the handler, the container is eventually terminated. Other management of the container blocks until the hook completes. More info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks
+||||||| merged common ancestors
+
volumeNamespace string
+
VolumeNamespace specifies the scope of the volume within StorageOS. If no namespace is specified then the Pod's namespace will be used. This allows the Kubernetes name scoping to be mirrored within StorageOS for tighter integration. Set VolumeName to any name to override the default behaviour. Set to "default" if you are not using namespaces within StorageOS. Namespaces that do not pre-exist within StorageOS will be created.
Default resource requirement limit value by resource name if resource limit is omitted.
+||||||| merged common ancestors
+
fsType string
+
Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified.
+=======
+
caBundle string
+
CABundle is a PEM encoded CA bundle which will be used to validate an API server's serving certificate.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
SecretRef specifies the secret to use for obtaining the StorageOS API credentials. If not specified, default values will be attempted.
+=======
+
groupPriorityMinimum integer
+
GroupPriorityMininum is the priority this group should have at least. Higher priority means that the group is preferred by clients over lower priority ones. Note that other versions of this group might specify even higher GroupPriorityMininum values such that the whole group gets a higher priority. The primary sort is based on GroupPriorityMinimum, ordered highest number to lowest (20 before 10). The secondary sort is based on the alphabetical comparison of the name of the object. (v1.bar before v1.foo) We'd recommend something like: *.k8s.io (except extensions) at 18000 and PaaSes (OpenShift, Deis) are recommended to be in the 2000s
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
MaxLimitRequestRatio if specified, the named resource must have a request and limit that are both non-zero where limit divided by request is less than or equal to the enumerated value; this represents the max burst for the named resource.
+||||||| merged common ancestors
+
volumeName string
+
VolumeName is the human-readable name of the StorageOS volume. Volume names are only unique within a namespace.
+=======
+
insecureSkipTLSVerify boolean
+
InsecureSkipTLSVerify disables TLS certificate verification when communicating with this server. This is strongly discouraged. You should use the CABundle instead.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Min usage constraints on this kind by resource name.
type string
Type of resource that this limit applies to.
+||||||| merged common ancestors
+
volumeNamespace string
+
VolumeNamespace specifies the scope of the volume within StorageOS. If no namespace is specified then the Pod's namespace will be used. This allows the Kubernetes name scoping to be mirrored within StorageOS for tighter integration. Set VolumeName to any name to override the default behaviour. Set to "default" if you are not using namespaces within StorageOS. Namespaces that do not pre-exist within StorageOS will be created.
Service is a reference to the service for this API server. It must communicate on port 443 If the Service is nil, that means the handling for the API groupversion is handled locally on this server. The call will simply delegate to the normal handler chain to be fulfilled.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
VersionPriority controls the ordering of this API version inside of its group. Must be greater than zero. The primary sort is based on VersionPriority, ordered highest to lowest (20 before 10). The secondary sort is based on the alphabetical comparison of the name of the object. (v1.bar before v1.foo) Since it's inside of a group, the number can be small, probably in the 10s.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
ListMeta describes metadata that synthetic resources must have, including lists and various status objects. A resource may have only one of {ObjectMeta, ListMeta}.
+||||||| merged common ancestors
+
+
+
Subject contains a reference to the object or user identities a role binding applies to. This can either hold a direct API object reference, or a value for non-objects such as user and group names.
+=======
+
APIServiceStatus v1beta1 apiregistration
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
continue may be set if the user set a limit on the number of items returned, and indicates that the server has more data available. The value is opaque and may be used to issue another request to the endpoint that served this list to retrieve the next set of available objects. Continuing a list may not be possible if the server configuration has changed or more than a few minutes have passed. The resourceVersion field returned when using this continue value will be identical to the value in the first response.
@@ -72565,34 +121752,35 @@ Appears In:
selfLink string
selfLink is a URL representing this object. Populated by the system. Read-only.
+||||||| merged common ancestors
+
apiGroup string
+
APIGroup holds the API group of the referenced subject. Defaults to "" for ServiceAccount subjects. Defaults to "rbac.authorization.k8s.io" for User and Group subjects.
+
+
+
kind string
+
Kind of object being referenced. Values defined by this API group are "User", "Group", and "ServiceAccount". If the Authorizer does not recognized the kind value, the Authorizer should report an error.
+
+
+
name string
+
Name of the object being referenced.
+
+
+
namespace string
+
Namespace of the referenced object. If the object kind is non-namespace, such as "User" or "Group", and this value is not empty the Authorizer should report an error.
+=======
+
conditions APIServiceCondition array patch type: merge patch merge key: type
+
Current service state of apiService.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Hostname is set for load-balancer ingress points that are DNS based (typically AWS load-balancers)
ip string
IP is set for load-balancer ingress points that are IP based (typically GCE or OpenStack load-balancers)
+||||||| merged common ancestors
+
evaluationError string
+
EvaluationError can appear in combination with Rules. It indicates an error occurred during rule evaluation, such as an authorizer that doesn't support rule evaluation, and that ResourceRules and/or NonResourceRules may be incomplete.
+
+
+
incomplete boolean
+
Incomplete is true when the rules returned by this call are incomplete. This is most commonly encountered when an authorizer, such as an external authorizer, doesn't support rules evaluation.
NonResourceRules is the list of actions the subject is allowed to perform on non-resources. The list ordering isn't significant, may contain duplicates, and possibly be incomplete.
ResourceRules is the list of actions the subject is allowed to perform on resources. The list ordering isn't significant, may contain duplicates, and possibly be incomplete.
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Ranges are the allowed ranges of supplemental groups. If you would like to force a single supplemental group then supply a single range with the same start and end.
+
+
+
rule string
+
Rule is the strategy that will dictate what supplemental groups is used in the SecurityContext.
Local represents directly-attached storage with node affinity
+||||||| merged common ancestors
+
TCPSocketAction describes an action based on opening a socket
+=======
+
Query Parameters
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
-
Field
+
Parameter
Description
-
path string
-
The full path to the volume on the node For alpha, this path must be a directory Once block as a source is supported, then this path can point to a block device
The full path to the volume on the node For alpha, this path must be a directory Once block as a source is supported, then this path can point to a block device
+||||||| merged common ancestors
+
effect string
+
Required. The effect of the taint on pods that do not tolerate the taint. Valid effects are NoSchedule, PreferNoSchedule and NoExecute.
external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).
@@ -72788,26 +122378,83 @@ Appears In:
type string
type is the type of metric source. It should be one of "Object", "Pods" or "Resource", each mapping to a matching field in the object.
external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).
+||||||| merged common ancestors
+
effect string
+
Effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).
+||||||| merged common ancestors
+
key string
+
Key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.
+=======
+
gracePeriodSeconds
+
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second). The values will be averaged together before being compared to the target value.
+||||||| merged common ancestors
+
operator string
+
Operator represents a key's relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.
+=======
+
orphanDependents
+
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the "pods" source.
-
-
-
type string
-
type is the type of metric source. It will be one of "Object", "Pods" or "Resource", each corresponds to a matching field in the object.
+||||||| merged common ancestors
+
tolerationSeconds integer
+
TolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.
+=======
+
propagationPolicy
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Any additional information provided by the authenticator.
+
+
groups string array
+
The names of groups this user is a part of.
+
+
+
uid string
+
A unique value that identifies this user across time. If this user is deleted and another user by the same name is added, they will have different UIDs.
+
+
+
username string
+
The name that uniquely identifies this user among all active users.
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Represents an NFS mount that lasts the lifetime of a pod. NFS volumes do not support ownership management or SELinux relabeling.
+||||||| merged common ancestors
+
VolumeAttachmentSource represents a volume that should be attached. Right now only PersistenVolumes can be attached via external attacher, in future we may allow also inline volumes in pods. Exactly one member can be set.
+
+
+=======
+
Response
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
NetworkPolicyEgressRule describes a particular set of traffic that is allowed out of pods matched by a NetworkPolicySpec's podSelector. The traffic must match both ports and to. This type is beta-level in 1.8
List of destination ports for outgoing traffic. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.
+||||||| merged common ancestors
+
devicePath string
+
devicePath is the path inside of the container that the device will be mapped to.
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
List of destinations for outgoing traffic of pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all destinations (traffic not restricted by destination). If this field is present and contains at least one item, this rule allows traffic only if the traffic matches at least one item in the to list.
+||||||| merged common ancestors
+
name string
+
name must match the name of a persistentVolumeClaim in the pod
+=======
+
exact
+
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
+
+
+
export
+
Should this value be exported. Export strips fields that a user can not specify.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
NetworkPolicyIngressRule describes a particular set of traffic that is allowed to the pods matched by a NetworkPolicySpec's podSelector. The traffic must match both ports and from.
+=======
+
+
+
curl Command (requires kubectl proxy to be running)
List of sources which should be able to access the pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all sources (traffic not restricted by source). If this field is present and contains at least on item, this rule allows traffic only if the traffic matches at least one item in the from list.
+||||||| merged common ancestors
+
message string
+
String detailing the error encountered during Attach or Detach operation. This string maybe logged, so it should not contain sensitive information.
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
List of ports which should be made accessible on the pods selected for this rule. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Selects Namespaces using cluster scoped-labels. This matches all pods in all namespaces selected by this label selector. This field follows standard label selector semantics. If present but empty, this selector selects all namespaces.
+
mountPropagation string
+
mountPropagation determines how mounts are propagated from the host to container and the other way around. When not set, MountPropagationHostToContainer is used. This field is alpha in 1.8 and can be reworked or removed in a future release.
This is a label selector which selects Pods in this namespace. This field follows standard label selector semantics. If present but empty, this selector selects all pods in this namespace.
+
name string
+
This must match the Name of a Volume.
+=======
+
name
+
name of the APIService
-
NetworkPolicyPort v1 networking
+
Query Parameters
-
Group
-
Version
-
Kind
+
Parameter
+
Description
-
networking.k8s.io
-
v1
-
NetworkPolicyPort
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
Selects Namespaces using cluster scoped-labels. This matches all pods in all namespaces selected by this label selector. This field follows standard label selector semantics. If present but empty, this selector selects all namespaces.
+||||||| merged common ancestors
+
readOnly boolean
+
Mounted read-only if true, read-write otherwise (false or unspecified). Defaults to false.
+=======
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
This is a label selector which selects Pods in this namespace. This field follows standard label selector semantics. If present but empty, this selector selects all pods in this namespace.
+||||||| merged common ancestors
+
subPath string
+
Path within the volume from which the container's volume should be mounted. Defaults to "" (volume's root).
+=======
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The port on the given protocol. This can either be a numerical or named port on a pod. If this field is not provided, this matches all port names and numbers.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified.
-
type string
-
Node address type, one of Hostname, ExternalIP or InternalIP.
+
storagePolicyID string
+
Storage Policy Based Management (SPBM) profile ID associated with the StoragePolicyName.
+
+
+
storagePolicyName string
+
Storage Policy Based Management (SPBM) profile name.
+=======
+
name
+
name of the APIService
-
NodeAffinity v1 core
+
Query Parameters
-
Group
-
Version
-
Kind
+
Parameter
+
Description
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The scheduler will prefer to schedule pods to nodes that satisfy the affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding "weight" to the sum if the node matches the corresponding matchExpressions; the node(s) with the highest sum are the most preferred.
+||||||| merged common ancestors
+
object
+
Object is: If Type is Added or Modified: the new state of the object. If Type is Deleted: the state of the object immediately before deletion. If Type is Error: Status is recommended; other types may make sense depending on context.
If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to an update), the system may or may not try to eventually evict the pod from its node.
Human readable message indicating details about last transition.
+||||||| merged common ancestors
+
name string
+
The name of the admission webhook. Name should be fully qualified, e.g., imagepolicy.kubernetes.io, where "imagepolicy" is the name of the webhook, and kubernetes.io is the name of the organization. Required.
+=======
+
reason string
+
Unique, one-word, CamelCase reason for the condition's last transition.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
NamespaceSelector decides whether to run the webhook on an object based on whether the namespace for that object matches the selector. If the object itself is a namespace, the matching is performed on object.metadata.labels. If the object is other cluster scoped resource, it is not subjected to the webhook. For example, to run the webhook on any objects whose namespace is not associated with "runlevel" of "0" or "1"; you will set the selector as follows: "namespaceSelector": { "matchExpressions": [ { "key": "runlevel", "operator": "NotIn", "values": [ "0", "1" ] } ] } If instead you want to only run the webhook on any objects whose namespace is associated with the "environment" of "prod" or "staging"; you will set the selector as follows: "namespaceSelector": { "matchExpressions": [ { "key": "environment", "operator": "In", "values": [ "prod", "staging" ] } ] } See https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/ for more examples of label selectors. Default to the empty LabelSelector, which matches everything.
+=======
+
status string
+
Status is the status of the condition. Can be True, False, Unknown.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
service is a reference to the service for this webhook. Either service or url must be specified. If the webhook is running within the cluster, then you should use service. If there is only one port open for the service, that port will be used. If there are multiple ports open, port 443 will be used if it is open, otherwise it is an error.
+
+
+
url string
+
url gives the location of the webhook, in standard URL form ([scheme://]host:port/path). Exactly one of url or service must be specified. The host should not refer to a service running in the cluster; use the service field instead. The host might be resolved via external DNS in some apiservers (e.g., kube-apiserver cannot resolve in-cluster DNS as that would be a layering violation). host may also be an IP address. Please note that using localhost or 127.0.0.1 as a host is risky unless you take great care to run this webhook on all hosts which run an apiserver which might need to make calls to this webhook. Such installs are likely to be non-portable, i.e., not easy to turn up in a new cluster. The scheme must be "https"; the URL must begin with "https://". A path is optional, and if present may be any string permissible in a URL. You may use the path to pass an arbitrary string to the webhook, for example, a cluster identifier. Attempting to use a user or basic auth e.g. "user:password@" is not allowed. Fragments ("#...") and query parameters ("?...") are not allowed, either.
ClusterRoleSelectors holds a list of selectors which will be used to find ClusterRoles and create the rules. If any of the selectors match, then the ClusterRole's permissions will be added
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
ClusterRoleSelectors holds a list of selectors which will be used to find ClusterRoles and create the rules. If any of the selectors match, then the ClusterRole's permissions will be added
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
A node selector represents the union of the results of one or more label queries over a set of nodes; that is, it represents the OR of the selectors represented by the node selector terms.
+||||||| merged common ancestors
+
+
+
+
AggregationRule describes how to locate ClusterRoles to aggregate into the ClusterRole
+=======
+
AllowedFlexVolume represents a single Flexvolume that is allowed to be used.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
ClusterRoleSelectors holds a list of selectors which will be used to find ClusterRoles and create the rules. If any of the selectors match, then the ClusterRole's permissions will be added
+=======
+
driver string
+
Driver is the name of the Flexvolume driver.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. If the operator is Gt or Lt, the values array must have a single element, which will be interpreted as an integer. This array is replaced during a strategic merge patch.
ClusterRoleSelectors holds a list of selectors which will be used to find ClusterRoles and create the rules. If any of the selectors match, then the ClusterRole's permissions will be added
+=======
+
pathPrefix string
+
is the path prefix that the host volume must match. It does not support *. Trailing slashes are trimmed when validating the path prefix with a host path. Examples: /foo would allow /foo, /foo/ and /foo/bar/foo would not allow /food or /etc/foo
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -73527,6 +124194,84 @@ Appears In:
kernelVersion string
Kernel Version reported by the node from 'uname -r' (e.g. 3.16.0-0.bpo.4-amd64).
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
Write Operations
+
See supported operations below...
+
Create
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
Output
+
+
+Coming Soon
+
+
+
Response Body
+
+
+Coming Soon
+
+
create a ClusterRole
+
HTTP Request
+
POST /apis/rbac.authorization.k8s.io/v1beta1/clusterroles
+
Query Parameters
+
+
+=======
+
+
+
Write Operations
+
See supported operations below...
+
Create
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
+
+
create a ClusterRole
+
HTTP Request
+
POST /apis/rbac.authorization.k8s.io/v1beta1/clusterroles
+
Query Parameters
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
OwnerReference contains enough information to let you identify an owning object. Currently, an owning object must be in the same namespace, so there is no namespace field.
+||||||| merged common ancestors
+
Read Operations
+
See supported operations below...
+
Read
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
Output
+
+
+Coming Soon
+
+
+
Response Body
+
+
+Coming Soon
+
+
read the specified ClusterRole
+
HTTP Request
+
GET /apis/rbac.authorization.k8s.io/v1beta1/clusterroles/{name}
+
Path Parameters
+=======
+
Read Operations
+
See supported operations below...
+
Read
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
+
+
read the specified ClusterRole
+
HTTP Request
+
GET /apis/rbac.authorization.k8s.io/v1beta1/clusterroles/{name}
+
Path Parameters
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
Output
+
+
+Coming Soon
+
+
+
Response Body
+
+
+Coming Soon
+
+
list or watch objects of kind ClusterRole
+
HTTP Request
+
GET /apis/rbac.authorization.k8s.io/v1beta1/clusterroles
+
Query Parameters
+=======
+
List
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
+
+
list or watch objects of kind ClusterRole
+
HTTP Request
+
GET /apis/rbac.authorization.k8s.io/v1beta1/clusterroles
+
Query Parameters
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -74180,8 +125361,16 @@ Appears In:
Unique, this should be a short, machine understandable string that gives the reason for condition's last transition. If it reports "ResizeStarted" that means the underlying persistent volume is being resized.
PersistentVolumeClaimVolumeSource references the user's PVC in the same namespace. This volume finds the bound PV and mounts that volume for the pod. A PersistentVolumeClaimVolumeSource is, essentially, a wrapper around another type of volume that is owned by someone else (the system).
+||||||| merged common ancestors
+
Watch
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
Output
+
+
+Coming Soon
+
+
+
Response Body
+
+
+Coming Soon
+
+
watch changes to an object of kind ClusterRole
+
HTTP Request
+
GET /apis/rbac.authorization.k8s.io/v1beta1/watch/clusterroles/{name}
+
Path Parameters
+=======
+
Watch
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
+
+
watch changes to an object of kind ClusterRole
+
HTTP Request
+
GET /apis/rbac.authorization.k8s.io/v1beta1/watch/clusterroles/{name}
+
Path Parameters
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
A list of DNS name server IP addresses. This will be appended to the base nameservers generated from DNSPolicy. Duplicated nameservers will be removed.
A list of DNS resolver options. This will be merged with the base options generated from DNSPolicy. Duplicated entries will be removed. Resolution options given in Options will override those that appear in the base DNSPolicy.
A list of DNS search domains for host-name lookup. This will be appended to the base search paths generated from DNSPolicy. Duplicated search paths will be removed.
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
Output
+
+
+Coming Soon
+
+
+
Response Body
+
+
+Coming Soon
+
+
watch changes to an object of kind ClusterRole
+
HTTP Request
+
GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/clusterroles/{name}
+
Path Parameters
+=======
+
Watch
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
+
+
watch changes to an object of kind ClusterRole
+
HTTP Request
+
GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/clusterroles/{name}
+
Path Parameters
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -75096,8 +127013,16 @@ Appears In:
Registry represents a single or multiple Quobyte Registry services specified as a string as host:port pair (multiple entries are separated with commas) which acts as the central registry for volumes
Namespace is the namespace of the action being requested. Currently, there is no distinction between no namespace and all namespaces "" (empty) is defaulted for LocalSubjectAccessReviews "" (empty) is empty for cluster-scoped resources "" (empty) means "all" for namespace scoped resources from a SubjectAccessReview or SelfSubjectAccessReview
Optional: mode bits to use on created files by default. Must be a value between 0 and 0777. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.
A machine-readable description of why this operation is in the "Failure" status. If this value is empty there is no information available. A Reason clarifies an HTTP status code but does not override it.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
APIGroup holds the API group of the referenced subject. Defaults to "" for ServiceAccount subjects. Defaults to "rbac.authorization.k8s.io" for User and Group subjects.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
kind string
Kind of object being referenced. Values defined by this API group are "User", "Group", and "ServiceAccount". If the Authorizer does not recognized the kind value, the Authorizer should report an error.
Namespace of the referenced object. If the object kind is non-namespace, such as "User" or "Group", and this value is not empty the Authorizer should report an error.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+=======
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
Output
+
+
+Coming Soon
+
+
+
Response Body
+
+
+Coming Soon
+
+
watch individual changes to a list of ControllerRevision
+
HTTP Request
+
GET /apis/apps/v1beta2/watch/namespaces/{namespace}/controllerrevisions
+
Path Parameters
+=======
+
Watch List
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
+
+
watch individual changes to a list of ControllerRevision
+
HTTP Request
+
GET /apis/apps/v1beta2/watch/namespaces/{namespace}/controllerrevisions
+
Path Parameters
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -77931,8 +132060,16 @@ Appears In:
The name of the admission webhook. Name should be fully qualified, e.g., imagepolicy.kubernetes.io, where "imagepolicy" is the name of the webhook, and kubernetes.io is the name of the organization. Required.
NamespaceSelector decides whether to run the webhook on an object based on whether the namespace for that object matches the selector. If the object itself is a namespace, the matching is performed on object.metadata.labels. If the object is another cluster scoped resource, it never skips the webhook. For example, to run the webhook on any objects whose namespace is not associated with "runlevel" of "0" or "1"; you will set the selector as follows: "namespaceSelector": { "matchExpressions": [ { "key": "runlevel", "operator": "NotIn", "values": [ "0", "1" ] } ] } If instead you want to only run the webhook on any objects whose namespace is associated with the "environment" of "prod" or "staging"; you will set the selector as follows: "namespaceSelector": { "matchExpressions": [ { "key": "environment", "operator": "In", "values": [ "prod", "staging" ] } ] } See https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/ for more examples of label selectors. Default to the empty LabelSelector, which matches everything.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+=======
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
List
+=======
+
List
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of APIService
HTTP Request
@@ -78842,8 +133219,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
Watch
+=======
+
Watch
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
list or watch objects of kind APIService
HTTP Request
@@ -79033,8 +133454,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
Watch List
+=======
+
Watch List
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch changes to an object of kind APIService
HTTP Request
@@ -79144,8 +133583,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
Watch List All Namespaces
+=======
+
Watch List All Namespaces
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch individual changes to a list of APIService
HTTP Request
@@ -79240,8 +133697,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
Watch
+=======
+
Watch
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a ClusterRole
HTTP Request
@@ -80469,8 +135244,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
Watch List
+=======
+
Watch List
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
read the specified ClusterRole
HTTP Request
@@ -80652,8 +135445,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
Watch List All Namespaces
+=======
+
Watch List All Namespaces
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch changes to an object of kind ClusterRole
HTTP Request
@@ -80763,8 +135574,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
Delete Collection
+=======
+
Delete Collection
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch individual changes to a list of ClusterRole
HTTP Request
@@ -81824,8 +137020,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
Watch List All Namespaces
+=======
+
Watch List All Namespaces
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of ClusterRoleBinding
HTTP Request
@@ -82399,8 +137835,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
Delete Collection
+=======
+
Delete Collection
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of ClusterRoleBinding
HTTP Request
@@ -83364,8 +139191,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
+||||||| merged common ancestors
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
List All Namespaces
+=======
+
List All Namespaces
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
read the specified ClusterRoleBinding
HTTP Request
@@ -83628,6 +139579,34 @@ Appears In:
pretty
If 'true', then the output is pretty printed.
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
+=======
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch changes to an object of kind ControllerRevision
HTTP Request
@@ -83893,8 +139892,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
Watch List All Namespaces
+=======
+
Watch List All Namespaces
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch changes to an object of kind ClusterRoleBinding
HTTP Request
@@ -84004,8 +140021,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
Delete Collection
+=======
+
Delete Collection
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
watch individual changes to a list of ControllerRevision
HTTP Request
@@ -85295,8 +142099,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
Watch List
+=======
+
Watch List
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running)
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of ControllerRevision
HTTP Request
@@ -86008,8 +144130,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The 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).
Minimum number of seconds for which a newly created 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)
+
paused boolean
+
Indicates that the deployment is paused and will not be processed by the deployment controller.
+
+
+
progressDeadlineSeconds integer
+
The maximum time in seconds for a deployment to make progress before it is considered to be failed. The deployment controller will continue to process failed deployments and a condition with a ProgressDeadlineExceeded reason will be surfaced in the deployment status. Note that progress will not be estimated during the time a deployment is paused. This is not set by default.
+
+
+
replicas integer
+
Number of desired pods. This is a pointer to distinguish between explicit zero and not specified. Defaults to 1.
+
+
+
revisionHistoryLimit integer
+
The number of old ReplicaSets to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified.
HorizontalPodAutoscaler is the configuration for a horizontal pod autoscaler, which automatically manages the replica count of any resource implementing the scale subresource based on the metrics specified.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
Count of hash collisions for the DaemonSet. The DaemonSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.
+||||||| merged common ancestors
+
availableReplicas integer
+
Total number of available pods (ready for at least minReadySeconds) targeted by this deployment.
+
collisionCount integer
+
Count of hash collisions for the Deployment. The Deployment controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ReplicaSet.
+
+
+
conditions DeploymentCondition array patch type: merge patch merge key: type
+
Represents the latest available observations of a deployment's current state.
+
+
+
observedGeneration integer
+
The generation observed by the deployment controller.
+
+
+
readyReplicas integer
+
Total number of ready pods targeted by this deployment.
+
+
+
replicas integer
+
Total number of non-terminated pods targeted by this deployment (their labels match the selector).
+
+
+
unavailableReplicas integer
+
Total number of unavailable pods targeted by this deployment. This is the total number of pods that are still required for the deployment to have 100% available capacity. They may either be pods that are running but not yet available or pods that still have not been created.
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 spec.minReadySeconds)
metrics contains the specifications for which to use to calculate the desired replica count (the maximum replica count across all metrics will be used). The desired replica count is calculated multiplying the ratio between the target value and the current value by the current number of pods. Ergo, metrics used must decrease as the pod count is increased, and vice-versa. See the individual metric source types for more information about how each type of metric must respond.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
scaleTargetRef points to the target resource to scale, and is used to the pods for which metrics should be collected, as well as to actually change the replica count.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
DeploymentStrategy v1beta1 extensions
+
+
+
+
+=======
+
+
+
HorizontalPodAutoscalerStatus v2beta1 autoscaling
+
+
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
numberUnavailable integer
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 spec.minReadySeconds)
lastScaleTime is the last time the HorizontalPodAutoscaler scaled the number of pods, used by the autoscaler to control how often the number of pods is changed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
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%, at most 30% of the total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their pods stopped for an update at any given time. The update starts by stopping at most 30% of those DaemonSet pods and then brings up new DaemonSet pods in their place. Once the new pods are available, 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.
+||||||| merged common ancestors
+
maxSurge
+
The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. By default, a value of 1 is used. Example: when this is set to 30%, the new RC can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new RC can be scaled up further, ensuring that total number of pods running at any time during the update is atmost 130% of desired pods.
+
+
+
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.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Path Parameters
@@ -90155,8 +156981,16 @@ orphanDependents: false
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
lastScaleTime is the last time the HorizontalPodAutoscaler scaled the number of pods, used by the autoscaler to control how often the number of pods is changed.
+
+
+
observedGeneration integer
+
observedGeneration is the most recent generation observed by this autoscaler.
Selects Namespaces using cluster scoped-labels. This matches all pods in all namespaces selected by this label selector. This field follows standard label selector semantics. If present but empty, this selector selects all namespaces.
This is a label selector which selects Pods in this namespace. This field follows standard label selector semantics. If present but empty, this selector selects all pods in this namespace.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
If specified, the port on the given protocol. This can either be a numerical or named port on a pod. If this field is not provided, this matches all port names and numbers. If present, only traffic on the specified protocol AND port will be matched.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
+||||||| merged common ancestors
+
gracePeriodSeconds
+
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
+=======
+
verb string
+
Verb is the standard HTTP verb
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+||||||| merged common ancestors
+
orphanDependents
+
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+=======
+
Group
+
Version
+
Kind
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+||||||| merged common ancestors
+
propagationPolicy
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+=======
+
authorization
+
v1beta1
+
NonResourceRule
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
-
Body Parameters
+
+
+
+
NonResourceRule holds information that describes a rule for the non-resource
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+||||||| merged common ancestors
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+=======
+
allowedCapabilities string array
+
AllowedCapabilities is a list of capabilities that can be requested to add to the container. Capabilities in this field may be added at the pod author's discretion. You must not list a capability in both AllowedCapabilities and RequiredDropCapabilities.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
AllowedFlexVolumes is a whitelist of allowed Flexvolumes. Empty or nil indicates that all Flexvolumes may be used. This parameter is effective only when the usage of the Flexvolumes is allowed in the "Volumes" field.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+||||||| merged common ancestors
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+=======
+
defaultAddCapabilities string array
+
DefaultAddCapabilities is the default set of capabilities that will be added to the container unless the pod spec specifically drops the capability. You may not list a capability in both DefaultAddCapabilities and RequiredDropCapabilities. Capabilities added here are implicitly allowed, and need not be included in the AllowedCapabilities list.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+=======
+
defaultAllowPrivilegeEscalation boolean
+
DefaultAllowPrivilegeEscalation controls the default setting for whether a process can gain more privileges than its parent process.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
hostPorts determines which host port ranges are allowed to be exposed.
+
+
+
privileged boolean
+
privileged determines if a pod can request to be run as privileged.
+
+
+
readOnlyRootFilesystem boolean
+
ReadOnlyRootFilesystem when set to true will force containers to run with a read only root file system. If the container specifically requests to run with a non-read only root file system the PSP should deny the pod. If set to false the container may run with a read only root file system if it wishes but it will not be forced to.
+
+
+
requiredDropCapabilities string array
+
RequiredDropCapabilities are the capabilities that will be dropped from the container. These are required to be dropped and cannot be added.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -110171,6 +180645,631 @@ Appears In:
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
Parameter
+
Description
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+||||||| merged common ancestors
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+=======
+
name
+
name of the PodSecurityPolicy
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+=======
+
Parameter
+
Description
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
Parameter
+
Description
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+||||||| merged common ancestors
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+=======
+
gracePeriodSeconds
+
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+=======
+
propagationPolicy
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
object name and auth scope, such as for teams and projects
+
+
+
+
Query Parameters
+
+
+
+
Parameter
+
Description
+||||||| merged common ancestors
+
namespace
+
object name and auth scope, such as for teams and projects
+
+
+
+
Query Parameters
+
+
+
+
Parameter
+
Description
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
curl Command (requires kubectl proxy to be running)
-
-
-Coming Soon
-
-
-
Output
-
-
-Coming Soon
-
-
-
Response Body
-
-
-Coming Soon
-
-
list or watch objects of kind ReplicaSet
-
HTTP Request
-
GET /apis/apps/v1beta2/namespaces/{namespace}/replicasets
-
Path Parameters
-
-
-
-
Parameter
-
Description
-
-
-
-
-
namespace
-
object name and auth scope, such as for teams and projects
-
-
-
-
Query Parameters
-
-
-
-
Parameter
-
Description
-
-
-
-
-
pretty
-
If 'true', then the output is pretty printed.
-
-
-
continue
-
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
-
-
fieldSelector
-
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
-
-
includeUninitialized
-
If true, partially initialized resources are included in the response.
-
-
-
labelSelector
-
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
-
-
limit
-
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
-
-
resourceVersion
-
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
-
-
timeoutSeconds
-
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
-
-
watch
-
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
->>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
-
-
kubectl Command
-
-
-Coming Soon
-
-
-
curl Command (requires kubectl proxy to be running)
-
-
-Coming Soon
-
-
-
Output
-
-
-Coming Soon
-
-
-
Response Body
-
-
-Coming Soon
-
-
list or watch objects of kind ReplicaSet
-
HTTP Request
-
GET /apis/apps/v1beta2/replicasets
-
Query Parameters
-
-
-
-
Parameter
-
Description
-
-
-
-
-
continue
-
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
-
-
fieldSelector
-
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
-
-
includeUninitialized
-
If true, partially initialized resources are included in the response.
-
-
-
labelSelector
-
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
-
-
limit
-
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
-
-
pretty
-
If 'true', then the output is pretty printed.
-
-
-
resourceVersion
-
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
-
-
timeoutSeconds
-
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
-
-
watch
-
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
curl Command (requires kubectl proxy to be running)
-
-
-Coming Soon
-
-
-
Output
-
-
-Coming Soon
-
-
-
Response Body
-
-
-Coming Soon
-
-
watch changes to an object of kind ReplicaSet
-
HTTP Request
-
GET /apis/apps/v1beta2/watch/namespaces/{namespace}/replicasets/{name}
-
Path Parameters
-
-
-
-
Parameter
-
Description
-
-
-
-
-
name
-
name of the ReplicaSet
-
-
-
namespace
-
object name and auth scope, such as for teams and projects
-
-
-
-
Query Parameters
-
-
-
-
Parameter
-
Description
-
-
-
-
-
continue
-
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
-
-
fieldSelector
-
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
-
-
includeUninitialized
-
If true, partially initialized resources are included in the response.
-
-
-
labelSelector
-
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
-
-
limit
-
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
-
-
pretty
-
If 'true', then the output is pretty printed.
-
-
-
resourceVersion
-
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
-
-
timeoutSeconds
-
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
-
-
watch
-
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
->>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
-
-
kubectl Command
-
-
-Coming Soon
-
-
-
curl Command (requires kubectl proxy to be running)
-
-
-Coming Soon
-
-
-
Output
-
-
-Coming Soon
-
-
-
Response Body
-
-
-Coming Soon
-
-
watch individual changes to a list of ReplicaSet
-
HTTP Request
-
GET /apis/apps/v1beta2/watch/namespaces/{namespace}/replicasets
-
Path Parameters
-
-
-
-
Parameter
-
Description
-
-
-
-
-
namespace
-
object name and auth scope, such as for teams and projects
-
-
-
-
Query Parameters
-
-
-
-
Parameter
-
Description
-
-
-
-
-
continue
-
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
-
-
fieldSelector
-
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
-
-
includeUninitialized
-
If true, partially initialized resources are included in the response.
-
-
-
labelSelector
-
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
-
-
limit
-
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
-
-
pretty
-
If 'true', then the output is pretty printed.
-
-
-
resourceVersion
-
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
-
-
timeoutSeconds
-
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
-
-
watch
-
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -110773,16 +181377,51 @@ Appears In:
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+||||||| merged common ancestors
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+=======
+
name
+
name of the PodSecurityPolicy
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+=======
+
Parameter
+
Description
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
exact
+
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
object name and auth scope, such as for teams and projects
-
-
-
-
Query Parameters
-
-
-
-
Parameter
-
Description
-
-
-
-
+||||||| merged common ancestors
+
name
+
name of the HorizontalPodAutoscaler
+=======
pretty
If 'true', then the output is pretty printed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
-
-
-
Body Parameters
-
-
-
Parameter
-
Description
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
-
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
If 'true', then the output is pretty printed.
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
-
namespace
-
object name and auth scope, such as for teams and projects
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
-
-
Query Parameters
-
-
-
Parameter
-
Description
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
-
pretty
If 'true', then the output is pretty printed.
-
-
-
Body Parameters
-
-
-
Parameter
-
Description
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
DEPRECATED 1.9 - This group version of IPBlock is deprecated by networking/v1/IPBlock. IPBlock describes a particular CIDR (Ex. "192.168.1.1/24") that is allowed to the pods matched by a NetworkPolicySpec's podSelector. The except entry describes CIDRs that should not be included within this rule.
+
+
+=======
+
+
+
+
PolicyRule holds information that describes a policy rule, but does not contain information about who the rule applies to or which namespace the rule applies to.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
CIDR is a string representing the IP Block Valid examples are "192.168.1.1/24"
+
+
+
except string array
+
Except is a slice of CIDRs that should not be included within an IP Block Valid examples are "192.168.1.1/24" Except values will be rejected if they are outside the CIDR range
+=======
+
apiGroups string array
+
APIGroups is the name of the APIGroup that contains the resources. If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed.
+
+
+
nonResourceURLs string array
+
NonResourceURLs is a set of partial urls that a user should have access to. *s are allowed, but only as the full, final step in the path Since non-resource URLs are not namespaced, this field is only applicable for ClusterRoles referenced from a ClusterRoleBinding. Rules can either apply to API resources (such as "pods" or "secrets") or non-resource URL paths (such as "/api"), but not both.
+
+
+
resourceNames string array
+
ResourceNames is an optional white list of names that the rule applies to. An empty set means that everything is allowed.
+
+
+
resources string array
+
Resources is a list of resources this rule applies to. '' represents all resources in the specified apiGroups. '/foo' represents the subresource 'foo' for all resources in the specified apiGroups.
+
+
+
verbs string array
+
Verbs is a list of Verbs that apply to ALL the ResourceKinds and AttributeRestrictions contained in this rule. VerbAll represents all kinds.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
PUT /apis/apps/v1beta2/namespaces/{namespace}/replicasets/{name}/status
Path Parameters
+||||||| merged common ancestors
+
+
+
+
Initializer describes the name and the failure policy of an initializer, and what resources it applies to.
+
+
+=======
+
+
+
+
PolicyRule holds information that describes a policy rule, but does not contain information about who the rule applies to or which namespace the rule applies to.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Name is the identifier of the initializer. It will be added to the object that needs to be initialized. Name should be fully qualified, e.g., alwayspullimages.kubernetes.io, where "alwayspullimages" is the name of the webhook, and kubernetes.io is the name of the organization. Required
Rules describes what resources/subresources the initializer cares about. The initializer cares about an operation if it matches any Rule. Rule.Resources must not include subresources.
+
+
+
+
+
JobTemplateSpec v2alpha1 batch
+
+
+
+
Group
+
Version
+
Kind
+=======
+
apiGroups string array
+
APIGroups is the name of the APIGroup that contains the resources. If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
NonResourceURLs is a set of partial urls that a user should have access to. *s are allowed, but only as the full, final step in the path This name is intentionally different than the internal type so that the DefaultConvert works nicely and because the ordering may be different. Since non-resource URLs are not namespaced, this field is only applicable for ClusterRoles referenced from a ClusterRoleBinding. Rules can either apply to API resources (such as "pods" or "secrets") or non-resource URL paths (such as "/api"), but not both.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
GET /apis/apps/v1beta2/namespaces/{namespace}/replicasets/{name}/scale
Path Parameters
+||||||| merged common ancestors
+
+
+
+
LocalSubjectAccessReview checks whether or not a user or group can perform an action in a given namespace. Having a namespace scoped resource makes it much easier to grant namespace scoped policy that includes permissions checking.
+=======
+
+
+
+
DEPRECATED - This group version of ReplicaSet is deprecated by apps/v1/ReplicaSet. See the release notes for more information. ReplicaSet ensures that a specified number of pod replicas are running at any given time.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Spec holds information about the request being evaluated. spec.namespace must be equal to the namespace you made the request against. If empty, it is defaulted.
DEPRECATED - This group version of ReplicaSet is deprecated by apps/v1beta2/ReplicaSet. See the release notes for more information. ReplicaSet ensures that a specified number of pod replicas are running at any given time.
+||||||| merged common ancestors
+
+
+
+
DEPRECATED 1.9 - This group version of NetworkPolicy is deprecated by networking/v1/NetworkPolicy. NetworkPolicy describes what network traffic is allowed for a set of Pods
+=======
+
ReplicaSetSpec v1beta2 apps
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
Minimum number of seconds for which a newly created 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)
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Minimum number of seconds for which a newly created 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)
List of egress rules to be applied to the selected pods. Outgoing traffic is allowed if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic matches at least one egress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy limits all outgoing traffic (and serves solely to ensure that the pods it selects are isolated by default). This field is beta-level in 1.8
+=======
+
availableReplicas integer
+
The number of available replicas (ready for at least minReadySeconds) for this replica set.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
List of ingress rules to be applied to the selected pods. Traffic is allowed to a pod if there are no NetworkPolicies selecting the pod OR if the traffic source is the pod's local node, OR if the traffic matches at least one ingress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy does not allow any traffic (and serves solely to ensure that the pods it selects are isolated by default).
+=======
+
conditions ReplicaSetCondition array patch type: merge patch merge key: type
+
Represents the latest available observations of a replica set's current state.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Selects the pods to which this NetworkPolicy object applies. The array of ingress rules is applied to any pods selected by this field. Multiple network policies can select the same set of pods. In this case, the ingress rules for each are combined additively. This field is NOT optional and follows standard label selector semantics. An empty podSelector matches all pods in this namespace.
+=======
+
fullyLabeledReplicas integer
+
The number of pods that have labels matching the labels of the pod template of the replicaset.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
List of rule types that the NetworkPolicy relates to. Valid options are Ingress, Egress, or Ingress,Egress. If this field is not specified, it will default based on the existence of Ingress or Egress rules; policies that contain an Egress section are assumed to affect Egress, and all policies (whether or not they contain an Ingress section) are assumed to affect Ingress. If you want to write an egress-only policy, you must explicitly specify policyTypes [ "Egress" ]. Likewise, if you want to write a policy that specifies that no egress is allowed, you must specify a policyTypes value that include "Egress" (since such a policy would not include an Egress section and would otherwise default to just [ "Ingress" ]). This field is beta-level in 1.8
+=======
+
observedGeneration integer
+
ObservedGeneration reflects the generation of the most recently observed ReplicaSet.
+
+
+
readyReplicas integer
+
The number of ready replicas for this replica set.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Path Parameters
@@ -112294,8 +183777,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
GET /apis/extensions/v1beta1/namespaces/{namespace}/replicasets
+||||||| merged common ancestors
+
GET /apis/extensions/v1beta1/namespaces/{namespace}/networkpolicies
+=======
+
GET /apis/apps/v1beta2/namespaces/{namespace}/replicasets
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Path Parameters
@@ -112486,8 +184029,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Query Parameters
@@ -112576,8 +184149,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
GET /apis/extensions/v1beta1/watch/namespaces/{namespace}/replicasets/{name}
||||||| merged common ancestors
POST /apis/apps/v1beta2/namespaces/{namespace}/replicasets
@@ -112867,6 +184559,11 @@ Appears In:
+||||||| merged common ancestors
+
GET /apis/extensions/v1beta1/watch/networkpolicies
+=======
+
GET /apis/apps/v1beta2/watch/replicasets
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Query Parameters
@@ -112905,8 +184602,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
DEPRECATED 1.9 - This group version of NetworkPolicyEgressRule is deprecated by networking/v1/NetworkPolicyEgressRule. NetworkPolicyEgressRule describes a particular set of traffic that is allowed out of pods matched by a NetworkPolicySpec's podSelector. The traffic must match both ports and to. This type is beta-level in 1.8
List of destination ports for outgoing traffic. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.
List of destinations for outgoing traffic of pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all destinations (traffic not restricted by destination). If this field is present and contains at least one item, this rule allows traffic only if the traffic matches at least one item in the to list.
+
+
+
+
+
NetworkPolicyIngressRule v1beta1 extensions
+
+
+
+
Group
+
Version
+
Kind
+
+
+
+
+
extensions
+
v1beta1
+
NetworkPolicyIngressRule
+
+
+
+
+
+
+
DEPRECATED 1.9 - This group version of NetworkPolicyIngressRule is deprecated by networking/v1/NetworkPolicyIngressRule. This NetworkPolicyIngressRule matches traffic if and only if the traffic matches both ports AND from.
List of sources which should be able to access the pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all sources (traffic not restricted by source). If this field is present and contains at least on item, this rule allows traffic only if the traffic matches at least one item in the from list.
List of ports which should be made accessible on the pods selected for this rule. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.
+
+
+
+
+
NetworkPolicyPeer v1beta1 extensions
+
+
+
+
Group
+
Version
+
Kind
+
+
+
+
+
extensions
+
v1beta1
+
NetworkPolicyPeer
+
+
+
+
+
+
+
DEPRECATED 1.9 - This group version of NetworkPolicyPeer is deprecated by networking/v1/NetworkPolicyPeer.
Selects Namespaces using cluster scoped-labels. This matches all pods in all namespaces selected by this label selector. This field follows standard label selector semantics. If present but empty, this selector selects all namespaces.
This is a label selector which selects Pods in this namespace. This field follows standard label selector semantics. If present but empty, this selector selects all pods in this namespace.
+
+
+
+
+
NetworkPolicyPort v1beta1 extensions
+
+
+
+
Group
+
Version
+
Kind
+
+
+
+
+
extensions
+
v1beta1
+
NetworkPolicyPort
+
+
+
+
+
+
+
DEPRECATED 1.9 - This group version of NetworkPolicyPort is deprecated by networking/v1/NetworkPolicyPort.
+
+
+=======
+
OK
+
+
+
+
Status Operations
+
See supported operations below...
+
Patch Status
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
+
+
partially update status of the specified ReplicaSet
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+||||||| merged common ancestors
+
Field
+
Description
+
+
+
+
+
port
+
If specified, the port on the given protocol. This can either be a numerical or named port on a pod. If this field is not provided, this matches all port names and numbers. If present, only traffic on the specified protocol AND port will be matched.
-
propagationPolicy
-
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+
protocol string
+
Optional. The protocol (TCP or UDP) which traffic must match. If not specified, this field defaults to TCP.
+
+
NonResourceAttributes v1beta1 authorization
+
+
+
+
Group
+
Version
+
Kind
+=======
+
Parameter
+
Description
+
+
+
+
+
name
+
name of the ReplicaSet
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+||||||| merged common ancestors
+
authorization
+
v1beta1
+
NonResourceAttributes
+=======
+
namespace
+
object name and auth scope, such as for teams and projects
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+||||||| merged common ancestors
+
nonResourceURLs string array
+
NonResourceURLs is a set of partial urls that a user should have access to. s are allowed, but only as the full, final step in the path. "" means all.
+
verbs string array
+
Verb is a list of kubernetes non-resource API verbs, like: get, post, put, delete, patch, head, options. "*" means all.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
+
+
+
PolicyRule holds information that describes a policy rule, but does not contain information about who the rule applies to or which namespace the rule applies to.
+
+
+
+
+=======
+
+
+
Response
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
apiGroups string array
+
APIGroups is the name of the APIGroup that contains the resources. If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed.
+
nonResourceURLs string array
+
NonResourceURLs is a set of partial urls that a user should have access to. *s are allowed, but only as the full, final step in the path Since non-resource URLs are not namespaced, this field is only applicable for ClusterRoles referenced from a ClusterRoleBinding. Rules can either apply to API resources (such as "pods" or "secrets") or non-resource URL paths (such as "/api"), but not both.
+
+
+
resourceNames string array
+
ResourceNames is an optional white list of names that the rule applies to. An empty set means that everything is allowed.
+
+
+
resources string array
+
Resources is a list of resources this rule applies to. '' represents all resources in the specified apiGroups. '/foo' represents the subresource 'foo' for all resources in the specified apiGroups.
+
+
+
verbs string array
+
Verbs is a list of Verbs that apply to ALL the ResourceKinds and AttributeRestrictions contained in this rule. VerbAll represents all kinds.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
+
+
+
+
PolicyRule holds information that describes a policy rule, but does not contain information about who the rule applies to or which namespace the rule applies to.
+
+
+
+
+=======
+
+
+
Read Status
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
+
+
read status of the specified ReplicaSet
+
HTTP Request
+
GET /apis/apps/v1beta2/namespaces/{namespace}/replicasets/{name}/status
+
Path Parameters
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
If true, partially initialized resources are included in the response.
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+||||||| merged common ancestors
+
apiGroups string array
+
APIGroups is the name of the APIGroup that contains the resources. If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed.
+
nonResourceURLs string array
+
NonResourceURLs is a set of partial urls that a user should have access to. *s are allowed, but only as the full, final step in the path This name is intentionally different than the internal type so that the DefaultConvert works nicely and because the ordering may be different. Since non-resource URLs are not namespaced, this field is only applicable for ClusterRoles referenced from a ClusterRoleBinding. Rules can either apply to API resources (such as "pods" or "secrets") or non-resource URL paths (such as "/api"), but not both.
+=======
+
name
+
name of the ReplicaSet
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
resourceNames string array
+
ResourceNames is an optional white list of names that the rule applies to. An empty set means that everything is allowed.
+=======
+
namespace
+
object name and auth scope, such as for teams and projects
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
resources string array
+
Resources is a list of resources this rule applies to. ResourceAll represents all resources.
+=======
+
Parameter
+
Description
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
GET /apis/apps/v1beta2/namespaces/{namespace}/replicasets/{name}
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
Path Parameters
+||||||| merged common ancestors
+
+
+
+
DEPRECATED - This group version of ReplicaSet is deprecated by apps/v1/ReplicaSet. See the release notes for more information. ReplicaSet ensures that a specified number of pod replicas are running at any given time.
+
+
+=======
+
Replace Status
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
+
+
replace status of the specified ReplicaSet
+
HTTP Request
+
PUT /apis/apps/v1beta2/namespaces/{namespace}/replicasets/{name}/status
+
Path Parameters
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Minimum number of seconds for which a newly created 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)
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
@@ -113399,6 +185771,33 @@ Appears In:
export
Should this value be exported. Export strips fields that a user can not specify.
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
availableReplicas integer
+
The number of available replicas (ready for at least minReadySeconds) for this replica set.
+
+
+
conditions ReplicaSetCondition array patch type: merge patch merge key: type
+
Represents the latest available observations of a replica set's current state.
+
+
+
fullyLabeledReplicas integer
+
The number of pods that have labels matching the labels of the pod template of the replicaset.
+
+
+
observedGeneration integer
+
ObservedGeneration reflects the generation of the most recently observed ReplicaSet.
+
+
+
readyReplicas integer
+
The number of ready replicas for this replica set.
DEPRECATED - This group version of ReplicaSet is deprecated by apps/v1beta2/ReplicaSet. See the release notes for more information. ReplicaSet ensures that a specified number of pod replicas are running at any given time.
Minimum number of seconds for which a newly created 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)
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -113813,11 +186563,37 @@ Appears In:
includeUninitialized
If true, partially initialized resources are included in the response.
+||||||| merged common ancestors
+
+
gracePeriodSeconds
+
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
+
+
+
orphanDependents
+
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+
+
+
propagationPolicy
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+
+
+
+
Body Parameters
+
+
+=======
+
+
+
Body Parameters
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
@@ -113868,6 +186644,13 @@ Appears In:
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
+
Body Parameters
+
+
+
+
Parameter
+
Description
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
+
+
+
orphanDependents
+
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+
+
+
propagationPolicy
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
The last time the condition transitioned from one status to another.
+||||||| merged common ancestors
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Status of the condition, one of True, False, Unknown.
type string
Type of replica set condition.
+||||||| merged common ancestors
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
exact
+
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
+
+
+
export
+
Should this value be exported. Export strips fields that a user can not specify.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Namespace is the namespace of the action being requested. Currently, there is no distinction between no namespace and all namespaces "" (empty) is defaulted for LocalSubjectAccessReviews "" (empty) is empty for cluster-scoped resources "" (empty) means "all" for namespace scoped resources from a SubjectAccessReview or SelfSubjectAccessReview
||||||| merged common ancestors
@@ -114529,39 +187762,66 @@ Appears In:
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
Output
+
+
+Coming Soon
+
+
+
Response Body
+
+
+Coming Soon
+
+
read status of the specified ReplicaSet
+
HTTP Request
+
GET /apis/apps/v1beta2/namespaces/{namespace}/replicasets/{name}/status
+
Path Parameters
+
+
+=======
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
-
Parameter
-
Description
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
object name and auth scope, such as for teams and projects
+||||||| merged common ancestors
+
namespace
+
object name and auth scope, such as for teams and projects
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
-
-
-
Query Parameters
-
-
-
Parameter
-
Description
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+=======
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
namespace
object name and auth scope, such as for teams and projects
@@ -115179,24 +188691,49 @@ Appears In:
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
pretty
If 'true', then the output is pretty printed.
-
-
-
Body Parameters
-
-
-
Parameter
-
Description
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
>>>>>>> bb8c59a640337f352e57a094ddac20bd6bbd4715
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
object name and auth scope, such as for teams and projects
+||||||| merged common ancestors
+
namespace
+
object name and auth scope, such as for teams and projects
+=======
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
-
-
-
Query Parameters
-
-
-
Parameter
-
Description
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
-
pretty
If 'true', then the output is pretty printed.
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -115513,14 +189212,51 @@ Appears In:
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
@@ -115646,33 +189382,222 @@ Appears In:
=======
Delete
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
+
+
+
ReplicaSet v1beta1 extensions
+
+
+
+
Group
+
Version
+
Kind
+
+
+
+
+
extensions
+
v1beta1
+
ReplicaSet
+
+
+
+
+
+
+
DEPRECATED - This group version of ReplicaSet is deprecated by apps/v1beta2/ReplicaSet. See the release notes for more information. ReplicaSet ensures that a specified number of pod replicas are running at any given time.
Minimum number of seconds for which a newly created 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)
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+||||||| merged common ancestors
+
name
+
name of the ReplicaSet
+=======
+
name
+
name of the Scale
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
namespace
@@ -115941,12 +189985,20 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
object name and auth scope, such as for teams and projects
@@ -116027,6 +190133,7 @@ Appears In:
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
A selector to restrict the list of returned objects by their fields. Defaults to everything.
@@ -116039,11 +190146,37 @@ Appears In:
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+||||||| merged common ancestors
+
+
gracePeriodSeconds
+
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
+
+
+
orphanDependents
+
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+
+
+
propagationPolicy
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+
+
+
+
Body Parameters
+
+
+=======
+
+
+
Body Parameters
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -116146,33 +190370,82 @@ Appears In:
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
pretty
+
If 'true', then the output is pretty printed.
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
group string
+
Group is the API Group of the Resource. "*" means all.
+
+
+
name string
+
Name is the name of the resource being requested for a "get" or deleted for a "delete". "" (empty) means all.
+
+
+
namespace string
+
Namespace is the namespace of the action being requested. Currently, there is no distinction between no namespace and all namespaces "" (empty) is defaulted for LocalSubjectAccessReviews "" (empty) is empty for cluster-scoped resources "" (empty) means "all" for namespace scoped resources from a SubjectAccessReview or SelfSubjectAccessReview
+
+
+
resource string
+
Resource is one of the existing resource types. "*" means all.
+
+
+
subresource string
+
Subresource is one of the existing resource types. "" means none.
+
+
+
verb string
+
Verb is a kubernetes resource API verb, like: get, list, watch, create, update, delete, proxy. "*" means all.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
PUT /apis/rbac.authorization.k8s.io/v1alpha1/namespaces/{namespace}/roles/{name}
Path Parameters
+||||||| merged common ancestors
+
List All Namespaces
+
+
kubectl Command
+
+
+Coming Soon
+
+
+
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
Output
+
+
+Coming Soon
+
+
+
Response Body
+
+
+Coming Soon
+
+
list or watch objects of kind ReplicaSet
+
HTTP Request
+
GET /apis/extensions/v1beta1/replicasets
+
Query Parameters
+=======
+
+
+
+
ResourceRule is the list of actions the subject is allowed to perform on resources. The list ordering isn't significant, may contain duplicates, and possibly be incomplete.
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+=======
+
apiGroups string array
+
APIGroups is the name of the APIGroup that contains the resources. If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed. "*" means all.
+
+
+
resourceNames string array
+
ResourceNames is an optional white list of names that the rule applies to. An empty set means that everything is allowed. "*" means all.
+
+
+
resources string array
+
Resources is a list of resources this rule applies to. "" means all in the specified apiGroups. "/foo" represents the subresource 'foo' for all resources in the specified apiGroups.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+=======
+
rbac
+
v1beta1
+
Role
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+||||||| merged common ancestors
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
@@ -116648,12 +191388,31 @@ Appears In:
Parameter
Description
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
Parameter
+
Description
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
namespace
object name and auth scope, such as for teams and projects
@@ -116737,6 +191540,37 @@ Appears In:
pretty
If 'true', then the output is pretty printed.
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+=======
+
name
+
name of the Role
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
namespace
@@ -116912,8 +191844,54 @@ Appears In:
pretty
If 'true', then the output is pretty printed.
+
+
gracePeriodSeconds
+
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
+
+
+
orphanDependents
+
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+
+
+
propagationPolicy
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -117301,6 +192453,41 @@ Appears In:
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+||||||| merged common ancestors
+=======
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+||||||| merged common ancestors
+
name
+
name of the Scale
+=======
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
If true, partially initialized resources are included in the response.
+||||||| merged common ancestors
+
Parameter
+
Description
+=======
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
Parameter
+
Description
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -117486,19 +192784,64 @@ Appears In:
pretty
+||||||| merged common ancestors
+
pretty
+=======
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
Parameter
+
Description
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -117598,12 +193008,60 @@ Appears In:
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
@@ -117614,51 +193072,166 @@ Appears In:
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+||||||| merged common ancestors
+
extensions
+
v1beta1
+
ReplicaSetCondition
+=======
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The last time the condition transitioned from one status to another.
+
message string
+
A human readable message indicating details about the transition.
+
+
+
reason string
+
The reason for the condition's last transition.
+=======
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+=======
+||||||| merged common ancestors
+
+
+
+
ResourceAttributes v1beta1 authorization
+
+
+=======
+
+
+
Response
+
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+||||||| merged common ancestors
+
group string
+
Group is the API Group of the Resource. "*" means all.
+=======
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
If true, partially initialized resources are included in the response.
+||||||| merged common ancestors
+
namespace string
+
Namespace is the namespace of the action being requested. Currently, there is no distinction between no namespace and all namespaces "" (empty) is defaulted for LocalSubjectAccessReviews "" (empty) is empty for cluster-scoped resources "" (empty) means "all" for namespace scoped resources from a SubjectAccessReview or SelfSubjectAccessReview
+=======
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
subresource string
+
Subresource is one of the existing resource types. "" means none.
+=======
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
version string
+
Version is the API Version of the Resource. "*" means all.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+=======
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
RoleBinding references a role, but does not contain it. It can reference a Role in the same namespace or a ClusterRole in the global namespace. It adds who information via Subjects and namespace information by which namespace it exists in. RoleBindings in a given namespace only have effect in that namespace.
RoleRef can reference a Role in the current namespace or a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Path Parameters
@@ -118329,8 +194378,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
GET /apis/rbac.authorization.k8s.io/v1beta1/namespaces/{namespace}/rolebindings
+||||||| merged common ancestors
+
GET /apis/rbac.authorization.k8s.io/v1beta1/namespaces/{namespace}/roles
+=======
+
GET /apis/rbac.authorization.k8s.io/v1alpha1/namespaces/{namespace}/roles
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Path Parameters
@@ -118531,8 +194632,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
GET /apis/rbac.authorization.k8s.io/v1beta1/rolebindings
+||||||| merged common ancestors
+
GET /apis/rbac.authorization.k8s.io/v1beta1/roles
+=======
+
GET /apis/rbac.authorization.k8s.io/v1alpha1/roles
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Query Parameters
@@ -118627,8 +194758,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
GET /apis/rbac.authorization.k8s.io/v1beta1/watch/namespaces/{namespace}/rolebindings/{name}
+||||||| merged common ancestors
+
GET /apis/rbac.authorization.k8s.io/v1beta1/watch/namespaces/{namespace}/roles/{name}
+=======
+
GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/namespaces/{namespace}/roles/{name}
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Path Parameters
@@ -118742,8 +194903,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
GET /apis/rbac.authorization.k8s.io/v1beta1/watch/namespaces/{namespace}/rolebindings
+||||||| merged common ancestors
+
GET /apis/rbac.authorization.k8s.io/v1beta1/watch/namespaces/{namespace}/roles
+=======
+
GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/namespaces/{namespace}/roles
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Path Parameters
@@ -118853,8 +195038,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
GET /apis/rbac.authorization.k8s.io/v1beta1/watch/rolebindings
+||||||| merged common ancestors
+
GET /apis/rbac.authorization.k8s.io/v1beta1/watch/roles
+=======
+
GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/roles
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Query Parameters
@@ -118949,8 +195158,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+=======
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
RoleBinding references a role, but does not contain it. It can reference a Role in the same namespace or a ClusterRole in the global namespace. It adds who information via Subjects and namespace information by which namespace it exists in. RoleBindings in a given namespace only have effect in that namespace.
RoleRef can reference a Role in the current namespace or a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.
RoleRef can reference a Role in the current namespace or a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Path Parameters
@@ -119566,8 +195997,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
GET /apis/rbac.authorization.k8s.io/v1alpha1/namespaces/{namespace}/rolebindings
+||||||| merged common ancestors
+
GET /apis/rbac.authorization.k8s.io/v1alpha1/namespaces/{namespace}/roles
+=======
+
GET /apis/rbac.authorization.k8s.io/v1beta1/namespaces/{namespace}/rolebindings
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Path Parameters
@@ -119768,8 +196259,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
GET /apis/rbac.authorization.k8s.io/v1alpha1/rolebindings
+||||||| merged common ancestors
+
GET /apis/rbac.authorization.k8s.io/v1alpha1/roles
+=======
+
GET /apis/rbac.authorization.k8s.io/v1beta1/rolebindings
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Query Parameters
@@ -119864,8 +196385,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
namespace
@@ -119979,8 +196538,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/namespaces/{namespace}/rolebindings
+||||||| merged common ancestors
+
GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/namespaces/{namespace}/roles
+=======
+
GET /apis/rbac.authorization.k8s.io/v1beta1/watch/namespaces/{namespace}/rolebindings
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Path Parameters
@@ -120090,8 +196673,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/rolebindings
+||||||| merged common ancestors
+
GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/roles
+=======
+
GET /apis/rbac.authorization.k8s.io/v1beta1/watch/rolebindings
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Query Parameters
@@ -120186,8 +196793,16 @@ Appears In:
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
RoleRef can reference a Role in the current namespace or a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.
podManagementPolicy controls how pods are created during initial scale up, when replacing pods on nodes, or when scaling down. The default policy is OrderedReady, where pods are created in increasing order (pod-0, then pod-1, etc) and the controller will wait until each pod is ready before continuing. When scaling down, the pods are removed in the opposite order. The alternative policy is Parallel which will create pods in parallel to match the desired scale without waiting, and on scale down will delete all pods at once.
volumeClaimTemplates is a list of claims that pods are allowed to reference. The StatefulSet controller is responsible for mapping network identities to claims in a way that maintains the identity of a pod. Every claim in this list must have at least one matching (by name) volumeMount in one container in the template. A claim in this list takes precedence over any volumes in the template, with the same name.
+||||||| merged common ancestors
+
podManagementPolicy string
+
podManagementPolicy controls how pods are created during initial scale up, when replacing pods on nodes, or when scaling down. The default policy is OrderedReady, where pods are created in increasing order (pod-0, then pod-1, etc) and the controller will wait until each pod is ready before continuing. When scaling down, the pods are removed in the opposite order. The alternative policy is Parallel which will create pods in parallel to match the desired scale without waiting, and on scale down will delete all pods at once.
+
+
+
replicas integer
+
replicas is the desired number of replicas of the given Template. These are replicas in the sense that they are instantiations of the same Template, but individual replicas also have a consistent identity. If unspecified, defaults to 1.
+
+
+
revisionHistoryLimit integer
+
revisionHistoryLimit is the maximum number of revisions that will be maintained in the StatefulSet's revision history. The revision history consists of all revisions not represented by a currently applied StatefulSetSpec version. The default value is 10.
serviceName is the name of the service that governs this StatefulSet. This service must exist before the StatefulSet, and is responsible for the network identity of the set. Pods get DNS/hostnames that follow the pattern: pod-specific-string.serviceName.default.svc.cluster.local where "pod-specific-string" is managed by the StatefulSet controller.
template is the object that describes the pod that will be created if insufficient replicas are detected. Each pod stamped out by the StatefulSet will fulfill this Template, but have a unique identity from the rest of the StatefulSet.
volumeClaimTemplates is a list of claims that pods are allowed to reference. The StatefulSet controller is responsible for mapping network identities to claims in a way that maintains the identity of a pod. Every claim in this list must have at least one matching (by name) volumeMount in one container in the template. A claim in this list takes precedence over any volumes in the template, with the same name.
+=======
+
namespace
+
object name and auth scope, such as for teams and projects
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
collisionCount is the count of hash collisions for the StatefulSet. The StatefulSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.
+||||||| merged common ancestors
+
collisionCount integer
+
collisionCount is the count of hash collisions for the StatefulSet. The StatefulSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.
+=======
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
observedGeneration is the most recent generation observed for this StatefulSet. It corresponds to the StatefulSet's generation, which is updated on mutation by the API Server.
+||||||| merged common ancestors
+
observedGeneration integer
+
observedGeneration is the most recent generation observed for this StatefulSet. It corresponds to the StatefulSet's generation, which is updated on mutation by the API Server.
+=======
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
replicas is the number of Pods created by the StatefulSet controller.
+||||||| merged common ancestors
+
replicas integer
+
replicas is the number of Pods created by the StatefulSet controller.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
object name and auth scope, such as for teams and projects
+||||||| merged common ancestors
+
namespace
+
object name and auth scope, such as for teams and projects
+=======
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
-
-
-
Query Parameters
-
-
-
Parameter
-
Description
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
-
pretty
If 'true', then the output is pretty printed.
-
-
-
Body Parameters
-
-
-
Parameter
-
Description
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
@@ -124490,6 +205006,21 @@ Appears In:
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+||||||| merged common ancestors
+
+
gracePeriodSeconds
+
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
+
+
+
orphanDependents
+
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+
+
+
propagationPolicy
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+
+=======
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -124616,6 +205186,41 @@ Appears In:
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+||||||| merged common ancestors
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
+=======
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
exact
+
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
+=======
+
Parameter
+
Description
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
-
-
fieldSelector
-
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
-
-
includeUninitialized
-
If true, partially initialized resources are included in the response.
-
-
-
labelSelector
-
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
-
-
limit
-
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
-
-
pretty
+||||||| merged common ancestors
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
-
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
Body Parameters
+
+
-
timeoutSeconds
-
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
Parameter
+
Description
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+
-
watch
-
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+=======
+
Group
+
Version
+
Kind
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+=======
+
apps
+
v1beta1
+
StatefulSet
+
+
+
+
+
+
+
DEPRECATED - This group version of StatefulSet is deprecated by apps/v1beta2/StatefulSet. See the release notes for more information. StatefulSet represents a set of pods with consistent identities. Identities are defined as:
+
+
Network: A single stable DNS and hostname.
+
Storage: As many VolumeClaims as requested.
+The StatefulSet guarantees that a given network identity will always map to the same storage identity.
podManagementPolicy controls how pods are created during initial scale up, when replacing pods on nodes, or when scaling down. The default policy is OrderedReady, where pods are created in increasing order (pod-0, then pod-1, etc) and the controller will wait until each pod is ready before continuing. When scaling down, the pods are removed in the opposite order. The alternative policy is Parallel which will create pods in parallel to match the desired scale without waiting, and on scale down will delete all pods at once.
+
+
+
replicas integer
+
replicas is the desired number of replicas of the given Template. These are replicas in the sense that they are instantiations of the same Template, but individual replicas also have a consistent identity. If unspecified, defaults to 1.
+
+
+
revisionHistoryLimit integer
+
revisionHistoryLimit is the maximum number of revisions that will be maintained in the StatefulSet's revision history. The revision history consists of all revisions not represented by a currently applied StatefulSetSpec version. The default value is 10.
serviceName is the name of the service that governs this StatefulSet. This service must exist before the StatefulSet, and is responsible for the network identity of the set. Pods get DNS/hostnames that follow the pattern: pod-specific-string.serviceName.default.svc.cluster.local where "pod-specific-string" is managed by the StatefulSet controller.
template is the object that describes the pod that will be created if insufficient replicas are detected. Each pod stamped out by the StatefulSet will fulfill this Template, but have a unique identity from the rest of the StatefulSet.
volumeClaimTemplates is a list of claims that pods are allowed to reference. The StatefulSet controller is responsible for mapping network identities to claims in a way that maintains the identity of a pod. Every claim in this list must have at least one matching (by name) volumeMount in one container in the template. A claim in this list takes precedence over any volumes in the template, with the same name.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+||||||| merged common ancestors
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+=======
+
collisionCount integer
+
collisionCount is the count of hash collisions for the StatefulSet. The StatefulSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+=======
+
observedGeneration integer
+
observedGeneration is the most recent generation observed for this StatefulSet. It corresponds to the StatefulSet's generation, which is updated on mutation by the API Server.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+=======
+
replicas integer
+
replicas is the number of Pods created by the StatefulSet controller.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
curl Command (requires kubectl proxy to be running)
-
-
-Coming Soon
-
-
-
Output
-
-
-Coming Soon
-
-
-
Response Body
-
-
-Coming Soon
-
-
watch individual changes to a list of StatefulSet
-
HTTP Request
-
GET /apis/apps/v1beta2/watch/statefulsets
-
Query Parameters
-
-
-
-
Parameter
-
Description
-
-
-
-
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -125500,19 +206388,33 @@ Appears In:
pretty
+=======
+
pretty
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
If 'true', then the output is pretty printed.
+
+
+
Body Parameters
+
+
-
resourceVersion
-
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+=======
+
pretty
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
If 'true', then the output is pretty printed.
+
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
object name and auth scope, such as for teams and projects
+
+
+
+
Query Parameters
+
+
+
+
Parameter
+
Description
+
+
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
gracePeriodSeconds
+
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
+
+
+
orphanDependents
+
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+
+
+
propagationPolicy
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
@@ -125755,6 +206999,41 @@ Appears In:
=======
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+=======
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
||||||| merged common ancestors
@@ -126115,39 +207532,49 @@ Appears In:
name
name of the Scale
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
name
+
name of the Scale
+=======
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
object name and auth scope, such as for teams and projects
+||||||| merged common ancestors
+
namespace
+
object name and auth scope, such as for teams and projects
+=======
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
-
-
-
Query Parameters
-
-
-
Parameter
-
Description
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
-
pretty
If 'true', then the output is pretty printed.
-
-
-
Body Parameters
-
-
-
Parameter
-
Description
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
GET /apis/apps/v1beta1/watch/namespaces/{namespace}/statefulsets/{name}
Path Parameters
@@ -126285,7 +207741,7 @@ Appears In:
name
-
name of the Scale
+
name of the StatefulSet
namespace
@@ -126303,23 +207759,40 @@ Appears In:
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
pretty
If 'true', then the output is pretty printed.
-
-
-
Body Parameters
-
-
-
Parameter
-
Description
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
RollingUpdate is used to communicate parameters when Type is RollingUpdateStatefulSetStrategyType.
+||||||| merged common ancestors
+
podManagementPolicy string
+
podManagementPolicy controls how pods are created during initial scale up, when replacing pods on nodes, or when scaling down. The default policy is OrderedReady, where pods are created in increasing order (pod-0, then pod-1, etc) and the controller will wait until each pod is ready before continuing. When scaling down, the pods are removed in the opposite order. The alternative policy is Parallel which will create pods in parallel to match the desired scale without waiting, and on scale down will delete all pods at once.
+=======
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Type indicates the type of the StatefulSetUpdateStrategy. Default is RollingUpdate.
+||||||| merged common ancestors
+
replicas integer
+
replicas is the desired number of replicas of the given Template. These are replicas in the sense that they are instantiations of the same Template, but individual replicas also have a consistent identity. If unspecified, defaults to 1.
+=======
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
revisionHistoryLimit is the maximum number of revisions that will be maintained in the StatefulSet's revision history. The revision history consists of all revisions not represented by a currently applied StatefulSetSpec version. The default value is 10.
+=======
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
serviceName is the name of the service that governs this StatefulSet. This service must exist before the StatefulSet, and is responsible for the network identity of the set. Pods get DNS/hostnames that follow the pattern: pod-specific-string.serviceName.default.svc.cluster.local where "pod-specific-string" is managed by the StatefulSet controller.
+=======
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
template is the object that describes the pod that will be created if insufficient replicas are detected. Each pod stamped out by the StatefulSet will fulfill this Template, but have a unique identity from the rest of the StatefulSet.
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
updateStrategy indicates the StatefulSetUpdateStrategy that will be employed to update Pods in the StatefulSet when a revision is made to Template.
+=======
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
volumeClaimTemplates is a list of claims that pods are allowed to reference. The StatefulSet controller is responsible for mapping network identities to claims in a way that maintains the identity of a pod. Every claim in this list must have at least one matching (by name) volumeMount in one container in the template. A claim in this list takes precedence over any volumes in the template, with the same name.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
collisionCount is the count of hash collisions for the StatefulSet. The StatefulSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.
currentRevision, if not empty, indicates the version of the StatefulSet used to generate Pods in the sequence [0,currentReplicas).
+=======
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Dynamically provisioned PersistentVolumes of this storage class are created with these mountOptions, e.g. ["ro", "soft"]. Not validated - mount of the PVs will simply fail if one is invalid.
+||||||| merged common ancestors
+
observedGeneration integer
+
observedGeneration is the most recent generation observed for this StatefulSet. It corresponds to the StatefulSet's generation, which is updated on mutation by the API Server.
+=======
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Dynamically provisioned PersistentVolumes of this storage class are created with this reclaimPolicy. Defaults to Delete.
+||||||| merged common ancestors
+
updateRevision string
+
updateRevision, if not empty, indicates the version of the StatefulSet used to generate Pods in the sequence [replicas-updatedReplicas,replicas)
+=======
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
VolumeBindingMode indicates how PersistentVolumeClaims should be provisioned and bound. When unset, VolumeBindingImmediate is used. This field is alpha-level and is only honored by servers that enable the VolumeScheduling feature.
+||||||| merged common ancestors
+
updatedReplicas integer
+
updatedReplicas is the number of Pods created by the StatefulSet controller from the StatefulSet version indicated by updateRevision.
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+=======
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
-
Field
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
+
+
replace status of the specified StatefulSet
+
HTTP Request
+
PUT /apis/apps/v1beta1/namespaces/{namespace}/statefulsets/{name}/status
+
Path Parameters
+
+
-
pretty
-
If 'true', then the output is pretty printed.
-
-
-
continue
-
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
-
-
fieldSelector
-
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
Parameter
+
Description
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
@@ -127161,6 +209256,36 @@ Appears In:
export
Should this value be exported. Export strips fields that a user can not specify.
+||||||| merged common ancestors
+
+
gracePeriodSeconds
+
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
+
+
+
orphanDependents
+
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+
+
+
propagationPolicy
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
PUT /apis/apps/v1beta1/namespaces/{namespace}/statefulsets/{name}/scale
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Path Parameters
@@ -127228,6 +209381,10 @@ Appears In:
+
name
+
name of the Scale
+
+
namespace
object name and auth scope, such as for teams and projects
@@ -127246,37 +209403,20 @@ Appears In:
pretty
If 'true', then the output is pretty printed.
+
+
+
Body Parameters
+
+
-
continue
-
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
Parameter
+
Description
+
+
-
fieldSelector
-
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
-
-
includeUninitialized
-
If true, partially initialized resources are included in the response.
-
-
-
labelSelector
-
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
-
-
limit
-
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
-
-
resourceVersion
-
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
-
-
timeoutSeconds
-
Timeout for the list/watch call.
-
-
-
watch
-
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+||||||| merged common ancestors
+
name
+
name of the StatefulSet
+=======
+
name
+
name of the Scale
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
exact
+
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
+=======
+
Parameter
+
Description
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
GET /apis/apps/v1beta1/namespaces/{namespace}/statefulsets
Path Parameters
-
-
-
-
Parameter
-
Description
-
-
-
-
-
namespace
-
object name and auth scope, such as for teams and projects
-
-
-
-
Query Parameters
-
-
-
-
Parameter
-
Description
-
-
-
-
-
pretty
-
If 'true', then the output is pretty printed.
-
-
-
continue
-
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
-
-
fieldSelector
-
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
-
-
includeUninitialized
-
If true, partially initialized resources are included in the response.
-
-
-
labelSelector
-
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
-
-
limit
-
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
-
-
resourceVersion
-
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
-
-
timeoutSeconds
-
Timeout for the list/watch call.
-
-
-
watch
-
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
GET /apis/apps/v1beta1/namespaces/{namespace}/statefulsets
+
Path Parameters
+=======
+
+
StatefulSetCondition v1beta2 apps
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
-
Parameter
+
Group
+
Version
+
Kind
+
+
+
+
+
apps
+
v1beta2
+
StatefulSetCondition
+
+
+
+
+
+
+
StatefulSetCondition describes the state of a statefulset at a certain point.
+
+
+
+
+
+
Field
Description
-
continue
-
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
Last time the condition transitioned from one status to another.
-
fieldSelector
-
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
message string
+
A human readable message indicating details about the transition.
-
includeUninitialized
-
If true, partially initialized resources are included in the response.
+
reason string
+
The reason for the condition's last transition.
-
labelSelector
-
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
status string
+
Status of the condition, one of True, False, Unknown.
-
limit
-
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
-
-
pretty
-
If 'true', then the output is pretty printed.
-
-
-
resourceVersion
-
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
-
-
timeoutSeconds
-
Timeout for the list/watch call.
-
-
-
watch
-
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+
type string
+
Type of statefulset condition.
-
Response
+
+
StatefulSetCondition v1beta1 apps
-
Code
+
Group
+
Version
+
Kind
+
+
+
+
+
apps
+
v1beta1
+
StatefulSetCondition
+
+
+
+
+
+
+
StatefulSetCondition describes the state of a statefulset at a certain point.
Last time the condition transitioned from one status to another.
+
+
+
message string
+
A human readable message indicating details about the transition.
+
+
+
reason string
+
The reason for the condition's last transition.
+
+
+
status string
+
Status of the condition, one of True, False, Unknown.
+
+
+
type string
+
Type of statefulset condition.
+
+
StatefulSetUpdateStrategy v1beta2 apps
+
+
+
+
Group
+
Version
+
Kind
+
+
+
+
+
apps
+
v1beta2
+
StatefulSetUpdateStrategy
+
+
+
+
+
+
+
StatefulSetUpdateStrategy indicates the strategy that the StatefulSet controller will use to perform updates. It includes any additional parameters necessary to perform the update for the indicated strategy.
GET /apis/apps/v1beta1/watch/namespaces/{namespace}/statefulsets/{name}
Path Parameters
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
-
-
-
-
Parameter
-
Description
-
-
-
-
-
pretty
-
If 'true', then the output is pretty printed.
-
-
-
continue
-
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
-
-
fieldSelector
-
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
-
-
includeUninitialized
-
If true, partially initialized resources are included in the response.
-
-
-
labelSelector
-
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
-
-
limit
-
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
-
-
resourceVersion
-
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
-
-
timeoutSeconds
-
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
-
-
watch
-
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
->>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+
Watch
kubectl Command
@@ -127707,9 +209905,9 @@ Appears In:
Coming Soon
-
watch changes to an object of kind StorageClass
+
watch changes to an object of kind StatefulSet
HTTP Request
-
GET /apis/storage.k8s.io/v1beta1/watch/storageclasses/{name}
+
GET /apis/apps/v1beta1/watch/namespaces/{namespace}/statefulsets/{name}
Path Parameters
@@ -127720,12 +209918,291 @@ Appears In:
-
name
-
name of the StorageClass
+
name
+
name of the StatefulSet
+
+
+
namespace
+
object name and auth scope, such as for teams and projects
Query Parameters
+=======
+
+
+
+
StatefulSetUpdateStrategy indicates the strategy that the StatefulSet controller will use to perform updates. It includes any additional parameters necessary to perform the update for the indicated strategy.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+||||||| merged common ancestors
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+=======
+
allowVolumeExpansion boolean
+
AllowVolumeExpansion shows whether the storage class allow volume expand
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+=======
+
mountOptions string array
+
Dynamically provisioned PersistentVolumes of this storage class are created with these mountOptions, e.g. ["ro", "soft"]. Not validated - mount of the PVs will simply fail if one is invalid.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+=======
+
parameters object
+
Parameters holds the parameters for the provisioner that should create volumes of this storage class.
+
+
+
provisioner string
+
Provisioner indicates the type of the provisioner.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+||||||| merged common ancestors
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+=======
+
volumeBindingMode string
+
VolumeBindingMode indicates how PersistentVolumeClaims should be provisioned and bound. When unset, VolumeBindingImmediate is used. This field is alpha-level and is only honored by servers that enable the VolumeScheduling feature.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -127769,67 +210270,7 @@ Appears In:
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
curl Command (requires kubectl proxy to be running)
-
-
-Coming Soon
-
-
-
Output
-
-
-Coming Soon
-
-
-
Response Body
-
-
-Coming Soon
-
-
watch individual changes to a list of StatefulSet
-
HTTP Request
-
GET /apis/apps/v1beta1/watch/statefulsets
-
Query Parameters
-
-
-
-
Parameter
-
Description
-
-
-
-
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -127864,6 +210305,10 @@ Appears In:
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
||||||| merged common ancestors
@@ -128024,39 +210607,52 @@ Appears In:
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
@@ -128097,6 +210694,15 @@ Appears In:
namespace
object name and auth scope, such as for teams and projects
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+||||||| merged common ancestors
+
name of the StatefulSet
+
+
+
namespace
+
object name and auth scope, such as for teams and projects
+=======
+
name of the StorageClass
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -128121,6 +210727,33 @@ Appears In:
If 'true', then the output is pretty printed.
>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+
+
gracePeriodSeconds
+
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
+
+
+
orphanDependents
+
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+
+
+
propagationPolicy
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
APIGroup holds the API group of the referenced subject. Defaults to "" for ServiceAccount subjects. Defaults to "rbac.authorization.k8s.io" for User and Group subjects.
+||||||| merged common ancestors
+
name
+
name of the StatefulSet
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Kind of object being referenced. Values defined by this API group are "User", "Group", and "ServiceAccount". If the Authorizer does not recognized the kind value, the Authorizer should report an error.
@@ -128255,25 +210915,56 @@ Appears In:
namespace string
Namespace of the referenced object. If the object kind is non-namespace, such as "User" or "Group", and this value is not empty the Authorizer should report an error.
+||||||| merged common ancestors
+
namespace
+
object name and auth scope, such as for teams and projects
+=======
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
APIVersion holds the API group and version of the referenced subject. Defaults to "v1" for ServiceAccount subjects. Defaults to "rbac.authorization.k8s.io/v1alpha1" for User and Group subjects.
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
POST /apis/authorization.k8s.io/v1beta1/subjectaccessreviews
||||||| merged common ancestors
PUT /apis/apps/v1beta1/namespaces/{namespace}/statefulsets/{name}/status
@@ -128604,6 +211384,13 @@ Appears In:
=======
PUT /apis/apps/v1beta1/namespaces/{namespace}/statefulsets/{name}/scale
Path Parameters
+||||||| merged common ancestors
+
PUT /apis/apps/v1beta1/namespaces/{namespace}/statefulsets/{name}/scale
+
Path Parameters
+=======
+
GET /apis/storage.k8s.io/v1beta1/storageclasses
+
Query Parameters
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
@@ -128613,42 +211400,51 @@ Appears In:
-
name
-
name of the Scale
+
pretty
+
If 'true', then the output is pretty printed.
-
namespace
-
object name and auth scope, such as for teams and projects
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
GET /apis/storage.k8s.io/v1beta1/watch/storageclasses/{name}
Path Parameters
@@ -128733,11 +211566,7 @@ Appears In:
name
-
name of the Scale
-
-
-
namespace
-
object name and auth scope, such as for teams and projects
+
name of the StorageClass
@@ -128751,23 +211580,40 @@ Appears In:
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
pretty
If 'true', then the output is pretty printed.
-
-
-
Body Parameters
-
-
-
Parameter
-
Description
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
SubjectRulesReviewStatus contains the result of a rules check. This check can be incomplete depending on the set of authorizers the server is configured with and any errors experienced during evaluation. Because authorization rules are additive, if a rule appears in a list it's safe to assume the subject has that permission, even if that list is incomplete.
SubjectRulesReviewStatus contains the result of a rules check. This check can be incomplete depending on the set of authorizers the server is configured with and any errors experienced during evaluation. Because authorization rules are additive, if a rule appears in a list it's safe to assume the subject has that permission, even if that list is incomplete.
EvaluationError can appear in combination with Rules. It indicates an error occurred during rule evaluation, such as an authorizer that doesn't support rule evaluation, and that ResourceRules and/or NonResourceRules may be incomplete.
Last time the condition transitioned from one status to another.
+=======
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
Incomplete is true when the rules returned by this call are incomplete. This is most commonly encountered when an authorizer, such as an external authorizer, doesn't support rules evaluation.
+||||||| merged common ancestors
+
message string
+
A human readable message indicating details about the transition.
+=======
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
NonResourceRules is the list of actions the subject is allowed to perform on non-resources. The list ordering isn't significant, may contain duplicates, and possibly be incomplete.
+||||||| merged common ancestors
+
reason string
+
The reason for the condition's last transition.
+=======
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
ResourceRules is the list of actions the subject is allowed to perform on resources. The list ordering isn't significant, may contain duplicates, and possibly be incomplete.
+||||||| merged common ancestors
+
status string
+
Status of the condition, one of True, False, Unknown.
+=======
+
Code
+
Description
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+=======
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
TokenReview attempts to authenticate a token to a known user. Note: TokenReview requests may be cached by the webhook token authenticator plugin in the kube-apiserver.
@@ -128938,12 +211948,28 @@ Appears In:
TokenReviewSpec v1beta1 authentication
+||||||| merged common ancestors
+
StatefulSetCondition describes the state of a statefulset at a certain point.
+=======
+
Subject contains a reference to the object or user identities a role binding applies to. This can either hold a direct API object reference, or a value for non-objects such as user and group names.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
Last time the condition transitioned from one status to another.
+
+
+
message string
+
A human readable message indicating details about the transition.
+=======
+
apiGroup string
+
APIGroup holds the API group of the referenced subject. Defaults to "" for ServiceAccount subjects. Defaults to "rbac.authorization.k8s.io" for User and Group subjects.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Authenticated indicates that the token was associated with a known user.
+||||||| merged common ancestors
+
reason string
+
The reason for the condition's last transition.
+=======
+
kind string
+
Kind of object being referenced. Values defined by this API group are "User", "Group", and "ServiceAccount". If the Authorizer does not recognized the kind value, the Authorizer should report an error.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Namespace of the referenced object. If the object kind is non-namespace, such as "User" or "Group", and this value is not empty the Authorizer should report an error.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
+||||||| merged common ancestors
+
+=======
+
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+<<<<<<< HEAD:docs/reference/generated/kubernetes-api/v1.10/index.html
UserInfo holds the information about the user needed to implement the user.Info interface.
+||||||| merged common ancestors
+
StatefulSetUpdateStrategy indicates the strategy that the StatefulSet controller will use to perform updates. It includes any additional parameters necessary to perform the update for the indicated strategy.
+=======
+
Subject contains a reference to the object or user identities a role binding applies to. This can either hold a direct API object reference, or a value for non-objects such as user and group names.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
RollingUpdate is used to communicate parameters when Type is RollingUpdateStatefulSetStrategyType.
+=======
+
apiVersion string
+
APIVersion holds the API group and version of the referenced subject. Defaults to "v1" for ServiceAccount subjects. Defaults to "rbac.authorization.k8s.io/v1alpha1" for User and Group subjects.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The name that uniquely identifies this user among all active users.
+||||||| merged common ancestors
+
type string
+
Type indicates the type of the StatefulSetUpdateStrategy. Default is RollingUpdate.
+=======
+
kind string
+
Kind of object being referenced. Values defined by this API group are "User", "Group", and "ServiceAccount". If the Authorizer does not recognized the kind value, the Authorizer should report an error.
+
+
+
name string
+
Name of the object being referenced.
+
+
+
namespace string
+
Namespace of the referenced object. If the object kind is non-namespace, such as "User" or "Group", and this value is not empty the Authorizer should report an error.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Dynamically provisioned PersistentVolumes of this storage class are created with these mountOptions, e.g. ["ro", "soft"]. Not validated - mount of the PVs will simply fail if one is invalid.
+=======
+
group string array
+
Groups is the groups you're testing for.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The last error encountered during attach operation, if any. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.
+||||||| merged common ancestors
+
parameters object
+
Parameters holds the parameters for the provisioner that should create volumes of this storage class.
Upon successful attach, this field is populated with any information returned by the attach operation that must be passed into subsequent WaitForAttach or Mount calls. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.
+||||||| merged common ancestors
+
reclaimPolicy string
+
Dynamically provisioned PersistentVolumes of this storage class are created with this reclaimPolicy. Defaults to Delete.
+=======
+
uid string
+
UID information about the requesting user.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The last error encountered during detach operation, if any. This field must only be set by the entity completing the detach operation, i.e. the external-attacher.
+||||||| merged common ancestors
+
volumeBindingMode string
+
VolumeBindingMode indicates how PersistentVolumeClaims should be provisioned and bound. When unset, VolumeBindingImmediate is used. This field is alpha-level and is only honored by servers that enable the VolumeScheduling feature.
+=======
+
user string
+
User is the user you're testing for. If you specify "User" but not "Group", then is it interpreted as "What if User were not a member of any groups
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Denied is optional. True if the action would be denied, otherwise false. If both allowed is false and denied is false, then the authorizer has no opinion on whether to authorize the action. Denied may not be true if Allowed is true.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
EvaluationError is an indication that some error occurred during the authorization check. It is entirely possible to get an error and be able to continue determine authorization status in spite of it. For instance, RBAC can be missing a role, but enough roles are still present and bound to reason about the request.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
SubjectRulesReviewStatus contains the result of a rules check. This check can be incomplete depending on the set of authorizers the server is configured with and any errors experienced during evaluation. Because authorization rules are additive, if a rule appears in a list it's safe to assume the subject has that permission, even if that list is incomplete.
EvaluationError can appear in combination with Rules. It indicates an error occurred during rule evaluation, such as an authorizer that doesn't support rule evaluation, and that ResourceRules and/or NonResourceRules may be incomplete.
+
+
+
incomplete boolean
+
Incomplete is true when the rules returned by this call are incomplete. This is most commonly encountered when an authorizer, such as an external authorizer, doesn't support rules evaluation.
NonResourceRules is the list of actions the subject is allowed to perform on non-resources. The list ordering isn't significant, may contain duplicates, and possibly be incomplete.
ResourceRules is the list of actions the subject is allowed to perform on resources. The list ordering isn't significant, may contain duplicates, and possibly be incomplete.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+
+
+
+
SupplementalGroupsStrategyOptions v1beta1 policy
+
+
+
+
Group
+
Version
+
Kind
+
+
+
+
+
policy
+
v1beta1
+
SupplementalGroupsStrategyOptions
+
+
+
+
SupplementalGroupsStrategyOptions defines the strategy type and options used to create the strategy.
Ranges are the allowed ranges of supplemental groups. If you would like to force a single supplemental group then supply a single range with the same start and end.
+
+
+
rule string
+
Rule is the strategy that will dictate what supplemental groups is used in the SecurityContext.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
+
+
+
+
TokenReview v1beta1 authentication
+
+
+
+
Group
+
Version
+
Kind
+
+
+
+
+
authentication
+
v1beta1
+
TokenReview
+
+
+
+
+
+
+
TokenReview attempts to authenticate a token to a known user. Note: TokenReview requests may be cached by the webhook token authenticator plugin in the kube-apiserver.
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
+||||||| merged common ancestors
+
gracePeriodSeconds
+
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
+=======
+
groups string array
+
The names of groups this user is a part of.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+||||||| merged common ancestors
+
orphanDependents
+
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+=======
+
uid string
+
A unique value that identifies this user across time. If this user is deleted and another user by the same name is added, they will have different UIDs.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+||||||| merged common ancestors
+
propagationPolicy
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
+=======
+
username string
+
The name that uniquely identifies this user among all active users.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
-
-
fieldSelector
-
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
-
-
includeUninitialized
-
If true, partially initialized resources are included in the response.
-
-
-
labelSelector
-
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
-
-
limit
-
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
-
-
resourceVersion
-
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
-
-
timeoutSeconds
-
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
-
-
watch
-
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+||||||| merged common ancestors
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+=======
+
attacher string
+
Attacher indicates the name of the volume driver that MUST handle this request. This is the name returned by GetPluginName().
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
The last error encountered during attach operation, if any. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+=======
+
attached boolean
+
Indicates the volume is successfully attached. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
attachmentMetadata object
+
Upon successful attach, this field is populated with any information returned by the attach operation that must be passed into subsequent WaitForAttach or Mount calls. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
The last error encountered during detach operation, if any. This field must only be set by the entity completing the detach operation, i.e. the external-attacher.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+||||||| merged common ancestors
+
pretty
+
If 'true', then the output is pretty printed.
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+=======
+
name
+
name of the VolumeAttachment
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+||||||| merged common ancestors
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+=======
+
Parameter
+
Description
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+=======
+
pretty
+
If 'true', then the output is pretty printed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -130056,19 +214163,71 @@ Appears In:
pretty
-
If 'true', then the output is pretty printed.
+||||||| merged common ancestors
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+=======
+
pretty
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+||||||| merged common ancestors
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
timeoutSeconds
+
Timeout for the list/watch call.
+=======
+
Parameter
+
Description
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Subject contains a reference to the object or user identities a role binding applies to. This can either hold a direct API object reference, or a value for non-objects such as user and group names.
APIVersion holds the API group and version of the referenced subject. Defaults to "v1" for ServiceAccount subjects. Defaults to "rbac.authorization.k8s.io/v1alpha1" for User and Group subjects.
+
apiGroup string
+
APIGroup holds the API group of the referenced subject. Defaults to "" for ServiceAccount subjects. Defaults to "rbac.authorization.k8s.io" for User and Group subjects.
kind string
@@ -130627,7 +214883,7 @@ Appears In:
-
SubjectAccessReview v1beta1 authorization
+
Subject v1alpha1 rbac
@@ -130638,155 +214894,16 @@ Appears In:
-
authorization
-
v1beta1
-
SubjectAccessReview
+
rbac
+
v1alpha1
+
Subject
+=======
+
name
+
name of the VolumeAttachment
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
-
-
-
-
SubjectAccessReview checks whether or not a user or group can perform an action.
ResourceAuthorizationAttributes describes information for a resource access request
-
-
-
uid string
-
UID information about the requesting user.
-
-
-
user string
-
User is the user you're testing for. If you specify "User" but not "Group", then is it interpreted as "What if User were not a member of any groups
-
-
-
-
SubjectAccessReviewStatus v1beta1 authorization
-
-
-
-
-
-
Field
-
Description
-
-
-
-
-
allowed boolean
-
Allowed is required. True if the action would be allowed, false otherwise.
-
-
-
denied boolean
-
Denied is optional. True if the action would be denied, otherwise false. If both allowed is false and denied is false, then the authorizer has no opinion on whether to authorize the action. Denied may not be true if Allowed is true.
-
-
-
evaluationError string
-
EvaluationError is an indication that some error occurred during the authorization check. It is entirely possible to get an error and be able to continue determine authorization status in spite of it. For instance, RBAC can be missing a role, but enough roles are still present and bound to reason about the request.
-
-
-
reason string
-
Reason is optional. It indicates why a request was allowed or denied.
-
-
-
-
Write Operations
-
See supported operations below...
-
Create
-
-
kubectl Command
-
-
-Coming Soon
-
-
-
curl Command (requires kubectl proxy to be running)
-
-
-Coming Soon
-
-
-
Output
-
-
-Coming Soon
-
-
-
Response Body
-
-
-Coming Soon
-
-
create a SubjectAccessReview
-
HTTP Request
-
POST /apis/authorization.k8s.io/v1beta1/subjectaccessreviews
Query Parameters
@@ -130800,6 +214917,18 @@ Appears In:
pretty
If 'true', then the output is pretty printed.
+
+
gracePeriodSeconds
+
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
+
+
+
orphanDependents
+
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
+
+
+
propagationPolicy
+
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
VolumeAttachmentSource represents a volume that should be attached. Right now only PersistenVolumes can be attached via external attacher, in future we may allow also inline volumes in pods. Exactly one member can be set.
-
-
-
-
-
-
Field
+
Parameter
Description
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
VolumeAttachmentSource represents a volume that should be attached. Right now only PersistenVolumes can be attached via external attacher, in future we may allow also inline volumes in pods. Exactly one member can be set.
EvaluationError can appear in combination with Rules. It indicates an error occurred during rule evaluation, such as an authorizer that doesn't support rule evaluation, and that ResourceRules and/or NonResourceRules may be incomplete.
-
-
-
incomplete boolean
-
Incomplete is true when the rules returned by this call are incomplete. This is most commonly encountered when an authorizer, such as an external authorizer, doesn't support rules evaluation.
NonResourceRules is the list of actions the subject is allowed to perform on non-resources. The list ordering isn't significant, may contain duplicates, and possibly be incomplete.
ResourceRules is the list of actions the subject is allowed to perform on resources. The list ordering isn't significant, may contain duplicates, and possibly be incomplete.
-
-
-
-
-
TokenReview v1beta1 authentication
-
-
-
-
Group
-
Version
-
Kind
-
-
-
-
-
authentication
-
v1beta1
-
TokenReview
-
-
-
-
-
-
-
TokenReview attempts to authenticate a token to a known user. Note: TokenReview requests may be cached by the webhook token authenticator plugin in the kube-apiserver.
User is the UserInfo associated with the provided token.
-
-
-
-
Write Operations
-
See supported operations below...
-
Create
-
-
kubectl Command
-
-
-Coming Soon
-
-
-
curl Command (requires kubectl proxy to be running)
-
-
-Coming Soon
-
-
-
Output
-
-
-Coming Soon
-
-
-
Response Body
-
-
-Coming Soon
-
-
create a TokenReview
-
HTTP Request
-
POST /apis/authentication.k8s.io/v1beta1/tokenreviews
-
Query Parameters
-
-
-
-
Parameter
-
Description
-
-
-
-
+||||||| merged common ancestors
+
evaluationError string
+
EvaluationError can appear in combination with Rules. It indicates an error occurred during rule evaluation, such as an authorizer that doesn't support rule evaluation, and that ResourceRules and/or NonResourceRules may be incomplete.
+=======
pretty
If 'true', then the output is pretty printed.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
-
-
-
Body Parameters
-
-
-
Parameter
-
Description
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
curl Command (requires kubectl proxy to be running)
+
+
+Coming Soon
+
+
+
+
Output
+
+
+Coming Soon
+
+
+
+
Response Body
+
+
+Coming Soon
+
+
+
watch individual changes to a list of VolumeAttachment
+
HTTP Request
+
GET /apis/storage.k8s.io/v1alpha1/watch/volumeattachments
+
Query Parameters
+
+
+
+
Parameter
+
Description
+
+
+
+
+
continue
+
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
+
+
+
fieldSelector
+
A selector to restrict the list of returned objects by their fields. Defaults to everything.
+
+
+
includeUninitialized
+
If true, partially initialized resources are included in the response.
+
+
+
labelSelector
+
A selector to restrict the list of returned objects by their labels. Defaults to everything.
+
+
+
limit
+
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
+
+
+
pretty
+
If 'true', then the output is pretty printed.
+
+
+
resourceVersion
+
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
+
+
+
timeoutSeconds
+
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
+
+
+
watch
+
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
->>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
-
VolumeError v1alpha1 storage.k8s.io
+
VolumeAttachmentSource v1alpha1 storage
@@ -131304,21 +215712,21 @@ Appears In:
-
storage.k8s.io
-
v1alpha1
-
VolumeError
+
storage
+
v1alpha1
+
VolumeAttachmentSource
-
+
-
VolumeError captures an error encountered during a volume operation.
+
VolumeAttachmentSource represents a volume that should be attached. Right now only PersistenVolumes can be attached via external attacher, in future we may allow also inline volumes in pods. Exactly one member can be set.
@@ -131330,12 +215738,108 @@ Appears In:
+
persistentVolumeName string
+
Name of the persistent volume to attach.
+
+>>>>>>> merge master to 1.10, with fixes (#7682):docs/reference/generated/kubernetes-api/v1.9/index.html
+
+
String detailing the error encountered during Attach or Detach operation. This string maybe logged, so it should not contain sensitive information.
+||||||| merged common ancestors
+
extra object
+
Any additional information provided by the authenticator.
+
groups string array
+
The names of groups this user is a part of.
+
+
+
uid string
+
A unique value that identifies this user across time. If this user is deleted and another user by the same name is added, they will have different UIDs.
+=======
+
message string
+
String detailing the error encountered during Attach or Detach operation. This string maybe logged, so it should not contain sensitive information.
+>>>>>>> update generated api-reference docs for 1.10 (#7856):docs/reference/generated/kubernetes-api/v1.10/index.html
+