See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-See supported operations below...
-APIService represents a server for a particular GroupVersion. Name must be "version.group".
Appears In:
@@ -43488,32 +44069,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create an APIService
HTTP Request
@@ -43571,30 +44156,34 @@ Appears In:
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified APIService
HTTP Request
@@ -43659,30 +44248,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified APIService
HTTP Request
@@ -43742,39 +44335,43 @@ Appears In:
-200 APIService
-OK
-
-
201 APIService
Created
+
+200 APIService
+OK
+
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete an APIService
HTTP Request
@@ -43851,30 +44448,34 @@ Appears In:
-Delete Collection
+Delete Collection
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
@@ -43918,7 +44519,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
@@ -43941,32 +44542,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 APIService
HTTP Request
@@ -44024,30 +44629,34 @@ Appears In:
-List
+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 APIService
HTTP Request
@@ -44091,7 +44700,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
@@ -44114,30 +44723,34 @@ Appears In:
-Watch
+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 APIService
HTTP Request
@@ -44196,7 +44809,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
@@ -44219,30 +44832,34 @@ Appears In:
-Watch List
+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 APIService
HTTP Request
@@ -44286,7 +44903,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
@@ -44309,32 +44926,36 @@ Appears In:
-Status Operations
+Status Operations
See supported operations below...
-Replace Status
+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 APIService
HTTP Request
@@ -44448,32 +45069,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a Binding
HTTP Request
@@ -44533,10 +45158,6 @@ Appears In:
-200 Binding
-OK
-
-
201 Binding
Created
@@ -44544,6 +45165,10 @@ Appears In:
202 Binding
Accepted
+
+200 Binding
+OK
+
@@ -44697,32 +45322,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a CertificateSigningRequest
HTTP Request
@@ -44780,30 +45409,34 @@ Appears In:
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified CertificateSigningRequest
HTTP Request
@@ -44868,30 +45501,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified CertificateSigningRequest
HTTP Request
@@ -44960,30 +45597,34 @@ Appears In:
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a CertificateSigningRequest
HTTP Request
@@ -45060,30 +45701,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of CertificateSigningRequest
HTTP Request
@@ -45127,7 +45772,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
@@ -45150,32 +45795,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 CertificateSigningRequest
HTTP Request
@@ -45233,30 +45882,34 @@ Appears In:
-List
+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 CertificateSigningRequest
HTTP Request
@@ -45300,7 +45953,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
@@ -45323,30 +45976,34 @@ Appears In:
-Watch
+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 CertificateSigningRequest
HTTP Request
@@ -45405,7 +46062,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
@@ -45428,30 +46085,34 @@ Appears In:
-Watch List
+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 CertificateSigningRequest
HTTP Request
@@ -45495,7 +46156,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
@@ -45518,32 +46179,36 @@ Appears In:
-Status Operations
+Status Operations
See supported operations below...
-Replace Status
+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 CertificateSigningRequest
HTTP Request
@@ -45698,32 +46363,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+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
@@ -45781,30 +46450,34 @@ Appears In:
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified ClusterRole
HTTP Request
@@ -45869,30 +46542,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified ClusterRole
HTTP Request
@@ -45961,30 +46638,34 @@ Appears In:
-Delete
+Delete
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
@@ -46061,30 +46742,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of ClusterRole
HTTP Request
@@ -46128,7 +46813,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
@@ -46151,32 +46836,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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
@@ -46226,30 +46915,34 @@ Appears In:
-List
+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
@@ -46293,7 +46986,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
@@ -46316,30 +47009,34 @@ Appears In:
-Watch
+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
@@ -46398,7 +47095,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
@@ -46421,30 +47118,34 @@ Appears In:
-Watch List
+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 ClusterRole
HTTP Request
@@ -46488,7 +47189,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
@@ -46597,32 +47298,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a ClusterRoleBinding
HTTP Request
@@ -46667,10 +47372,6 @@ Appears In:
-202 ClusterRoleBinding
-Accepted
-
-
200 ClusterRoleBinding
OK
@@ -46678,32 +47379,40 @@ Appears In:
201 ClusterRoleBinding
Created
+
+202 ClusterRoleBinding
+Accepted
+
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified ClusterRoleBinding
HTTP Request
@@ -46768,30 +47477,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified ClusterRoleBinding
HTTP Request
@@ -46860,30 +47573,34 @@ Appears In:
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a ClusterRoleBinding
HTTP Request
@@ -46960,30 +47677,34 @@ Appears In:
-Delete Collection
+Delete Collection
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
@@ -47027,7 +47748,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
@@ -47050,32 +47771,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 ClusterRoleBinding
HTTP Request
@@ -47125,30 +47850,34 @@ Appears In:
-List
+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 ClusterRoleBinding
HTTP Request
@@ -47192,7 +47921,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
@@ -47215,30 +47944,34 @@ Appears In:
-Watch
+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 ClusterRoleBinding
HTTP Request
@@ -47297,7 +48030,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
@@ -47320,30 +48053,34 @@ Appears In:
-Watch List
+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 ClusterRoleBinding
HTTP Request
@@ -47387,7 +48124,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
@@ -47489,32 +48226,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 ComponentStatus
HTTP Request
@@ -47564,30 +48305,34 @@ Appears In:
-List
+List
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
list objects of kind ComponentStatus
HTTP Request
@@ -47631,7 +48376,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
@@ -47706,32 +48451,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a LocalSubjectAccessReview
HTTP Request
@@ -47791,10 +48540,6 @@ Appears In:
-200 LocalSubjectAccessReview
-OK
-
-
201 LocalSubjectAccessReview
Created
@@ -47802,6 +48547,10 @@ Appears In:
202 LocalSubjectAccessReview
Accepted
+
+200 LocalSubjectAccessReview
+OK
+
@@ -47931,32 +48680,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a Namespace
HTTP Request
@@ -48014,30 +48767,34 @@ Appears In:
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified Namespace
HTTP Request
@@ -48102,30 +48859,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified Namespace
HTTP Request
@@ -48185,39 +48946,43 @@ Appears In:
-201 Namespace
-Created
-
-
200 Namespace
OK
+
+201 Namespace
+Created
+
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a Namespace
HTTP Request
@@ -48294,32 +49059,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 Namespace
HTTP Request
@@ -48377,30 +49146,34 @@ Appears In:
-List
+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 Namespace
HTTP Request
@@ -48444,7 +49217,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
@@ -48467,30 +49240,34 @@ Appears In:
-Watch
+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 Namespace
HTTP Request
@@ -48549,7 +49326,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
@@ -48572,30 +49349,34 @@ Appears In:
-Watch List
+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 Namespace
HTTP Request
@@ -48639,7 +49420,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
@@ -48662,32 +49443,36 @@ Appears In:
-Status Operations
+Status Operations
See supported operations below...
-Patch Status
+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 Namespace
HTTP Request
@@ -48752,30 +49537,34 @@ Appears In:
-Read Status
+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 Namespace
HTTP Request
@@ -48825,30 +49614,34 @@ Appears In:
-Replace Status
+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 Namespace
HTTP Request
@@ -49100,32 +49893,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a Node
HTTP Request
@@ -49170,6 +49967,10 @@ Appears In:
+201 Node
+Created
+
+
202 Node
Accepted
@@ -49177,36 +49978,36 @@ Appears In:
200 Node
OK
-
-201 Node
-Created
-
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified Node
HTTP Request
@@ -49271,30 +50072,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified Node
HTTP Request
@@ -49363,30 +50168,34 @@ Appears In:
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a Node
HTTP Request
@@ -49463,30 +50272,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of Node
HTTP Request
@@ -49530,7 +50343,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
@@ -49553,32 +50366,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 Node
HTTP Request
@@ -49636,30 +50453,34 @@ Appears In:
-List
+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 Node
HTTP Request
@@ -49703,7 +50524,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
@@ -49726,30 +50547,34 @@ Appears In:
-Watch
+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 Node
HTTP Request
@@ -49808,7 +50633,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
@@ -49831,30 +50656,34 @@ Appears In:
-Watch List
+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 Node
HTTP Request
@@ -49898,7 +50727,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
@@ -49921,32 +50750,36 @@ Appears In:
-Status Operations
+Status Operations
See supported operations below...
-Patch Status
+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 Node
HTTP Request
@@ -50011,30 +50844,34 @@ Appears In:
-Read Status
+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 Node
HTTP Request
@@ -50084,30 +50921,34 @@ Appears In:
-Replace Status
+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 Node
HTTP Request
@@ -50176,32 +51017,36 @@ Appears In:
-Proxy Operations
+Proxy Operations
See supported operations below...
-Create Connect Proxy
+Create Connect Proxy
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
connect POST requests to proxy of Node
HTTP Request
@@ -50251,30 +51096,34 @@ Appears In:
-Create Connect Proxy Path
+Create Connect Proxy Path
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
connect POST requests to proxy of Node
HTTP Request
@@ -50328,150 +51177,34 @@ Appears In:
-Create Proxy
-
- kubectl Command
-
-
-Coming Soon
-
-
- curl Command (requires kubectl proxy to be running )
-
-
-Coming Soon
-
-
- Output
-
-
-Coming Soon
-
-
- Response Body
-
-
-Coming Soon
-
-proxy POST requests to Node
-HTTP Request
-POST /api/v1/proxy/nodes/{name}
-Path Parameters
-
-
-
-Parameter
-Description
-
-
-
-
-name
-name of the Node
-
-
-
-Response
-
-
-
-Code
-Description
-
-
-
-
-200 string
-OK
-
-
-
-Create Proxy Path
-
- kubectl Command
-
-
-Coming Soon
-
-
- curl Command (requires kubectl proxy to be running )
-
-
-Coming Soon
-
-
- Output
-
-
-Coming Soon
-
-
- Response Body
-
-
-Coming Soon
-
-proxy POST requests to Node
-HTTP Request
-POST /api/v1/proxy/nodes/{name}/{path}
-Path Parameters
-
-
-
-Parameter
-Description
-
-
-
-
-name
-name of the Node
-
-
-path
-path to the resource
-
-
-
-Response
-
-
-
-Code
-Description
-
-
-
-
-200 string
-OK
-
-
-
-Delete Connect Proxy
+Delete Connect Proxy
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
connect DELETE requests to proxy of Node
HTTP Request
@@ -50521,30 +51254,34 @@ Appears In:
-Delete Connect Proxy Path
+Delete Connect Proxy Path
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
connect DELETE requests to proxy of Node
HTTP Request
@@ -50598,150 +51335,34 @@ Appears In:
-Delete Proxy
-
- kubectl Command
-
-
-Coming Soon
-
-
- curl Command (requires kubectl proxy to be running )
-
-
-Coming Soon
-
-
- Output
-
-
-Coming Soon
-
-
- Response Body
-
-
-Coming Soon
-
-proxy DELETE requests to Node
-HTTP Request
-DELETE /api/v1/proxy/nodes/{name}
-Path Parameters
-
-
-
-Parameter
-Description
-
-
-
-
-name
-name of the Node
-
-
-
-Response
-
-
-
-Code
-Description
-
-
-
-
-200 string
-OK
-
-
-
-Delete Proxy Path
-
- kubectl Command
-
-
-Coming Soon
-
-
- curl Command (requires kubectl proxy to be running )
-
-
-Coming Soon
-
-
- Output
-
-
-Coming Soon
-
-
- Response Body
-
-
-Coming Soon
-
-proxy DELETE requests to Node
-HTTP Request
-DELETE /api/v1/proxy/nodes/{name}/{path}
-Path Parameters
-
-
-
-Parameter
-Description
-
-
-
-
-name
-name of the Node
-
-
-path
-path to the resource
-
-
-
-Response
-
-
-
-Code
-Description
-
-
-
-
-200 string
-OK
-
-
-
-Get Connect Proxy
+Get Connect Proxy
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
connect GET requests to proxy of Node
HTTP Request
@@ -50791,30 +51412,34 @@ Appears In:
-Get Connect Proxy Path
+Get Connect Proxy Path
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
connect GET requests to proxy of Node
HTTP Request
@@ -50868,150 +51493,34 @@ Appears In:
-Get Proxy
-
- kubectl Command
-
-
-Coming Soon
-
-
- curl Command (requires kubectl proxy to be running )
-
-
-Coming Soon
-
-
- Output
-
-
-Coming Soon
-
-
- Response Body
-
-
-Coming Soon
-
-proxy GET requests to Node
-HTTP Request
-GET /api/v1/proxy/nodes/{name}
-Path Parameters
-
-
-
-Parameter
-Description
-
-
-
-
-name
-name of the Node
-
-
-
-Response
-
-
-
-Code
-Description
-
-
-
-
-200 string
-OK
-
-
-
-Get Proxy Path
-
- kubectl Command
-
-
-Coming Soon
-
-
- curl Command (requires kubectl proxy to be running )
-
-
-Coming Soon
-
-
- Output
-
-
-Coming Soon
-
-
- Response Body
-
-
-Coming Soon
-
-proxy GET requests to Node
-HTTP Request
-GET /api/v1/proxy/nodes/{name}/{path}
-Path Parameters
-
-
-
-Parameter
-Description
-
-
-
-
-name
-name of the Node
-
-
-path
-path to the resource
-
-
-
-Response
-
-
-
-Code
-Description
-
-
-
-
-200 string
-OK
-
-
-
-Head Connect Proxy
+Head Connect Proxy
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
connect HEAD requests to proxy of Node
HTTP Request
@@ -51061,30 +51570,34 @@ Appears In:
-Head Connect Proxy Path
+Head Connect Proxy Path
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
connect HEAD requests to proxy of Node
HTTP Request
@@ -51138,30 +51651,34 @@ Appears In:
-Replace Connect Proxy
+Replace Connect Proxy
kubectl Command
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 Node
HTTP Request
@@ -51211,30 +51728,34 @@ Appears In:
-Replace Connect Proxy Path
+Replace Connect Proxy Path
kubectl Command
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 Node
HTTP Request
@@ -51288,126 +51809,6 @@ Appears In:
-Replace Proxy
-
- kubectl Command
-
-
-Coming Soon
-
-
- curl Command (requires kubectl proxy to be running )
-
-
-Coming Soon
-
-
- Output
-
-
-Coming Soon
-
-
- Response Body
-
-
-Coming Soon
-
-proxy PUT requests to Node
-HTTP Request
-PUT /api/v1/proxy/nodes/{name}
-Path Parameters
-
-
-
-Parameter
-Description
-
-
-
-
-name
-name of the Node
-
-
-
-Response
-
-
-
-Code
-Description
-
-
-
-
-200 string
-OK
-
-
-
-Replace Proxy Path
-
- kubectl Command
-
-
-Coming Soon
-
-
- curl Command (requires kubectl proxy to be running )
-
-
-Coming Soon
-
-
- Output
-
-
-Coming Soon
-
-
- Response Body
-
-
-Coming Soon
-
-proxy PUT requests to Node
-HTTP Request
-PUT /api/v1/proxy/nodes/{name}/{path}
-Path Parameters
-
-
-
-Parameter
-Description
-
-
-
-
-name
-name of the Node
-
-
-path
-path to the resource
-
-
-
-Response
-
-
-
-Code
-Description
-
-
-
-
-200 string
-OK
-
-
-
PersistentVolume v1 core
@@ -51519,14 +51920,14 @@ Appears In:
csi CSIPersistentVolumeSource
-CSI represents storage that handled by an external CSI driver
+CSI represents storage that handled by an external CSI driver (Beta feature).
fc FCVolumeSource
FC represents a Fibre Channel resource that is attached to a kubelet's host machine and then exposed to the pod.
-flexVolume FlexVolumeSource
+flexVolume FlexPersistentVolumeSource
FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.
@@ -51562,8 +51963,12 @@ Appears In:
NFS represents an NFS mount on the host. Provisioned by an admin. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs
+nodeAffinity VolumeNodeAffinity
+NodeAffinity defines constraints that limit what nodes this volume can be accessed from. This field influences the scheduling of pods that use this volume.
+
+
persistentVolumeReclaimPolicy string
-What happens to a persistent volume when released from its claim. Valid options are Retain (default) and Recycle. Recycling must be supported by the volume plugin underlying this persistent volume. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#reclaiming
+What happens to a persistent volume when released from its claim. Valid options are Retain (default for manually created PersistentVolumes), Delete (default for dynamically provisioned PersistentVolumes), and Recycle (deprecated). Recycle must be supported by the volume plugin underlying this PersistentVolume. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#reclaiming
photonPersistentDisk PhotonPersistentDiskVolumeSource
@@ -51660,32 +52065,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a PersistentVolume
HTTP Request
@@ -51730,10 +52139,6 @@ Appears In:
-202 PersistentVolume
-Accepted
-
-
200 PersistentVolume
OK
@@ -51741,32 +52146,40 @@ Appears In:
201 PersistentVolume
Created
+
+202 PersistentVolume
+Accepted
+
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified PersistentVolume
HTTP Request
@@ -51831,30 +52244,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified PersistentVolume
HTTP Request
@@ -51923,30 +52340,34 @@ Appears In:
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a PersistentVolume
HTTP Request
@@ -52023,30 +52444,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of PersistentVolume
HTTP Request
@@ -52090,7 +52515,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
@@ -52113,32 +52538,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 PersistentVolume
HTTP Request
@@ -52196,30 +52625,34 @@ Appears In:
-List
+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 PersistentVolume
HTTP Request
@@ -52263,7 +52696,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
@@ -52286,30 +52719,34 @@ Appears In:
-Watch
+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 PersistentVolume
HTTP Request
@@ -52368,7 +52805,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
@@ -52391,30 +52828,34 @@ Appears In:
-Watch List
+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 PersistentVolume
HTTP Request
@@ -52458,7 +52899,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
@@ -52481,32 +52922,36 @@ Appears In:
-Status Operations
+Status Operations
See supported operations below...
-Patch Status
+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 PersistentVolume
HTTP Request
@@ -52571,30 +53016,34 @@ Appears In:
-Read Status
+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 PersistentVolume
HTTP Request
@@ -52644,30 +53093,34 @@ Appears In:
-Replace Status
+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 PersistentVolume
HTTP Request
@@ -52871,32 +53324,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a ResourceQuota
HTTP Request
@@ -52969,30 +53426,34 @@ Appears In:
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified ResourceQuota
HTTP Request
@@ -53061,30 +53522,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified ResourceQuota
HTTP Request
@@ -53157,30 +53622,34 @@ Appears In:
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a ResourceQuota
HTTP Request
@@ -53261,30 +53730,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of ResourceQuota
HTTP Request
@@ -53343,7 +53816,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
@@ -53366,32 +53839,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 ResourceQuota
HTTP Request
@@ -53453,30 +53930,34 @@ Appears In:
-List
+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 ResourceQuota
HTTP Request
@@ -53535,7 +54016,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
@@ -53558,30 +54039,34 @@ Appears In:
-List All Namespaces
+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 ResourceQuota
HTTP Request
@@ -53625,7 +54110,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
@@ -53648,30 +54133,34 @@ Appears In:
-Watch
+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 ResourceQuota
HTTP Request
@@ -53734,7 +54223,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
@@ -53757,30 +54246,34 @@ Appears In:
-Watch List
+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 ResourceQuota
HTTP Request
@@ -53839,7 +54332,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
@@ -53862,30 +54355,34 @@ Appears In:
-Watch List All Namespaces
+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 ResourceQuota
HTTP Request
@@ -53929,7 +54426,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
@@ -53952,32 +54449,36 @@ Appears In:
-Status Operations
+Status Operations
See supported operations below...
-Patch Status
+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 ResourceQuota
HTTP Request
@@ -54046,30 +54547,34 @@ Appears In:
-Read Status
+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 ResourceQuota
HTTP Request
@@ -54123,30 +54628,34 @@ Appears In:
-Replace Status
+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 ResourceQuota
HTTP Request
@@ -54210,13 +54719,13 @@ Appears In:
-200 ResourceQuota
-OK
-
-
201 ResourceQuota
Created
+
+200 ResourceQuota
+OK
+
@@ -54301,32 +54810,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a Role
HTTP Request
@@ -54399,30 +54912,34 @@ Appears In:
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified Role
HTTP Request
@@ -54491,30 +55008,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified Role
HTTP Request
@@ -54587,30 +55108,34 @@ Appears In:
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a Role
HTTP Request
@@ -54691,30 +55216,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of Role
HTTP Request
@@ -54773,7 +55302,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
@@ -54796,32 +55325,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 Role
HTTP Request
@@ -54875,30 +55408,34 @@ Appears In:
-List
+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 Role
HTTP Request
@@ -54957,7 +55494,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
@@ -54980,30 +55517,34 @@ Appears In:
-List All Namespaces
+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 Role
HTTP Request
@@ -55047,7 +55588,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
@@ -55070,30 +55611,34 @@ Appears In:
-Watch
+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 Role
HTTP Request
@@ -55156,7 +55701,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
@@ -55179,30 +55724,34 @@ Appears In:
-Watch List
+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 Role
HTTP Request
@@ -55261,7 +55810,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
@@ -55284,30 +55833,34 @@ Appears In:
-Watch List All Namespaces
+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 Role
HTTP Request
@@ -55351,7 +55904,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
@@ -55460,32 +56013,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a RoleBinding
HTTP Request
@@ -55545,6 +56102,10 @@ Appears In:
+201 RoleBinding
+Created
+
+
202 RoleBinding
Accepted
@@ -55552,36 +56113,36 @@ Appears In:
200 RoleBinding
OK
-
-201 RoleBinding
-Created
-
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified RoleBinding
HTTP Request
@@ -55650,30 +56211,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified RoleBinding
HTTP Request
@@ -55737,39 +56302,43 @@ Appears In:
-200 RoleBinding
-OK
-
-
201 RoleBinding
Created
+
+200 RoleBinding
+OK
+
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a RoleBinding
HTTP Request
@@ -55850,30 +56419,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of RoleBinding
HTTP Request
@@ -55932,7 +56505,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
@@ -55955,32 +56528,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 RoleBinding
HTTP Request
@@ -56034,30 +56611,34 @@ Appears In:
-List
+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 RoleBinding
HTTP Request
@@ -56116,7 +56697,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
@@ -56139,30 +56720,34 @@ Appears In:
-List All Namespaces
+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 RoleBinding
HTTP Request
@@ -56206,7 +56791,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
@@ -56229,30 +56814,34 @@ Appears In:
-Watch
+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 RoleBinding
HTTP Request
@@ -56315,7 +56904,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
@@ -56338,30 +56927,34 @@ Appears In:
-Watch List
+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 RoleBinding
HTTP Request
@@ -56420,7 +57013,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
@@ -56443,30 +57036,34 @@ Appears In:
-Watch List All Namespaces
+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 RoleBinding
HTTP Request
@@ -56510,7 +57107,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
@@ -56611,32 +57208,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a SelfSubjectAccessReview
HTTP Request
@@ -56681,10 +57282,6 @@ Appears In:
-202 SelfSubjectAccessReview
-Accepted
-
-
200 SelfSubjectAccessReview
OK
@@ -56692,6 +57289,10 @@ Appears In:
201 SelfSubjectAccessReview
Created
+
+202 SelfSubjectAccessReview
+Accepted
+
@@ -56768,32 +57369,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a SelfSubjectRulesReview
HTTP Request
@@ -56838,6 +57443,10 @@ Appears In:
+200 SelfSubjectRulesReview
+OK
+
+
201 SelfSubjectRulesReview
Created
@@ -56845,10 +57454,6 @@ Appears In:
202 SelfSubjectRulesReview
Accepted
-
-200 SelfSubjectRulesReview
-OK
-
@@ -56938,32 +57543,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a ServiceAccount
HTTP Request
@@ -57023,10 +57632,6 @@ Appears In:
-200 ServiceAccount
-OK
-
-
201 ServiceAccount
Created
@@ -57034,32 +57639,40 @@ Appears In:
202 ServiceAccount
Accepted
+
+200 ServiceAccount
+OK
+
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified ServiceAccount
HTTP Request
@@ -57128,30 +57741,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified ServiceAccount
HTTP Request
@@ -57215,39 +57832,43 @@ Appears In:
-200 ServiceAccount
-OK
-
-
201 ServiceAccount
Created
+
+200 ServiceAccount
+OK
+
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a ServiceAccount
HTTP Request
@@ -57328,30 +57949,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of ServiceAccount
HTTP Request
@@ -57410,7 +58035,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
@@ -57433,32 +58058,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 ServiceAccount
HTTP Request
@@ -57520,30 +58149,34 @@ Appears In:
-List
+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 ServiceAccount
HTTP Request
@@ -57602,7 +58235,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
@@ -57625,30 +58258,34 @@ Appears In:
-List All Namespaces
+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 ServiceAccount
HTTP Request
@@ -57692,7 +58329,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
@@ -57715,30 +58352,34 @@ Appears In:
-Watch
+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 ServiceAccount
HTTP Request
@@ -57801,7 +58442,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
@@ -57824,30 +58465,34 @@ Appears In:
-Watch List
+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 ServiceAccount
HTTP Request
@@ -57906,7 +58551,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
@@ -57929,30 +58574,34 @@ Appears In:
-Watch List All Namespaces
+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 ServiceAccount
HTTP Request
@@ -57996,7 +58645,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
@@ -58150,32 +58799,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+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
@@ -58220,10 +58873,6 @@ Appears In:
-200 SubjectAccessReview
-OK
-
-
201 SubjectAccessReview
Created
@@ -58231,6 +58880,10 @@ Appears In:
202 SubjectAccessReview
Accepted
+
+200 SubjectAccessReview
+OK
+
@@ -58337,32 +58990,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+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
@@ -58407,10 +59064,6 @@ Appears In:
-202 TokenReview
-Accepted
-
-
200 TokenReview
OK
@@ -58418,6 +59071,10 @@ Appears In:
201 TokenReview
Created
+
+202 TokenReview
+Accepted
+
@@ -58536,32 +59193,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a NetworkPolicy
HTTP Request
@@ -58621,10 +59282,6 @@ Appears In:
-200 NetworkPolicy
-OK
-
-
201 NetworkPolicy
Created
@@ -58632,32 +59289,40 @@ Appears In:
202 NetworkPolicy
Accepted
+
+200 NetworkPolicy
+OK
+
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified NetworkPolicy
HTTP Request
@@ -58726,30 +59391,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified NetworkPolicy
HTTP Request
@@ -58822,30 +59491,34 @@ Appears In:
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a NetworkPolicy
HTTP Request
@@ -58926,30 +59599,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of NetworkPolicy
HTTP Request
@@ -59008,7 +59685,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
@@ -59031,32 +59708,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 NetworkPolicy
HTTP Request
@@ -59118,30 +59799,34 @@ Appears In:
-List
+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 NetworkPolicy
HTTP Request
@@ -59200,7 +59885,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
@@ -59223,30 +59908,34 @@ Appears In:
-List All Namespaces
+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 NetworkPolicy
HTTP Request
@@ -59290,7 +59979,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
@@ -59313,30 +60002,34 @@ Appears In:
-Watch
+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
@@ -59399,7 +60092,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
@@ -59422,30 +60115,34 @@ Appears In:
-Watch List
+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 NetworkPolicy
HTTP Request
@@ -59504,7 +60201,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
@@ -59527,30 +60224,34 @@ Appears In:
-Watch List All Namespaces
+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
@@ -59594,7 +60295,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
@@ -59749,7 +60450,7 @@ Appears In:
-APIServiceCondition v1beta1 apiregistration
+APIService v1 apiregistration
@@ -59761,16 +60462,77 @@ Appears In:
apiregistration
-v1beta1
-APIServiceCondition
+v1
+APIService
+Other api versions of this object exist: v1beta1
+
+APIService represents a server for a particular GroupVersion. Name must be "version.group".
+
+
+APIServiceCondition v1 apiregistration
+
+
+
+Group
+Version
+Kind
+
+
+
+
+apiregistration
+v1
+APIServiceCondition
+
+
+
+Other api versions of this object exist: v1beta1
+
+
+
+
@@ -60284,7 +61046,7 @@ Appears In:
-Represents storage that is managed by an external CSI volume driver
+Represents storage that is managed by an external CSI volume driver (Beta feature)
Appears In:
@@ -60301,14 +61063,34 @@ Appears In:
+controllerPublishSecretRef SecretReference
+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.
+
+
driver string
Driver is the name of the driver to use for this volume. Required.
+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.
+
+
+nodePublishSecretRef SecretReference
+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 SecretReference
+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.
@@ -60889,7 +61671,7 @@ Appears In:
names string array
-Names by which this image is known. e.g. ["gcr.io/google_containers/hyperkube:v1.0.7", "dockerhub.io/google_containers/hyperkube:v1.0.7"]
+Names by which this image is known. e.g. ["k8s.gcr.io/hyperkube:v1.0.7", "dockerhub.io/google_containers/hyperkube:v1.0.7"]
sizeBytes integer
@@ -61283,6 +62065,10 @@ Appears In:
+categories string array
+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.
@@ -61304,6 +62090,134 @@ Appears In:
+CustomResourceSubresourceScale v1beta1 apiextensions
+
+
+
+Group
+Version
+Kind
+
+
+
+
+apiextensions
+v1beta1
+CustomResourceSubresourceScale
+
+
+
+CustomResourceSubresourceScale defines how to serve the scale subresource for CustomResources.
+
+
+
+
+
+Field
+Description
+
+
+
+
+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.
+
+
+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.
+
+
+
+CustomResourceSubresourceStatus v1beta1 apiextensions
+
+
+
+Group
+Version
+Kind
+
+
+
+
+apiextensions
+v1beta1
+CustomResourceSubresourceStatus
+
+
+
+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
+
+
+
+
+
+Field
+Description
+
+
+
+
+
+
+
+
+CustomResourceSubresources v1beta1 apiextensions
+
+
+
+Group
+Version
+Kind
+
+
+
+
+apiextensions
+v1beta1
+CustomResourceSubresources
+
+
+
+CustomResourceSubresources defines the status and scale subresources for CustomResources.
+
+
+
CustomResourceValidation v1beta1 apiextensions
@@ -62301,6 +63215,108 @@ Appears In:
+ExternalMetricSource v2beta1 autoscaling
+
+
+
+Group
+Version
+Kind
+
+
+
+
+autoscaling
+v2beta1
+ExternalMetricSource
+
+
+
+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.
+
+
+
+
+
+Field
+Description
+
+
+
+
+metricName string
+metricName is the name of the metric in question.
+
+
+metricSelector LabelSelector
+metricSelector is used to identify a specific time series within a given metric.
+
+
+targetAverageValue Quantity
+targetAverageValue is the target per-pod value of global metric (as a quantity). Mutually exclusive with TargetValue.
+
+
+targetValue Quantity
+targetValue is the target value of the metric (as a quantity). Mutually exclusive with TargetAverageValue.
+
+
+
+ExternalMetricStatus v2beta1 autoscaling
+
+
+
+Group
+Version
+Kind
+
+
+
+
+autoscaling
+v2beta1
+ExternalMetricStatus
+
+
+
+ExternalMetricStatus indicates the current value of a global metric not associated with any Kubernetes object.
+
+
+
+
+
+Field
+Description
+
+
+
+
+currentAverageValue Quantity
+currentAverageValue is the current value of metric averaged over autoscaled pods.
+
+
+currentValue Quantity
+currentValue is the current value of the metric (as a quantity)
+
+
+metricName string
+metricName is the name of a metric used for autoscaling in metric system.
+
+
+metricSelector LabelSelector
+metricSelector is used to identify a specific time series within a given metric.
+
+
+
FCVolumeSource v1 core
@@ -62400,6 +63416,61 @@ Appears In:
+FlexPersistentVolumeSource v1 core
+
+
+
+Group
+Version
+Kind
+
+
+
+
+Core
+v1
+FlexPersistentVolumeSource
+
+
+
+FlexPersistentVolumeSource represents a generic persistent volume resource that is provisioned/attached using an exec based plugin.
+
+
+
+
+
+Field
+Description
+
+
+
+
+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.
+
+
+secretRef SecretReference
+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.
+
+
+
FlexVolumeSource v1 core
@@ -62422,7 +63493,6 @@ Appears In:
Appears In:
@@ -62850,7 +63920,7 @@ Appears In:
-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 '#'.
+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 '#'.
Appears In:
@@ -63622,7 +64692,7 @@ Appears In:
-JSONSchemaProps is a JSON-Schema following Specification Draft 4 (http://json-schema.org/ ).
+JSONSchemaProps is a JSON-Schema following Specification Draft 4 (http://json-schema.org/) .
@@ -64559,6 +65634,10 @@ Appears In:
+external ExternalMetricSource
+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).
+
+
object ObjectMetricSource
object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).
@@ -64572,7 +65651,7 @@ Appears In:
type string
-type is the type of metric source. It should match one of the fields below.
+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.
@@ -64610,6 +65689,10 @@ Appears In:
+external ExternalMetricStatus
+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).
+
+
object ObjectMetricStatus
object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).
@@ -64623,7 +65706,7 @@ Appears In:
type string
-type is the type of metric source. It will match one of the fields below.
+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.
@@ -65155,6 +66238,7 @@ Appears In:
@@ -65490,6 +66574,7 @@ Appears In:
Appears In:
@@ -66375,6 +67462,10 @@ Appears In:
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.
@@ -66798,6 +67889,8 @@ Appears In:
-ServiceReference v1beta1 admissionregistration
+ServiceReference v1 apiregistration
@@ -68405,18 +69505,20 @@ Appears In:
-admissionregistration
-v1beta1
+apiregistration
+v1
ServiceReference
+
+
ServiceReference holds a reference to Service.legacy.k8s.io
@@ -68429,15 +69531,11 @@ Appears In:
name string
-name is the name of the service. Required
+Name is the name of the service
namespace string
-namespace is the namespace of the service. Required
-
-
-path string
-path is an optional URL path which will be sent in any request to this service.
+Namespace is the namespace of the service
@@ -69131,6 +70229,7 @@ Appears In:
Appears In:
@@ -69289,7 +70389,7 @@ Appears In:
-VolumeAttachmentSource v1alpha1 storage
+VolumeAttachment v1beta1 storage
@@ -69301,17 +70401,77 @@ Appears In:
storage
-v1alpha1
+v1beta1
+VolumeAttachment
+
+
+
+Other api versions of this object exist: v1alpha1
+
+VolumeAttachment captures the intent to attach or detach the specified volume to/from the specified node.
+VolumeAttachment objects are non-namespaced.
+
+
+
+VolumeAttachmentSource v1beta1 storage
+
+
+
+Group
+Version
+Kind
+
+
+
+
+storage
+v1beta1
VolumeAttachmentSource
+Other api versions of this object exist: v1alpha1
+
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.
@@ -69371,7 +70531,7 @@ Appears In:
-VolumeError v1alpha1 storage
+VolumeError v1beta1 storage
@@ -69383,17 +70543,19 @@ Appears In:
storage
-v1alpha1
+v1beta1
VolumeError
+Other api versions of this object exist: v1alpha1
+
VolumeError captures an error encountered during a volume operation.
@@ -69454,7 +70616,7 @@ Appears In:
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.
+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 beta in 1.10.
name string
@@ -69470,6 +70632,45 @@ Appears In:
+VolumeNodeAffinity v1 core
+
+
+
+Group
+Version
+Kind
+
+
+
+
+Core
+v1
+VolumeNodeAffinity
+
+
+
+VolumeNodeAffinity defines constraints that limit what nodes this volume can be accessed from.
+
+
+
+
+
+Field
+Description
+
+
+
+
+required NodeSelector
+Required specifies hard node constraints that must be met.
+
+
+
VolumeProjection v1 core
@@ -69653,11 +70854,11 @@ Appears In:
namespaceSelector LabelSelector
-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.
+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.
rules RuleWithOperations array
-Rules describes what operations on what resources/subresources the webhook cares about. The webhook cares about an operation if it matches any Rule.
+Rules describes what operations on what resources/subresources the webhook cares about. The webhook cares about an operation if it matches any Rule. However, in order to prevent ValidatingAdmissionWebhooks and MutatingAdmissionWebhooks from putting the cluster in a state which cannot be recovered from without completely disabling the plugin, ValidatingAdmissionWebhooks and MutatingAdmissionWebhooks are never called on admission requests for ValidatingWebhookConfiguration and MutatingWebhookConfiguration objects.
@@ -69704,7 +70905,7 @@ Appears In:
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.
+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.
@@ -69755,6 +70956,1175 @@ Appears In:
OLD API VERSIONS
This section contains older versions of resources shown above.
+APIService v1beta1 apiregistration
+
+
+
+Group
+Version
+Kind
+
+
+
+
+apiregistration
+v1beta1
+APIService
+
+
+
+Other api versions of this object exist: v1
+
+
+APIService represents a server for a particular GroupVersion. Name must be "version.group".
+
+
+
+APIServiceSpec v1beta1 apiregistration
+
+
+
+
+
+Field
+Description
+
+
+
+
+caBundle string
+CABundle is a PEM encoded CA bundle which will be used to validate an API server's serving certificate.
+
+
+group string
+Group is the API group name this server hosts
+
+
+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
+
+
+insecureSkipTLSVerify boolean
+InsecureSkipTLSVerify disables TLS certificate verification when communicating with this server. This is strongly discouraged. You should use the CABundle instead.
+
+
+service ServiceReference
+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.
+
+
+version string
+Version is the API version this server hosts. For example, "v1"
+
+
+versionPriority integer
+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.
+
+
+
+APIServiceStatus v1beta1 apiregistration
+
+
+
+
+
+Field
+Description
+
+
+
+
+conditions APIServiceCondition array patch type : merge patch merge key : type
+Current service state of apiService.
+
+
+
+APIServiceList v1beta1 apiregistration
+
+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 an APIService
+HTTP Request
+POST /apis/apiregistration.k8s.io/v1beta1/apiservices
+Query Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+pretty
+If 'true', then the output is pretty printed.
+
+
+
+Body Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+body APIService
+
+
+
+
+Response
+
+Patch
+
+ kubectl Command
+
+
+Coming Soon
+
+
+
+ curl Command (requires kubectl proxy to be running )
+
+
+Coming Soon
+
+
+
+ Output
+
+
+Coming Soon
+
+
+
+ Response Body
+
+
+Coming Soon
+
+
+partially update the specified APIService
+HTTP Request
+PATCH /apis/apiregistration.k8s.io/v1beta1/apiservices/{name}
+Path Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+name
+name of the APIService
+
+
+
+Query Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+pretty
+If 'true', then the output is pretty printed.
+
+
+
+Body Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+body Patch
+
+
+
+
+Response
+
+
+
+Code
+Description
+
+
+
+
+200 APIService
+OK
+
+
+
+Replace
+
+ kubectl Command
+
+
+Coming Soon
+
+
+
+ curl Command (requires kubectl proxy to be running )
+
+
+Coming Soon
+
+
+
+ Output
+
+
+Coming Soon
+
+
+
+ Response Body
+
+
+Coming Soon
+
+
+replace the specified APIService
+HTTP Request
+PUT /apis/apiregistration.k8s.io/v1beta1/apiservices/{name}
+Path Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+name
+name of the APIService
+
+
+
+Query Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+pretty
+If 'true', then the output is pretty printed.
+
+
+
+Body Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+body APIService
+
+
+
+
+Response
+
+Delete
+
+ kubectl Command
+
+
+Coming Soon
+
+
+
+ curl Command (requires kubectl proxy to be running )
+
+
+Coming Soon
+
+
+
+ Output
+
+
+Coming Soon
+
+
+
+ Response Body
+
+
+Coming Soon
+
+
+delete an APIService
+HTTP Request
+DELETE /apis/apiregistration.k8s.io/v1beta1/apiservices/{name}
+Path Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+name
+name of the APIService
+
+
+
+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.
+
+
+
+Body Parameters
+
+Response
+
+
+
+Code
+Description
+
+
+
+
+200 Status
+OK
+
+
+
+Delete Collection
+
+ 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
+DELETE /apis/apiregistration.k8s.io/v1beta1/apiservices
+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.
+
+
+
+Response
+
+
+
+Code
+Description
+
+
+
+
+200 Status
+OK
+
+
+
+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 APIService
+HTTP Request
+GET /apis/apiregistration.k8s.io/v1beta1/apiservices/{name}
+Path Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+name
+name of the APIService
+
+
+
+Query Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+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.
+
+
+
+Response
+
+
+
+Code
+Description
+
+
+
+
+200 APIService
+OK
+
+
+
+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 APIService
+HTTP Request
+GET /apis/apiregistration.k8s.io/v1beta1/apiservices
+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.
+
+
+
+Response
+
+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 APIService
+HTTP Request
+GET /apis/apiregistration.k8s.io/v1beta1/watch/apiservices/{name}
+Path Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+name
+name of the APIService
+
+
+
+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.
+
+
+
+Response
+
+
+
+Code
+Description
+
+
+
+
+200 WatchEvent
+OK
+
+
+
+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 APIService
+HTTP Request
+GET /apis/apiregistration.k8s.io/v1beta1/watch/apiservices
+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.
+
+
+
+Response
+
+
+
+Code
+Description
+
+
+
+
+200 WatchEvent
+OK
+
+
+
+Status Operations
+See supported operations below...
+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 APIService
+HTTP Request
+PUT /apis/apiregistration.k8s.io/v1beta1/apiservices/{name}/status
+Path Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+name
+name of the APIService
+
+
+
+Query Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+pretty
+If 'true', then the output is pretty printed.
+
+
+
+Body Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+body APIService
+
+
+
+
+Response
+
+
+APIServiceCondition v1beta1 apiregistration
+
+
+
+Group
+Version
+Kind
+
+
+
+
+apiregistration
+v1beta1
+APIServiceCondition
+
+
+
+Other api versions of this object exist: v1
+
+
+
+
+
+
+
+
+
+Field
+Description
+
+
+
+
+lastTransitionTime Time
+Last time the condition transitioned from one status to another.
+
+
+message string
+Human-readable message indicating details about last transition.
+
+
+reason string
+Unique, one-word, CamelCase reason for the condition's last transition.
+
+
+status string
+Status is the status of the condition. Can be True, False, Unknown.
+
+
+type string
+Type is the type of the condition.
+
+
+
+
AggregationRule v1beta1 rbac
@@ -69841,6 +72211,86 @@ Appears In:
+AllowedFlexVolume v1beta1 policy
+
+
+
+Group
+Version
+Kind
+
+
+
+
+policy
+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 policy
+
+
+
+Group
+Version
+Kind
+
+
+
+
+policy
+v1beta1
+AllowedHostPath
+
+
+
+defines the host volume conditions that will be enabled by a policy for pods to use. It requires the path prefix to be defined.
+
+
+
+
+
+Field
+Description
+
+
+
+
+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
+
+
+
+
ClusterRole v1beta1 rbac
@@ -69926,32 +72376,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+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
@@ -69996,6 +72450,10 @@ Appears In:
+200 ClusterRole
+OK
+
+
201 ClusterRole
Created
@@ -70003,36 +72461,36 @@ Appears In:
202 ClusterRole
Accepted
-
-200 ClusterRole
-OK
-
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified ClusterRole
HTTP Request
@@ -70097,30 +72555,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified ClusterRole
HTTP Request
@@ -70189,30 +72651,34 @@ Appears In:
-Delete
+Delete
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
@@ -70289,30 +72755,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of ClusterRole
HTTP Request
@@ -70356,7 +72826,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
@@ -70379,32 +72849,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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
@@ -70454,30 +72928,34 @@ Appears In:
-List
+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
@@ -70521,7 +72999,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
@@ -70544,30 +73022,34 @@ Appears In:
-Watch
+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
@@ -70626,7 +73108,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
@@ -70649,30 +73131,34 @@ Appears In:
-Watch List
+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 ClusterRole
HTTP Request
@@ -70716,7 +73202,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
@@ -70825,32 +73311,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+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
@@ -70895,6 +73385,10 @@ Appears In:
+200 ClusterRole
+OK
+
+
201 ClusterRole
Created
@@ -70902,36 +73396,36 @@ Appears In:
202 ClusterRole
Accepted
-
-200 ClusterRole
-OK
-
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified ClusterRole
HTTP Request
@@ -70996,30 +73490,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified ClusterRole
HTTP Request
@@ -71088,30 +73586,34 @@ Appears In:
-Delete
+Delete
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
@@ -71188,30 +73690,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of ClusterRole
HTTP Request
@@ -71255,7 +73761,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
@@ -71278,32 +73784,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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
@@ -71353,30 +73863,34 @@ Appears In:
-List
+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
@@ -71420,7 +73934,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
@@ -71443,30 +73957,34 @@ Appears In:
-Watch
+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
@@ -71525,7 +74043,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
@@ -71548,30 +74066,34 @@ Appears In:
-Watch List
+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 ClusterRole
HTTP Request
@@ -71615,7 +74137,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
@@ -71724,32 +74246,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a ClusterRoleBinding
HTTP Request
@@ -71794,6 +74320,10 @@ Appears In:
+202 ClusterRoleBinding
+Accepted
+
+
200 ClusterRoleBinding
OK
@@ -71801,36 +74331,36 @@ Appears In:
201 ClusterRoleBinding
Created
-
-202 ClusterRoleBinding
-Accepted
-
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified ClusterRoleBinding
HTTP Request
@@ -71895,30 +74425,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified ClusterRoleBinding
HTTP Request
@@ -71978,39 +74512,43 @@ Appears In:
-201 ClusterRoleBinding
-Created
-
-
200 ClusterRoleBinding
OK
+
+201 ClusterRoleBinding
+Created
+
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a ClusterRoleBinding
HTTP Request
@@ -72087,30 +74625,34 @@ Appears In:
-Delete Collection
+Delete Collection
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
@@ -72154,7 +74696,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
@@ -72177,32 +74719,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 ClusterRoleBinding
HTTP Request
@@ -72252,30 +74798,34 @@ Appears In:
-List
+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 ClusterRoleBinding
HTTP Request
@@ -72319,7 +74869,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
@@ -72342,30 +74892,34 @@ Appears In:
-Watch
+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 ClusterRoleBinding
HTTP Request
@@ -72424,7 +74978,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
@@ -72447,30 +75001,34 @@ Appears In:
-Watch List
+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 ClusterRoleBinding
HTTP Request
@@ -72514,7 +75072,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
@@ -72623,32 +75181,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a ClusterRoleBinding
HTTP Request
@@ -72693,6 +75255,10 @@ Appears In:
+202 ClusterRoleBinding
+Accepted
+
+
200 ClusterRoleBinding
OK
@@ -72700,36 +75266,36 @@ Appears In:
201 ClusterRoleBinding
Created
-
-202 ClusterRoleBinding
-Accepted
-
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified ClusterRoleBinding
HTTP Request
@@ -72794,30 +75360,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified ClusterRoleBinding
HTTP Request
@@ -72877,39 +75447,43 @@ Appears In:
-200 ClusterRoleBinding
-OK
-
-
201 ClusterRoleBinding
Created
+
+200 ClusterRoleBinding
+OK
+
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a ClusterRoleBinding
HTTP Request
@@ -72986,30 +75560,34 @@ Appears In:
-Delete Collection
+Delete Collection
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
@@ -73053,7 +75631,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
@@ -73076,32 +75654,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 ClusterRoleBinding
HTTP Request
@@ -73151,30 +75733,34 @@ Appears In:
-List
+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 ClusterRoleBinding
HTTP Request
@@ -73218,7 +75804,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
@@ -73241,30 +75827,34 @@ Appears In:
-Watch
+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 ClusterRoleBinding
HTTP Request
@@ -73323,7 +75913,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
@@ -73346,30 +75936,34 @@ Appears In:
-Watch List
+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 ClusterRoleBinding
HTTP Request
@@ -73413,7 +76007,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
@@ -73522,32 +76116,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a ControllerRevision
HTTP Request
@@ -73607,6 +76205,10 @@ Appears In:
+200 ControllerRevision
+OK
+
+
201 ControllerRevision
Created
@@ -73614,36 +76216,36 @@ Appears In:
202 ControllerRevision
Accepted
-
-200 ControllerRevision
-OK
-
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified ControllerRevision
HTTP Request
@@ -73712,30 +76314,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified ControllerRevision
HTTP Request
@@ -73808,30 +76414,34 @@ Appears In:
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a ControllerRevision
HTTP Request
@@ -73912,30 +76522,34 @@ Appears In:
-Delete Collection
+Delete Collection
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
@@ -73994,7 +76608,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
@@ -74017,32 +76631,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 ControllerRevision
HTTP Request
@@ -74104,30 +76722,34 @@ Appears In:
-List
+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 ControllerRevision
HTTP Request
@@ -74186,7 +76808,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
@@ -74209,30 +76831,34 @@ Appears In:
-List All Namespaces
+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 ControllerRevision
HTTP Request
@@ -74276,7 +76902,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
@@ -74299,30 +76925,34 @@ Appears In:
-Watch
+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 ControllerRevision
HTTP Request
@@ -74385,7 +77015,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
@@ -74408,30 +77038,34 @@ Appears In:
-Watch List
+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
@@ -74490,7 +77124,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
@@ -74513,30 +77147,34 @@ Appears In:
-Watch List All Namespaces
+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 ControllerRevision
HTTP Request
@@ -74580,7 +77218,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
@@ -74689,32 +77327,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a ControllerRevision
HTTP Request
@@ -74774,10 +77416,6 @@ Appears In:
-201 ControllerRevision
-Created
-
-
202 ControllerRevision
Accepted
@@ -74785,32 +77423,40 @@ Appears In:
200 ControllerRevision
OK
+
+201 ControllerRevision
+Created
+
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified ControllerRevision
HTTP Request
@@ -74879,30 +77525,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified ControllerRevision
HTTP Request
@@ -74966,39 +77616,43 @@ Appears In:
-201 ControllerRevision
-Created
-
-
200 ControllerRevision
OK
+
+201 ControllerRevision
+Created
+
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a ControllerRevision
HTTP Request
@@ -75079,30 +77733,34 @@ Appears In:
-Delete Collection
+Delete Collection
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
@@ -75161,7 +77819,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
@@ -75184,32 +77842,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 ControllerRevision
HTTP Request
@@ -75271,30 +77933,34 @@ Appears In:
-List
+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 ControllerRevision
HTTP Request
@@ -75353,7 +78019,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
@@ -75376,30 +78042,34 @@ Appears In:
-List All Namespaces
+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 ControllerRevision
HTTP Request
@@ -75443,7 +78113,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
@@ -75466,30 +78136,34 @@ Appears In:
-Watch
+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 ControllerRevision
HTTP Request
@@ -75552,7 +78226,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
@@ -75575,30 +78249,34 @@ Appears In:
-Watch List
+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
@@ -75657,7 +78335,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
@@ -75680,30 +78358,34 @@ Appears In:
-Watch List All Namespaces
+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 ControllerRevision
HTTP Request
@@ -75747,7 +78429,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
@@ -75928,32 +78610,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a CronJob
HTTP Request
@@ -76013,10 +78699,6 @@ Appears In:
-200 CronJob
-OK
-
-
201 CronJob
Created
@@ -76024,32 +78706,40 @@ Appears In:
202 CronJob
Accepted
+
+200 CronJob
+OK
+
-Patch
+Patch
kubectl Command
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
@@ -76118,30 +78808,34 @@ Appears In:
-Replace
+Replace
kubectl Command
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
@@ -76214,30 +78908,34 @@ Appears In:
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a CronJob
HTTP Request
@@ -76318,30 +79016,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
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
@@ -76400,7 +79102,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
@@ -76423,32 +79125,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 CronJob
HTTP Request
@@ -76510,30 +79216,34 @@ Appears In:
-List
+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 CronJob
HTTP Request
@@ -76592,7 +79302,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
@@ -76615,30 +79325,34 @@ Appears In:
-List All Namespaces
+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 CronJob
HTTP Request
@@ -76682,7 +79396,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
@@ -76705,30 +79419,34 @@ Appears In:
-Watch
+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 CronJob
HTTP Request
@@ -76791,7 +79509,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
@@ -76814,30 +79532,34 @@ Appears In:
-Watch List
+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 CronJob
HTTP Request
@@ -76896,7 +79618,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
@@ -76919,30 +79641,34 @@ Appears In:
-Watch List All Namespaces
+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 CronJob
HTTP Request
@@ -76986,7 +79712,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
@@ -77009,32 +79735,36 @@ Appears In:
-Status Operations
+Status Operations
See supported operations below...
-Patch Status
+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 CronJob
HTTP Request
@@ -77103,30 +79833,34 @@ Appears In:
-Read Status
+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 CronJob
HTTP Request
@@ -77180,30 +79914,34 @@ Appears In:
-Replace Status
+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 CronJob
HTTP Request
@@ -77533,9 +80271,9 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
@@ -77563,6 +80301,7 @@ spec:
sleep 10 ;
done
' | kubectl create -f -
+
curl Command (requires kubectl proxy to be running )
@@ -77593,12 +80332,14 @@ spec:
sleep 10 ;
done
' http://127.0 .0.1:8001 /apis/apps/v1beta2/namespaces/default/daemonsets
+
Output
daemonset "daemonset-example" created
+
Response Body
@@ -77662,6 +80403,7 @@ spec:
"desiredNumberScheduled" : 0
}
}
+
create a DaemonSet
HTTP Request
@@ -77734,30 +80476,34 @@ spec:
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified DaemonSet
HTTP Request
@@ -77826,30 +80572,34 @@ spec:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified DaemonSet
HTTP Request
@@ -77913,21 +80663,22 @@ spec:
-201 DaemonSet
-Created
-
-
200 DaemonSet
OK
+
+201 DaemonSet
+Created
+
-Delete
+Delete
kubectl Command
$ kubectl delete daemonset daemonset-example
+
curl Command (requires kubectl proxy to be running )
@@ -77937,13 +80688,15 @@ $ kubectl proxy
$ curl -X DELETE -H 'Content-Type: application/yaml'
gracePeriodSeconds: 0
orphanDependents: false
-' ' http ://127.0 .0 .1 :8001 /apis/apps/v1beta2/namespaces/default /daemonsets/daemonset-example'
+' ' http ://127.0 .0 .1 :8001 /apis/apps/v1beta2/namespaces/default /daemonsets/daemonset-example'
+
Output
daemonset "daemonset-example" deleted
+
Response Body
@@ -77956,6 +80709,8 @@ orphanDependents: false
"status" : "Success" ,
"code" : 200
}
+
+
delete a DaemonSet
HTTP Request
@@ -78036,30 +80791,34 @@ orphanDependents: false
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of DaemonSet
HTTP Request
@@ -78118,7 +80877,7 @@ orphanDependents: false
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
@@ -78141,31 +80900,37 @@ orphanDependents: false
-Read Operations
+Read Operations
See supported operations below...
-Read
+Read
kubectl Command
$ 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/v1beta2/ namespaces/default/ daemonsets/daemonset-example
+$ kubectl proxy
+$ curl -X GET http: //127.0.0.1:8001/apis /apps/v 1beta2/namespaces/default/daemonsets/daemonset-example
+
Output
+
+
Response Body
+
+
read the specified DaemonSet
HTTP Request
@@ -78227,30 +80992,34 @@ $ curl -X GET http://
-List
+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 DaemonSet
HTTP Request
@@ -78309,7 +81078,7 @@ $ curl -X GET http://
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
@@ -78332,30 +81101,34 @@ $ curl -X GET http://
-List All Namespaces
+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 DaemonSet
HTTP Request
@@ -78399,7 +81172,7 @@ $ curl -X GET http://
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
@@ -78422,30 +81195,34 @@ $ curl -X GET http://
-Watch
+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 DaemonSet
HTTP Request
@@ -78508,7 +81285,7 @@ $ curl -X GET http://
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
@@ -78531,30 +81308,34 @@ $ curl -X GET http://
-Watch List
+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 DaemonSet
HTTP Request
@@ -78613,7 +81394,7 @@ $ curl -X GET http://
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
@@ -78636,30 +81417,34 @@ $ curl -X GET http://
-Watch List All Namespaces
+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 DaemonSet
HTTP Request
@@ -78703,7 +81488,7 @@ $ curl -X GET http://
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
@@ -78726,32 +81511,36 @@ $ curl -X GET http://
-Status Operations
+Status Operations
See supported operations below...
-Patch Status
+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 DaemonSet
HTTP Request
@@ -78820,30 +81609,34 @@ $ curl -X GET http://
-Read Status
+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 DaemonSet
HTTP Request
@@ -78897,30 +81690,34 @@ $ curl -X GET http://
-Replace Status
+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 DaemonSet
HTTP Request
@@ -79201,9 +81998,9 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
@@ -79231,6 +82028,7 @@ spec:
sleep 10 ;
done
' | kubectl create -f -
+
curl Command (requires kubectl proxy to be running )
@@ -79261,12 +82059,14 @@ spec:
sleep 10 ;
done
' http://127.0 .0.1:8001 /apis/extensions/v1beta1/namespaces/default/daemonsets
+
Output
daemonset "daemonset-example" created
+
Response Body
@@ -79330,6 +82130,7 @@ spec:
"desiredNumberScheduled" : 0
}
}
+
create a DaemonSet
HTTP Request
@@ -79402,30 +82203,34 @@ spec:
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified DaemonSet
HTTP Request
@@ -79494,30 +82299,34 @@ spec:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified DaemonSet
HTTP Request
@@ -79581,21 +82390,22 @@ spec:
-201 DaemonSet
-Created
-
-
200 DaemonSet
OK
+
+201 DaemonSet
+Created
+
-Delete
+Delete
kubectl Command
$ kubectl delete daemonset daemonset-example
+
curl Command (requires kubectl proxy to be running )
@@ -79605,13 +82415,15 @@ $ kubectl proxy
$ curl -X DELETE -H 'Content-Type: application/yaml'
gracePeriodSeconds: 0
orphanDependents: false
-' ' http ://127.0 .0 .1 :8001 /apis/extensions/v1beta1/namespaces/default /daemonsets/daemonset-example'
+' ' http ://127.0 .0 .1 :8001 /apis/extensions/v1beta1/namespaces/default /daemonsets/daemonset-example'
+
Output
daemonset "daemonset-example" deleted
+
Response Body
@@ -79624,6 +82436,8 @@ orphanDependents: false
"status" : "Success" ,
"code" : 200
}
+
+
delete a DaemonSet
HTTP Request
@@ -79704,30 +82518,34 @@ orphanDependents: false
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of DaemonSet
HTTP Request
@@ -79786,7 +82604,7 @@ orphanDependents: false
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
@@ -79809,31 +82627,37 @@ orphanDependents: false
-Read Operations
+Read Operations
See supported operations below...
-Read
+Read
kubectl Command
$ 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/ extensions/v1beta1/ namespaces/default/ daemonsets/daemonset-example
+$ kubectl proxy
+$ curl -X GET http: //127.0.0.1:8001/apis /extensions/v 1beta1/namespaces/default/daemonsets/daemonset-example
+
Output
+
+
Response Body
+
+
read the specified DaemonSet
HTTP Request
@@ -79895,30 +82719,34 @@ $ curl -X GET http://
-List
+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 DaemonSet
HTTP Request
@@ -79977,7 +82805,7 @@ $ curl -X GET http://
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
@@ -80000,30 +82828,34 @@ $ curl -X GET http://
-List All Namespaces
+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 DaemonSet
HTTP Request
@@ -80067,7 +82899,7 @@ $ curl -X GET http://
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
@@ -80090,30 +82922,34 @@ $ curl -X GET http://
-Watch
+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 DaemonSet
HTTP Request
@@ -80176,7 +83012,7 @@ $ curl -X GET http://
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
@@ -80199,30 +83035,34 @@ $ curl -X GET http://
-Watch List
+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 DaemonSet
HTTP Request
@@ -80281,7 +83121,7 @@ $ curl -X GET http://
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
@@ -80304,30 +83144,34 @@ $ curl -X GET http://
-Watch List All Namespaces
+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 DaemonSet
HTTP Request
@@ -80371,7 +83215,7 @@ $ curl -X GET http://
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
@@ -80394,32 +83238,36 @@ $ curl -X GET http://
-Status Operations
+Status Operations
See supported operations below...
-Patch Status
+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 DaemonSet
HTTP Request
@@ -80488,30 +83336,34 @@ $ curl -X GET http://
-Read Status
+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 DaemonSet
HTTP Request
@@ -80565,30 +83417,34 @@ $ curl -X GET http://
-Replace Status
+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 DaemonSet
HTTP Request
@@ -81112,9 +83968,9 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
@@ -81137,6 +83993,7 @@ spec:
ports:
- containerPort: 80
' | kubectl create -f -
+
curl Command (requires kubectl proxy to be running )
@@ -81162,12 +84019,14 @@ spec:
ports:
- containerPort: 80
' http: //127.0.0.1:8001/apis /apps/v 1beta2/namespaces/default/deployments
+
Output
deployment "deployment-example" created
+
Response Body
@@ -81235,6 +84094,7 @@ spec:
},
"status" : {}
}
+
create a Deployment
HTTP Request
@@ -81294,6 +84154,10 @@ spec:
+202 Deployment
+Accepted
+
+
200 Deployment
OK
@@ -81301,19 +84165,16 @@ spec:
201 Deployment
Created
-
-202 Deployment
-Accepted
-
-Patch
+Patch
kubectl Command
$ kubectl patch deployment deployment-example -p \
'{"spec" :{"template" :{"spec" :{"containers" :[{"name" :"nginx" ,"image" :"nginx:1.11" }]}}}}'
+
curl Command (requires kubectl proxy to be running )
@@ -81322,13 +84183,15 @@ $ kubectl patch deployment deployment-example
$ kubectl proxy
$ curl -X PATCH -H 'Content-Type: application/strategic-merge -patch +json ' --data '
{"spec" :{"template" :{"spec" :{"containers" :[{"name" :"nginx" ,"image" :"nginx:1.11" }]}}}}' \
- ' http ://127.0 .0 .1 :8001 /apis/apps/v1beta2/namespaces/default /deployments/deployment-example'
+ ' http ://127.0 .0 .1 :8001 /apis/apps/v1beta2/namespaces/default /deployments/deployment-example'
+
Output
"deployment-example" patched
+
Response Body
@@ -81404,6 +84267,8 @@ $ curl -X PATCH -H 'Content-Type: application/strategic-"availableReplicas" : 3
}
}
+
+
partially update the specified Deployment
HTTP Request
@@ -81472,7 +84337,7 @@ $ curl -X PATCH -H 'Content-Type: application/strategic-Replace
+Replace
kubectl Command
@@ -81495,6 +84360,7 @@ spec:
ports:
- containerPort: 80
' | kubectl replace -f -
+
curl Command (requires kubectl proxy to be running )
@@ -81520,12 +84386,14 @@ spec:
ports:
- containerPort: 80
' http: //127.0.0.1:8001/apis /apps/v 1beta2/namespaces/default/deployments/deployment-example
+
Output
deployment "deployment-example" replaced
+
Response Body
@@ -81598,6 +84466,8 @@ spec:
"availableReplicas" : 3
}
}
+
+
replace the specified Deployment
HTTP Request
@@ -81670,12 +84540,13 @@ spec:
-Delete
+Delete
kubectl Command
$ kubectl delete deployment deployment-example
+
curl Command (requires kubectl proxy to be running )
@@ -81685,13 +84556,15 @@ $ kubectl proxy
$ curl -X DELETE -H 'Content-Type: application/yaml'
gracePeriodSeconds: 0
orphanDependents: false
-' ' http ://127.0 .0 .1 :8001 /apis/apps/v1beta2/namespaces/default /deployments/deployment-example'
+' ' http ://127.0 .0 .1 :8001 /apis/apps/v1beta2/namespaces/default /deployments/deployment-example'
+
Output
deployment "deployment-example" deleted
+
Response Body
@@ -81704,6 +84577,8 @@ orphanDependents: false
"status" : "Success" ,
"code" : 200
}
+
+
delete a Deployment
HTTP Request
@@ -81784,30 +84659,34 @@ orphanDependents: false
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of Deployment
HTTP Request
@@ -81866,7 +84745,7 @@ orphanDependents: false
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
@@ -81889,21 +84768,23 @@ orphanDependents: false
-Read Operations
+Read Operations
See supported operations below...
-Read
+Read
kubectl Command
$ kubectl get deployment deployment-example -o json
+
curl Command (requires kubectl proxy to be running )
-$ kubectl proxy
-$ curl -X GET http:// 127.0 .0.1 :8001 /apis/ apps/v1beta2/ namespaces/default/ deployments/deployment-example
+$ kubectl proxy
+$ curl -X GET http: //127.0.0.1:8001/apis /apps/v 1beta2/namespaces/default/deployments/deployment-example
+
Output
@@ -81978,6 +84859,8 @@ $ curl -X GET http://
"availableReplicas" : 3
}
}
+
+
Response Body
@@ -82052,6 +84935,8 @@ $ curl -X GET http://
"availableReplicas" : 3
}
}
+
+
read the specified Deployment
HTTP Request
@@ -82113,12 +84998,13 @@ $ curl -X GET http://
-List
+List
kubectl Command
$ kubectl get deployment -o json
+
curl Command (requires kubectl proxy to be running )
@@ -82126,6 +85012,7 @@ $ kubectl get deployment -o json
$ kubectl proxy
$ curl -X GET 'http://127.0.0.1:8001/apis/apps/v1beta2/namespaces/default/deployments'
+
Output
@@ -82272,6 +85159,8 @@ $ kubectl proxy
}
]
}
+
+
Response Body
@@ -82418,6 +85307,8 @@ $ kubectl proxy
}
]
}
+
+
list or watch objects of kind Deployment
HTTP Request
@@ -82476,7 +85367,7 @@ $ kubectl proxy
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
@@ -82499,30 +85390,34 @@ $ kubectl proxy
-List All Namespaces
+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 Deployment
HTTP Request
@@ -82566,7 +85461,7 @@ $ kubectl proxy
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
@@ -82589,12 +85484,13 @@ $ kubectl proxy
-Watch
+Watch
kubectl Command
$ kubectl get deployment deployment-example
+
curl Command (requires kubectl proxy to be running )
@@ -82602,6 +85498,7 @@ $ kubectl get deployment deployment-example
$ kubectl proxy
$ curl -X GET 'http://127.0.0.1:8001/apis/apps/v1beta2/watch/namespaces/default/deployments/deployment-example'
+
Output
@@ -82681,6 +85578,7 @@ $ kubectl proxy
}
}
}
+
Response Body
@@ -82760,6 +85658,7 @@ $ kubectl proxy
}
}
}
+
watch changes to an object of kind Deployment
HTTP Request
@@ -82822,7 +85721,7 @@ $ kubectl proxy
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
@@ -82845,30 +85744,34 @@ $ kubectl proxy
-Watch List
+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 Deployment
HTTP Request
@@ -82927,7 +85830,7 @@ $ kubectl proxy
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
@@ -82950,30 +85853,34 @@ $ kubectl proxy
-Watch List All Namespaces
+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 Deployment
HTTP Request
@@ -83017,7 +85924,7 @@ $ kubectl proxy
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
@@ -83040,32 +85947,36 @@ $ kubectl proxy
-Status Operations
+Status Operations
See supported operations below...
-Patch Status
+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 Deployment
HTTP Request
@@ -83134,30 +86045,34 @@ $ kubectl proxy
-Read Status
+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 Deployment
HTTP Request
@@ -83211,30 +86126,34 @@ $ kubectl proxy
-Replace Status
+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 Deployment
HTTP Request
@@ -83298,41 +86217,45 @@ $ kubectl proxy
-200 Deployment
-OK
-
-
201 Deployment
Created
+
+200 Deployment
+OK
+
-Misc Operations
+Misc Operations
See supported operations below...
-Read Scale
+Read Scale
kubectl Command
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
@@ -83386,30 +86309,34 @@ $ kubectl proxy
-Replace Scale
+Replace Scale
kubectl Command
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
@@ -83473,39 +86400,43 @@ $ kubectl proxy
-201 Scale
-Created
-
-
200 Scale
OK
+
+201 Scale
+Created
+
-Patch Scale
+Patch Scale
kubectl Command
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
@@ -83847,9 +86778,9 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
@@ -83872,6 +86803,7 @@ spec:
ports:
- containerPort: 80
' | kubectl create -f -
+
curl Command (requires kubectl proxy to be running )
@@ -83897,12 +86829,14 @@ spec:
ports:
- containerPort: 80
' http: //127.0.0.1:8001/apis /apps/v 1beta1/namespaces/default/deployments
+
Output
deployment "deployment-example" created
+
Response Body
@@ -83970,6 +86904,7 @@ spec:
},
"status" : {}
}
+
create a Deployment
HTTP Request
@@ -84042,13 +86977,14 @@ spec:
-Patch
+Patch
kubectl Command
$ kubectl patch deployment deployment-example -p \
'{"spec" :{"template" :{"spec" :{"containers" :[{"name" :"nginx" ,"image" :"nginx:1.11" }]}}}}'
+
curl Command (requires kubectl proxy to be running )
@@ -84057,13 +86993,15 @@ $ kubectl patch deployment deployment-example
$ kubectl proxy
$ curl -X PATCH -H 'Content-Type: application/strategic-merge -patch +json ' --data '
{"spec" :{"template" :{"spec" :{"containers" :[{"name" :"nginx" ,"image" :"nginx:1.11" }]}}}}' \
- ' http ://127.0 .0 .1 :8001 /apis/apps/v1beta1/namespaces/default /deployments/deployment-example'
+ ' http ://127.0 .0 .1 :8001 /apis/apps/v1beta1/namespaces/default /deployments/deployment-example'
+
Output
"deployment-example" patched
+
Response Body
@@ -84139,6 +87077,8 @@ $ curl -X PATCH -H 'Content-Type: application/strategic-"availableReplicas" : 3
}
}
+
+
partially update the specified Deployment
HTTP Request
@@ -84207,7 +87147,7 @@ $ curl -X PATCH -H 'Content-Type: application/strategic-Replace
+Replace
kubectl Command
@@ -84230,6 +87170,7 @@ spec:
ports:
- containerPort: 80
' | kubectl replace -f -
+
curl Command (requires kubectl proxy to be running )
@@ -84255,12 +87196,14 @@ spec:
ports:
- containerPort: 80
' http: //127.0.0.1:8001/apis /apps/v 1beta1/namespaces/default/deployments/deployment-example
+
Output
deployment "deployment-example" replaced
+
Response Body
@@ -84333,6 +87276,8 @@ spec:
"availableReplicas" : 3
}
}
+
+
replace the specified Deployment
HTTP Request
@@ -84405,12 +87350,13 @@ spec:
-Delete
+Delete
kubectl Command
$ kubectl delete deployment deployment-example
+
curl Command (requires kubectl proxy to be running )
@@ -84420,13 +87366,15 @@ $ kubectl proxy
$ curl -X DELETE -H 'Content-Type: application/yaml'
gracePeriodSeconds: 0
orphanDependents: false
-' ' http ://127.0 .0 .1 :8001 /apis/apps/v1beta1/namespaces/default /deployments/deployment-example'
+' ' http ://127.0 .0 .1 :8001 /apis/apps/v1beta1/namespaces/default /deployments/deployment-example'
+
Output
deployment "deployment-example" deleted
+
Response Body
@@ -84439,6 +87387,8 @@ orphanDependents: false
"status" : "Success" ,
"code" : 200
}
+
+
delete a Deployment
HTTP Request
@@ -84519,30 +87469,34 @@ orphanDependents: false
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of Deployment
HTTP Request
@@ -84601,7 +87555,7 @@ orphanDependents: false
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
@@ -84624,21 +87578,23 @@ orphanDependents: false
-Read Operations
+Read Operations
See supported operations below...
-Read
+Read
kubectl Command
$ kubectl get deployment deployment-example -o json
+
curl Command (requires kubectl proxy to be running )
-$ kubectl proxy
-$ curl -X GET http:// 127.0 .0.1 :8001 /apis/ apps/v1beta1/ namespaces/default/ deployments/deployment-example
+$ kubectl proxy
+$ curl -X GET http: //127.0.0.1:8001/apis /apps/v 1beta1/namespaces/default/deployments/deployment-example
+
Output
@@ -84713,6 +87669,8 @@ $ curl -X GET http://
"availableReplicas" : 3
}
}
+
+
Response Body
@@ -84787,6 +87745,8 @@ $ curl -X GET http://
"availableReplicas" : 3
}
}
+
+
read the specified Deployment
HTTP Request
@@ -84848,12 +87808,13 @@ $ curl -X GET http://
-List
+List
kubectl Command
$ kubectl get deployment -o json
+
curl Command (requires kubectl proxy to be running )
@@ -84861,6 +87822,7 @@ $ kubectl get deployment -o json
$ kubectl proxy
$ curl -X GET 'http://127.0.0.1:8001/apis/apps/v1beta1/namespaces/default/deployments'
+
Output
@@ -85007,6 +87969,8 @@ $ kubectl proxy
}
]
}
+
+
Response Body
@@ -85153,6 +88117,8 @@ $ kubectl proxy
}
]
}
+
+
list or watch objects of kind Deployment
HTTP Request
@@ -85211,7 +88177,7 @@ $ kubectl proxy
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
@@ -85234,30 +88200,34 @@ $ kubectl proxy
-List All Namespaces
+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 Deployment
HTTP Request
@@ -85301,7 +88271,7 @@ $ kubectl proxy
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
@@ -85324,12 +88294,13 @@ $ kubectl proxy
-Watch
+Watch
kubectl Command
$ kubectl get deployment deployment-example
+
curl Command (requires kubectl proxy to be running )
@@ -85337,6 +88308,7 @@ $ kubectl get deployment deployment-example
$ kubectl proxy
$ curl -X GET 'http://127.0.0.1:8001/apis/apps/v1beta1/watch/namespaces/default/deployments/deployment-example'
+
Output
@@ -85416,6 +88388,7 @@ $ kubectl proxy
}
}
}
+
Response Body
@@ -85495,6 +88468,7 @@ $ kubectl proxy
}
}
}
+
watch changes to an object of kind Deployment
HTTP Request
@@ -85557,7 +88531,7 @@ $ kubectl proxy
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
@@ -85580,30 +88554,34 @@ $ kubectl proxy
-Watch List
+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 Deployment
HTTP Request
@@ -85662,7 +88640,7 @@ $ kubectl proxy
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
@@ -85685,30 +88663,34 @@ $ kubectl proxy
-Watch List All Namespaces
+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 Deployment
HTTP Request
@@ -85752,7 +88734,7 @@ $ kubectl proxy
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
@@ -85775,32 +88757,36 @@ $ kubectl proxy
-Status Operations
+Status Operations
See supported operations below...
-Patch Status
+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 Deployment
HTTP Request
@@ -85869,30 +88855,34 @@ $ kubectl proxy
-Read Status
+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 Deployment
HTTP Request
@@ -85946,30 +88936,34 @@ $ kubectl proxy
-Replace Status
+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 Deployment
HTTP Request
@@ -86042,32 +89036,36 @@ $ kubectl proxy
-Misc Operations
+Misc Operations
See supported operations below...
-Read Scale
+Read Scale
kubectl Command
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
@@ -86121,30 +89119,34 @@ $ kubectl proxy
-Replace Scale
+Replace Scale
kubectl Command
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
@@ -86217,30 +89219,34 @@ $ kubectl proxy
-Patch Scale
+Patch Scale
kubectl Command
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
@@ -86315,24 +89321,28 @@ $ kubectl proxy
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create rollback of a Deployment
HTTP Request
@@ -86682,9 +89692,9 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
@@ -86707,6 +89717,7 @@ spec:
ports:
- containerPort: 80
' | kubectl create -f -
+
curl Command (requires kubectl proxy to be running )
@@ -86732,12 +89743,14 @@ spec:
ports:
- containerPort: 80
' http: //127.0.0.1:8001/apis /extensions/v 1beta1/namespaces/default/deployments
+
Output
deployment "deployment-example" created
+
Response Body
@@ -86805,6 +89818,7 @@ spec:
},
"status" : {}
}
+
create a Deployment
HTTP Request
@@ -86864,6 +89878,10 @@ spec:
+202 Deployment
+Accepted
+
+
200 Deployment
OK
@@ -86871,19 +89889,16 @@ spec:
201 Deployment
Created
-
-202 Deployment
-Accepted
-
-Patch
+Patch
kubectl Command
$ kubectl patch deployment deployment-example -p \
'{"spec" :{"template" :{"spec" :{"containers" :[{"name" :"nginx" ,"image" :"nginx:1.11" }]}}}}'
+
curl Command (requires kubectl proxy to be running )
@@ -86892,13 +89907,15 @@ $ kubectl patch deployment deployment-example
$ kubectl proxy
$ curl -X PATCH -H 'Content-Type: application/strategic-merge -patch +json ' --data '
{"spec" :{"template" :{"spec" :{"containers" :[{"name" :"nginx" ,"image" :"nginx:1.11" }]}}}}' \
- ' http ://127.0 .0 .1 :8001 /apis/extensions/v1beta1/namespaces/default /deployments/deployment-example'
+ 'http ://127.0 .0 .1 :8001 /apis/extensions/v1beta1/namespaces/default /deployments/deployment-example'
+
Output
"deployment-example" patched
+
Response Body
@@ -86974,6 +89991,8 @@ $ curl -X PATCH -H 'Content-Type: application/strategic-"availableReplicas" : 3
}
}
+
+
partially update the specified Deployment
HTTP Request
@@ -87042,7 +90061,7 @@ $ curl -X PATCH -H 'Content-Type: application/strategic-Replace
+Replace
kubectl Command
@@ -87065,6 +90084,7 @@ spec:
ports:
- containerPort: 80
' | kubectl replace -f -
+
curl Command (requires kubectl proxy to be running )
@@ -87090,12 +90110,14 @@ spec:
ports:
- containerPort: 80
' http: //127.0.0.1:8001/apis /extensions/v 1beta1/namespaces/default/deployments/deployment-example
+
Output
deployment "deployment-example" replaced
+
Response Body
@@ -87168,6 +90190,8 @@ spec:
"availableReplicas" : 3
}
}
+
+
replace the specified Deployment
HTTP Request
@@ -87231,21 +90255,22 @@ spec:
-201 Deployment
-Created
-
-
200 Deployment
OK
+
+201 Deployment
+Created
+
-Delete
+Delete
kubectl Command
$ kubectl delete deployment deployment-example
+
curl Command (requires kubectl proxy to be running )
@@ -87255,13 +90280,15 @@ $ kubectl proxy
$ curl -X DELETE -H 'Content-Type: application/yaml'
gracePeriodSeconds: 0
orphanDependents: false
-' ' http ://127.0 .0 .1 :8001 /apis/extensions/v1beta1/namespaces/default /deployments/deployment-example'
+' ' http ://127.0 .0 .1 :8001 /apis/extensions/v1beta1/namespaces/default /deployments/deployment-example'
+
Output
deployment "deployment-example" deleted
+
Response Body
@@ -87274,6 +90301,8 @@ orphanDependents: false
"status" : "Success" ,
"code" : 200
}
+
+
delete a Deployment
HTTP Request
@@ -87354,30 +90383,34 @@ orphanDependents: false
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of Deployment
HTTP Request
@@ -87436,7 +90469,7 @@ orphanDependents: false
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
@@ -87459,21 +90492,23 @@ orphanDependents: false
-Read Operations
+Read Operations
See supported operations below...
-Read
+Read
kubectl Command
$ kubectl get deployment deployment-example -o json
+
curl Command (requires kubectl proxy to be running )
-$ kubectl proxy
-$ curl -X GET http:// 127.0 .0.1 :8001 /apis/ extensions/v1beta1/ namespaces/default/ deployments/deployment-example
+$ kubectl proxy
+$ curl -X GET http: //127.0.0.1:8001/apis /extensions/v 1beta1/namespaces/default/deployments/deployment-example
+
Output
@@ -87548,6 +90583,8 @@ $ curl -X GET http://
"availableReplicas" : 3
}
}
+
+
Response Body
@@ -87622,6 +90659,8 @@ $ curl -X GET http://
"availableReplicas" : 3
}
}
+
+
read the specified Deployment
HTTP Request
@@ -87683,12 +90722,13 @@ $ curl -X GET http://
-List
+List
kubectl Command
$ kubectl get deployment -o json
+
curl Command (requires kubectl proxy to be running )
@@ -87696,6 +90736,7 @@ $ kubectl get deployment -o json
$ kubectl proxy
$ curl -X GET 'http://127.0.0.1:8001/apis/extensions/v1beta1/namespaces/default/deployments'
+
Output
@@ -87842,6 +90883,8 @@ $ kubectl proxy
}
]
}
+
+
Response Body
@@ -87988,6 +91031,8 @@ $ kubectl proxy
}
]
}
+
+
list or watch objects of kind Deployment
HTTP Request
@@ -88046,7 +91091,7 @@ $ kubectl proxy
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
@@ -88069,30 +91114,34 @@ $ kubectl proxy
-List All Namespaces
+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 Deployment
HTTP Request
@@ -88136,7 +91185,7 @@ $ kubectl proxy
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
@@ -88159,12 +91208,13 @@ $ kubectl proxy
-Watch
+Watch
kubectl Command
$ kubectl get deployment deployment-example
+
curl Command (requires kubectl proxy to be running )
@@ -88172,6 +91222,7 @@ $ kubectl get deployment deployment-example
$ kubectl proxy
$ curl -X GET 'http://127.0.0.1:8001/apis/extensions/v1beta1/watch/namespaces/default/deployments/deployment-example'
+
Output
@@ -88251,6 +91302,7 @@ $ kubectl proxy
}
}
}
+
Response Body
@@ -88330,6 +91382,7 @@ $ kubectl proxy
}
}
}
+
watch changes to an object of kind Deployment
HTTP Request
@@ -88392,7 +91445,7 @@ $ kubectl proxy
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
@@ -88415,30 +91468,34 @@ $ kubectl proxy
-Watch List
+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 Deployment
HTTP Request
@@ -88497,7 +91554,7 @@ $ kubectl proxy
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
@@ -88520,30 +91577,34 @@ $ kubectl proxy
-Watch List All Namespaces
+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 Deployment
HTTP Request
@@ -88587,7 +91648,7 @@ $ kubectl proxy
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
@@ -88610,32 +91671,36 @@ $ kubectl proxy
-Status Operations
+Status Operations
See supported operations below...
-Patch Status
+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 Deployment
HTTP Request
@@ -88704,30 +91769,34 @@ $ kubectl proxy
-Read Status
+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 Deployment
HTTP Request
@@ -88781,30 +91850,34 @@ $ kubectl proxy
-Replace Status
+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 Deployment
HTTP Request
@@ -88877,32 +91950,36 @@ $ kubectl proxy
-Misc Operations
+Misc Operations
See supported operations below...
-Read Scale
+Read Scale
kubectl Command
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
@@ -88956,30 +92033,34 @@ $ kubectl proxy
-Replace Scale
+Replace Scale
kubectl Command
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
@@ -89043,39 +92124,43 @@ $ kubectl proxy
-200 Scale
-OK
-
-
201 Scale
Created
+
+200 Scale
+OK
+
-Patch Scale
+Patch Scale
kubectl Command
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
@@ -89144,30 +92229,34 @@ $ kubectl proxy
-Rollback
+Rollback
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create rollback of a Deployment
HTTP Request
@@ -89567,32 +92656,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create an Event
HTTP Request
@@ -89652,10 +92745,6 @@ Appears In:
-202 Event
-Accepted
-
-
200 Event
OK
@@ -89663,32 +92752,40 @@ Appears In:
201 Event
Created
+
+202 Event
+Accepted
+
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified Event
HTTP Request
@@ -89757,30 +92854,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified Event
HTTP Request
@@ -89844,39 +92945,43 @@ Appears In:
-200 Event
-OK
-
-
201 Event
Created
+
+200 Event
+OK
+
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete an Event
HTTP Request
@@ -89957,30 +93062,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of Event
HTTP Request
@@ -90039,7 +93148,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
@@ -90062,32 +93171,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 Event
HTTP Request
@@ -90149,30 +93262,34 @@ Appears In:
-List
+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 Event
HTTP Request
@@ -90231,7 +93348,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
@@ -90254,30 +93371,34 @@ Appears In:
-List All Namespaces
+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 Event
HTTP Request
@@ -90321,7 +93442,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
@@ -90344,30 +93465,34 @@ Appears In:
-Watch
+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 Event
HTTP Request
@@ -90430,7 +93555,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
@@ -90453,30 +93578,34 @@ Appears In:
-Watch List
+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 Event
HTTP Request
@@ -90535,7 +93664,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
@@ -90558,30 +93687,34 @@ Appears In:
-Watch List All Namespaces
+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 Event
HTTP Request
@@ -90625,7 +93758,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
@@ -90700,6 +93833,50 @@ Appears In:
+FSGroupStrategyOptions v1beta1 policy
+
+
+
+Group
+Version
+Kind
+
+
+
+
+policy
+v1beta1
+FSGroupStrategyOptions
+
+
+
+FSGroupStrategyOptions defines the strategy type and options used to create the strategy.
+
+
+
+
+
+Field
+Description
+
+
+
+
+ranges IDRange array
+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.
+
+
+rule string
+Rule is the strategy that will dictate what FSGroup is used in the SecurityContext.
+
+
+
+
HorizontalPodAutoscaler v2beta1 autoscaling
@@ -90861,32 +94038,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a HorizontalPodAutoscaler
HTTP Request
@@ -90959,30 +94140,34 @@ Appears In:
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified HorizontalPodAutoscaler
HTTP Request
@@ -91051,30 +94236,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified HorizontalPodAutoscaler
HTTP Request
@@ -91147,30 +94336,34 @@ Appears In:
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a HorizontalPodAutoscaler
HTTP Request
@@ -91251,30 +94444,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of HorizontalPodAutoscaler
HTTP Request
@@ -91333,7 +94530,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
@@ -91356,32 +94553,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 HorizontalPodAutoscaler
HTTP Request
@@ -91443,30 +94644,34 @@ Appears In:
-List
+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 HorizontalPodAutoscaler
HTTP Request
@@ -91525,7 +94730,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
@@ -91548,30 +94753,34 @@ Appears In:
-List All Namespaces
+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 HorizontalPodAutoscaler
HTTP Request
@@ -91615,7 +94824,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
@@ -91638,30 +94847,34 @@ Appears In:
-Watch
+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 HorizontalPodAutoscaler
HTTP Request
@@ -91724,7 +94937,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
@@ -91747,30 +94960,34 @@ Appears In:
-Watch List
+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 HorizontalPodAutoscaler
HTTP Request
@@ -91829,7 +95046,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
@@ -91852,30 +95069,34 @@ Appears In:
-Watch List All Namespaces
+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 HorizontalPodAutoscaler
HTTP Request
@@ -91919,7 +95140,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
@@ -91942,32 +95163,36 @@ Appears In:
-Status Operations
+Status Operations
See supported operations below...
-Patch Status
+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 HorizontalPodAutoscaler
HTTP Request
@@ -92036,30 +95261,34 @@ Appears In:
-Read Status
+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 HorizontalPodAutoscaler
HTTP Request
@@ -92113,30 +95342,34 @@ Appears In:
-Replace Status
+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 HorizontalPodAutoscaler
HTTP Request
@@ -92200,12 +95433,102 @@ Appears In:
+201 HorizontalPodAutoscaler
+Created
+
+
200 HorizontalPodAutoscaler
OK
+
+
+
+HostPortRange v1beta1 policy
+
+Host Port Range defines a range of host ports that will be enabled by a policy for pods to use. It requires both the start and end to be defined.
+
+
+
+
+
+Field
+Description
+
+
+
+
+max integer
+max is the end of the range, inclusive.
+
+
+min integer
+min is the start of the range, inclusive.
+
+
+
+
+IDRange v1beta1 policy
+
+
+
+Group
+Version
+Kind
+
+
+
+
+policy
+v1beta1
+IDRange
+
+
+
+ID Range provides a min/max of an allowed range of IDs.
+
+
+
+
+
+Field
+Description
+
+
+
+
+max integer
+Max is the end of the range, inclusive.
+
+
+min integer
+Min is the start of the range, inclusive.
@@ -92402,32 +95725,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a LocalSubjectAccessReview
HTTP Request
@@ -92487,6 +95814,10 @@ Appears In:
+200 LocalSubjectAccessReview
+OK
+
+
201 LocalSubjectAccessReview
Created
@@ -92494,10 +95825,6 @@ Appears In:
202 LocalSubjectAccessReview
Accepted
-
-200 LocalSubjectAccessReview
-OK
-
@@ -92616,32 +95943,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a NetworkPolicy
HTTP Request
@@ -92701,6 +96032,10 @@ Appears In:
+200 NetworkPolicy
+OK
+
+
201 NetworkPolicy
Created
@@ -92708,36 +96043,36 @@ Appears In:
202 NetworkPolicy
Accepted
-
-200 NetworkPolicy
-OK
-
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified NetworkPolicy
HTTP Request
@@ -92806,30 +96141,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified NetworkPolicy
HTTP Request
@@ -92902,30 +96241,34 @@ Appears In:
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a NetworkPolicy
HTTP Request
@@ -93006,30 +96349,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of NetworkPolicy
HTTP Request
@@ -93088,7 +96435,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
@@ -93111,32 +96458,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 NetworkPolicy
HTTP Request
@@ -93198,30 +96549,34 @@ Appears In:
-List
+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 NetworkPolicy
HTTP Request
@@ -93280,7 +96635,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
@@ -93303,30 +96658,34 @@ Appears In:
-List All Namespaces
+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 NetworkPolicy
HTTP Request
@@ -93370,7 +96729,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
@@ -93393,30 +96752,34 @@ Appears In:
-Watch
+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
@@ -93479,7 +96842,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
@@ -93502,30 +96865,34 @@ Appears In:
-Watch List
+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 NetworkPolicy
HTTP Request
@@ -93584,7 +96951,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
@@ -93607,30 +96974,34 @@ Appears In:
-Watch List All Namespaces
+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
@@ -93674,7 +97045,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
@@ -93987,6 +97358,1032 @@ Appears In:
+PodSecurityPolicy v1beta1 policy
+
+
+
+Group
+Version
+Kind
+
+
+
+
+policy
+v1beta1
+PodSecurityPolicy
+
+
+
+Pod Security Policy governs the ability to make requests that affect the Security Context that will be applied to a pod and container.
+
+
+
+PodSecurityPolicySpec v1beta1 policy
+
+
+
+
+
+Field
+Description
+
+
+
+
+allowPrivilegeEscalation boolean
+AllowPrivilegeEscalation determines if a pod can request to allow privilege escalation. If unspecified, defaults to true.
+
+
+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.
+
+
+allowedFlexVolumes AllowedFlexVolume array
+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.
+
+
+allowedHostPaths AllowedHostPath array
+is a white list of allowed host paths. Empty indicates that all host paths may be used.
+
+
+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.
+
+
+defaultAllowPrivilegeEscalation boolean
+DefaultAllowPrivilegeEscalation controls the default setting for whether a process can gain more privileges than its parent process.
+
+
+fsGroup FSGroupStrategyOptions
+FSGroup is the strategy that will dictate what fs group is used by the SecurityContext.
+
+
+hostIPC boolean
+hostIPC determines if the policy allows the use of HostIPC in the pod spec.
+
+
+hostNetwork boolean
+hostNetwork determines if the policy allows the use of HostNetwork in the pod spec.
+
+
+hostPID boolean
+hostPID determines if the policy allows the use of HostPID in the pod spec.
+
+
+hostPorts HostPortRange array
+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.
+
+
+runAsUser RunAsUserStrategyOptions
+runAsUser is the strategy that will dictate the allowable RunAsUser values that may be set.
+
+
+seLinux SELinuxStrategyOptions
+seLinux is the strategy that will dictate the allowable labels that may be set.
+
+
+supplementalGroups SupplementalGroupsStrategyOptions
+SupplementalGroups is the strategy that will dictate what supplemental groups are used by the SecurityContext.
+
+
+volumes string array
+volumes is a white list of allowed volume plugins. Empty indicates that all plugins may be used.
+
+
+
+PodSecurityPolicyList v1beta1 policy
+
+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 PodSecurityPolicy
+HTTP Request
+POST /apis/policy/v1beta1/podsecuritypolicies
+Query Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+pretty
+If 'true', then the output is pretty printed.
+
+
+
+Body Parameters
+
+Response
+
+Patch
+
+ kubectl Command
+
+
+Coming Soon
+
+
+
+ curl Command (requires kubectl proxy to be running )
+
+
+Coming Soon
+
+
+
+ Output
+
+
+Coming Soon
+
+
+
+ Response Body
+
+
+Coming Soon
+
+
+partially update the specified PodSecurityPolicy
+HTTP Request
+PATCH /apis/policy/v1beta1/podsecuritypolicies/{name}
+Path Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+name
+name of the PodSecurityPolicy
+
+
+
+Query Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+pretty
+If 'true', then the output is pretty printed.
+
+
+
+Body Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+body Patch
+
+
+
+
+Response
+
+Replace
+
+ kubectl Command
+
+
+Coming Soon
+
+
+
+ curl Command (requires kubectl proxy to be running )
+
+
+Coming Soon
+
+
+
+ Output
+
+
+Coming Soon
+
+
+
+ Response Body
+
+
+Coming Soon
+
+
+replace the specified PodSecurityPolicy
+HTTP Request
+PUT /apis/policy/v1beta1/podsecuritypolicies/{name}
+Path Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+name
+name of the PodSecurityPolicy
+
+
+
+Query Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+pretty
+If 'true', then the output is pretty printed.
+
+
+
+Body Parameters
+
+Response
+
+Delete
+
+ kubectl Command
+
+
+Coming Soon
+
+
+
+ curl Command (requires kubectl proxy to be running )
+
+
+Coming Soon
+
+
+
+ Output
+
+
+Coming Soon
+
+
+
+ Response Body
+
+
+Coming Soon
+
+
+delete a PodSecurityPolicy
+HTTP Request
+DELETE /apis/policy/v1beta1/podsecuritypolicies/{name}
+Path Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+name
+name of the PodSecurityPolicy
+
+
+
+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.
+
+
+
+Body Parameters
+
+Response
+
+
+
+Code
+Description
+
+
+
+
+200 Status
+OK
+
+
+
+Delete Collection
+
+ kubectl Command
+
+
+Coming Soon
+
+
+
+ curl Command (requires kubectl proxy to be running )
+
+
+Coming Soon
+
+
+
+ Output
+
+
+Coming Soon
+
+
+
+ Response Body
+
+
+Coming Soon
+
+
+delete collection of PodSecurityPolicy
+HTTP Request
+DELETE /apis/policy/v1beta1/podsecuritypolicies
+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.
+
+
+
+Response
+
+
+
+Code
+Description
+
+
+
+
+200 Status
+OK
+
+
+
+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 PodSecurityPolicy
+HTTP Request
+GET /apis/policy/v1beta1/podsecuritypolicies/{name}
+Path Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+name
+name of the PodSecurityPolicy
+
+
+
+Query Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+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.
+
+
+
+Response
+
+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 PodSecurityPolicy
+HTTP Request
+GET /apis/policy/v1beta1/podsecuritypolicies
+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.
+
+
+
+Response
+
+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 PodSecurityPolicy
+HTTP Request
+GET /apis/policy/v1beta1/watch/podsecuritypolicies/{name}
+Path Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+name
+name of the PodSecurityPolicy
+
+
+
+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.
+
+
+
+Response
+
+
+
+Code
+Description
+
+
+
+
+200 WatchEvent
+OK
+
+
+
+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 PodSecurityPolicy
+HTTP Request
+GET /apis/policy/v1beta1/watch/podsecuritypolicies
+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.
+
+
+
+Response
+
+
+
+Code
+Description
+
+
+
+
+200 WatchEvent
+OK
+
+
+
+
PolicyRule v1beta1 rbac
@@ -94268,32 +98665,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a ReplicaSet
HTTP Request
@@ -94353,6 +98754,10 @@ Appears In:
+201 ReplicaSet
+Created
+
+
202 ReplicaSet
Accepted
@@ -94360,36 +98765,36 @@ Appears In:
200 ReplicaSet
OK
-
-201 ReplicaSet
-Created
-
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified ReplicaSet
HTTP Request
@@ -94458,30 +98863,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified ReplicaSet
HTTP Request
@@ -94554,30 +98963,34 @@ Appears In:
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a ReplicaSet
HTTP Request
@@ -94658,30 +99071,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of ReplicaSet
HTTP Request
@@ -94740,7 +99157,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
@@ -94763,32 +99180,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 ReplicaSet
HTTP Request
@@ -94850,30 +99271,34 @@ Appears In:
-List
+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 ReplicaSet
HTTP Request
@@ -94932,7 +99357,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
@@ -94955,30 +99380,34 @@ Appears In:
-List All Namespaces
+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
@@ -95022,7 +99451,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
@@ -95045,30 +99474,34 @@ Appears In:
-Watch
+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 ReplicaSet
HTTP Request
@@ -95131,7 +99564,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
@@ -95154,30 +99587,34 @@ Appears In:
-Watch List
+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 ReplicaSet
HTTP Request
@@ -95236,7 +99673,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
@@ -95259,30 +99696,34 @@ Appears In:
-Watch List All Namespaces
+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 ReplicaSet
HTTP Request
@@ -95326,7 +99767,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
@@ -95349,32 +99790,36 @@ Appears In:
-Status Operations
+Status Operations
See supported operations below...
-Patch Status
+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
HTTP Request
@@ -95443,30 +99888,34 @@ Appears In:
-Read Status
+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
@@ -95520,30 +99969,34 @@ Appears In:
-Replace Status
+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
@@ -95607,41 +100060,45 @@ Appears In:
-201 ReplicaSet
-Created
-
-
200 ReplicaSet
OK
+
+201 ReplicaSet
+Created
+
-Misc Operations
+Misc Operations
See supported operations below...
-Read Scale
+Read Scale
kubectl Command
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
@@ -95695,30 +100152,34 @@ Appears In:
-Replace Scale
+Replace Scale
kubectl Command
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
@@ -95791,30 +100252,34 @@ Appears In:
-Patch Scale
+Patch Scale
kubectl Command
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
@@ -96045,32 +100510,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a ReplicaSet
HTTP Request
@@ -96143,30 +100612,34 @@ Appears In:
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified ReplicaSet
HTTP Request
@@ -96235,30 +100708,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified ReplicaSet
HTTP Request
@@ -96331,30 +100808,34 @@ Appears In:
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a ReplicaSet
HTTP Request
@@ -96435,30 +100916,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of ReplicaSet
HTTP Request
@@ -96517,7 +101002,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
@@ -96540,32 +101025,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 ReplicaSet
HTTP Request
@@ -96627,30 +101116,34 @@ Appears In:
-List
+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 ReplicaSet
HTTP Request
@@ -96709,7 +101202,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
@@ -96732,30 +101225,34 @@ Appears In:
-List All Namespaces
+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
@@ -96799,7 +101296,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
@@ -96822,30 +101319,34 @@ Appears In:
-Watch
+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 ReplicaSet
HTTP Request
@@ -96908,7 +101409,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
@@ -96931,30 +101432,34 @@ Appears In:
-Watch List
+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 ReplicaSet
HTTP Request
@@ -97013,7 +101518,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
@@ -97036,30 +101541,34 @@ Appears In:
-Watch List All Namespaces
+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 ReplicaSet
HTTP Request
@@ -97103,7 +101612,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
@@ -97126,32 +101635,36 @@ Appears In:
-Status Operations
+Status Operations
See supported operations below...
-Patch Status
+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
HTTP Request
@@ -97220,30 +101733,34 @@ Appears In:
-Read Status
+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
@@ -97297,30 +101814,34 @@ Appears In:
-Replace Status
+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
@@ -97393,32 +101914,36 @@ Appears In:
-Misc Operations
+Misc Operations
See supported operations below...
-Read Scale
+Read Scale
kubectl Command
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
@@ -97472,30 +101997,34 @@ Appears In:
-Replace Scale
+Replace Scale
kubectl Command
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
@@ -97559,39 +102088,43 @@ Appears In:
-201 Scale
-Created
-
-
200 Scale
OK
+
+201 Scale
+Created
+
-Patch Scale
+Patch Scale
kubectl Command
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
@@ -97983,32 +102516,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a Role
HTTP Request
@@ -98068,10 +102605,6 @@ Appears In:
-200 Role
-OK
-
-
201 Role
Created
@@ -98079,32 +102612,40 @@ Appears In:
202 Role
Accepted
+
+200 Role
+OK
+
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified Role
HTTP Request
@@ -98173,30 +102714,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified Role
HTTP Request
@@ -98260,39 +102805,43 @@ Appears In:
-201 Role
-Created
-
-
200 Role
OK
+
+201 Role
+Created
+
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a Role
HTTP Request
@@ -98373,30 +102922,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of Role
HTTP Request
@@ -98455,7 +103008,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
@@ -98478,32 +103031,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 Role
HTTP Request
@@ -98557,30 +103114,34 @@ Appears In:
-List
+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 Role
HTTP Request
@@ -98639,7 +103200,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
@@ -98662,30 +103223,34 @@ Appears In:
-List All Namespaces
+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 Role
HTTP Request
@@ -98729,7 +103294,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
@@ -98752,30 +103317,34 @@ Appears In:
-Watch
+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 Role
HTTP Request
@@ -98838,7 +103407,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
@@ -98861,30 +103430,34 @@ Appears In:
-Watch List
+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 Role
HTTP Request
@@ -98943,7 +103516,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
@@ -98966,30 +103539,34 @@ Appears In:
-Watch List All Namespaces
+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 Role
HTTP Request
@@ -99033,7 +103610,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
@@ -99138,32 +103715,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a Role
HTTP Request
@@ -99236,30 +103817,34 @@ Appears In:
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified Role
HTTP Request
@@ -99328,30 +103913,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified Role
HTTP Request
@@ -99424,30 +104013,34 @@ Appears In:
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a Role
HTTP Request
@@ -99528,30 +104121,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of Role
HTTP Request
@@ -99610,7 +104207,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
@@ -99633,32 +104230,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 Role
HTTP Request
@@ -99712,30 +104313,34 @@ Appears In:
-List
+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 Role
HTTP Request
@@ -99794,7 +104399,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
@@ -99817,30 +104422,34 @@ Appears In:
-List All Namespaces
+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 Role
HTTP Request
@@ -99884,7 +104493,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
@@ -99907,30 +104516,34 @@ Appears In:
-Watch
+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 Role
HTTP Request
@@ -99993,7 +104606,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
@@ -100016,30 +104629,34 @@ Appears In:
-Watch List
+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 Role
HTTP Request
@@ -100098,7 +104715,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
@@ -100121,30 +104738,34 @@ Appears In:
-Watch List All Namespaces
+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 Role
HTTP Request
@@ -100188,7 +104809,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
@@ -100297,32 +104918,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a RoleBinding
HTTP Request
@@ -100382,10 +105007,6 @@ Appears In:
-200 RoleBinding
-OK
-
-
201 RoleBinding
Created
@@ -100393,32 +105014,40 @@ Appears In:
202 RoleBinding
Accepted
+
+200 RoleBinding
+OK
+
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified RoleBinding
HTTP Request
@@ -100487,30 +105116,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified RoleBinding
HTTP Request
@@ -100583,30 +105216,34 @@ Appears In:
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a RoleBinding
HTTP Request
@@ -100687,30 +105324,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of RoleBinding
HTTP Request
@@ -100769,7 +105410,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
@@ -100792,32 +105433,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 RoleBinding
HTTP Request
@@ -100871,30 +105516,34 @@ Appears In:
-List
+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 RoleBinding
HTTP Request
@@ -100953,7 +105602,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
@@ -100976,30 +105625,34 @@ Appears In:
-List All Namespaces
+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 RoleBinding
HTTP Request
@@ -101043,7 +105696,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
@@ -101066,30 +105719,34 @@ Appears In:
-Watch
+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 RoleBinding
HTTP Request
@@ -101152,7 +105809,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
@@ -101175,30 +105832,34 @@ Appears In:
-Watch List
+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 RoleBinding
HTTP Request
@@ -101257,7 +105918,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
@@ -101280,30 +105941,34 @@ Appears In:
-Watch List All Namespaces
+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 RoleBinding
HTTP Request
@@ -101347,7 +106012,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
@@ -101456,32 +106121,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a RoleBinding
HTTP Request
@@ -101554,30 +106223,34 @@ Appears In:
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified RoleBinding
HTTP Request
@@ -101646,30 +106319,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified RoleBinding
HTTP Request
@@ -101742,30 +106419,34 @@ Appears In:
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a RoleBinding
HTTP Request
@@ -101846,30 +106527,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of RoleBinding
HTTP Request
@@ -101928,7 +106613,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
@@ -101951,32 +106636,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 RoleBinding
HTTP Request
@@ -102030,30 +106719,34 @@ Appears In:
-List
+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 RoleBinding
HTTP Request
@@ -102112,7 +106805,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
@@ -102135,30 +106828,34 @@ Appears In:
-List All Namespaces
+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 RoleBinding
HTTP Request
@@ -102202,7 +106899,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
@@ -102225,30 +106922,34 @@ Appears In:
-Watch
+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 RoleBinding
HTTP Request
@@ -102311,7 +107012,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
@@ -102334,30 +107035,34 @@ Appears In:
-Watch List
+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 RoleBinding
HTTP Request
@@ -102416,7 +107121,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
@@ -102439,30 +107144,34 @@ Appears In:
-Watch List All Namespaces
+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 RoleBinding
HTTP Request
@@ -102506,7 +107215,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
@@ -102761,6 +107470,94 @@ Appears In:
+RunAsUserStrategyOptions v1beta1 policy
+
+
+
+Group
+Version
+Kind
+
+
+
+
+policy
+v1beta1
+RunAsUserStrategyOptions
+
+
+
+Run A sUser Strategy Options defines the strategy type and any options used to create the strategy.
+
+
+
+
+
+Field
+Description
+
+
+
+
+ranges IDRange array
+Ranges are the allowed ranges of uids that may be used.
+
+
+rule string
+Rule is the strategy that will dictate the allowable RunAsUser values that may be set.
+
+
+
+
+SELinuxStrategyOptions v1beta1 policy
+
+
+
+Group
+Version
+Kind
+
+
+
+
+policy
+v1beta1
+SELinuxStrategyOptions
+
+
+
+SELinux Strategy Options defines the strategy type and any options used to create the strategy.
+
+
+
+
Scale v1beta2 apps
@@ -103150,32 +107947,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a SelfSubjectAccessReview
HTTP Request
@@ -103220,6 +108021,10 @@ Appears In:
+200 SelfSubjectAccessReview
+OK
+
+
201 SelfSubjectAccessReview
Created
@@ -103227,10 +108032,6 @@ Appears In:
202 SelfSubjectAccessReview
Accepted
-
-200 SelfSubjectAccessReview
-OK
-
@@ -103307,32 +108108,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a SelfSubjectRulesReview
HTTP Request
@@ -103377,10 +108182,6 @@ Appears In:
-202 SelfSubjectRulesReview
-Accepted
-
-
200 SelfSubjectRulesReview
OK
@@ -103388,6 +108189,61 @@ Appears In:
201 SelfSubjectRulesReview
Created
+
+202 SelfSubjectRulesReview
+Accepted
+
+
+
+
+ServiceReference v1beta1 admissionregistration
+
+
+
+Group
+Version
+Kind
+
+
+
+
+admissionregistration
+v1beta1
+ServiceReference
+
+
+
+Other api versions of this object exist: v1
+
+
+ServiceReference holds a reference to Service.legacy.k8s.io
+
+
+
+
+
+Field
+Description
+
+
+
+
+name string
+name is the name of the service. Required
+
+
+namespace string
+namespace is the namespace of the service. Required
+
+
+path string
+path is an optional URL path which will be sent in any request to this service.
+
@@ -103408,6 +108264,9 @@ Appears In:
+Other api versions of this object exist: v1
+
+
ServiceReference holds a reference to Service.legacy.k8s.io
Appears In:
@@ -103629,32 +108488,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a StatefulSet
HTTP Request
@@ -103714,10 +108577,6 @@ Appears In:
-202 StatefulSet
-Accepted
-
-
200 StatefulSet
OK
@@ -103725,32 +108584,40 @@ Appears In:
201 StatefulSet
Created
+
+202 StatefulSet
+Accepted
+
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified StatefulSet
HTTP Request
@@ -103819,30 +108686,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified StatefulSet
HTTP Request
@@ -103906,39 +108777,43 @@ Appears In:
-201 StatefulSet
-Created
-
-
200 StatefulSet
OK
+
+201 StatefulSet
+Created
+
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a StatefulSet
HTTP Request
@@ -104019,30 +108894,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
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
@@ -104101,7 +108980,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
@@ -104124,32 +109003,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 StatefulSet
HTTP Request
@@ -104211,30 +109094,34 @@ Appears In:
-List
+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 StatefulSet
HTTP Request
@@ -104293,7 +109180,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
@@ -104316,30 +109203,34 @@ Appears In:
-List All Namespaces
+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 StatefulSet
HTTP Request
@@ -104383,7 +109274,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
@@ -104406,30 +109297,34 @@ Appears In:
-Watch
+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 StatefulSet
HTTP Request
@@ -104492,7 +109387,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
@@ -104515,30 +109410,34 @@ Appears In:
-Watch List
+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 StatefulSet
HTTP Request
@@ -104597,7 +109496,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
@@ -104620,30 +109519,34 @@ Appears In:
-Watch List All Namespaces
+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 StatefulSet
HTTP Request
@@ -104687,7 +109590,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
@@ -104710,32 +109613,36 @@ Appears In:
-Status Operations
+Status Operations
See supported operations below...
-Patch Status
+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 StatefulSet
HTTP Request
@@ -104804,30 +109711,34 @@ Appears In:
-Read Status
+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 StatefulSet
HTTP Request
@@ -104881,30 +109792,34 @@ Appears In:
-Replace Status
+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 StatefulSet
HTTP Request
@@ -104977,32 +109892,36 @@ Appears In:
-Misc Operations
+Misc Operations
See supported operations below...
-Read Scale
+Read Scale
kubectl Command
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
@@ -105056,30 +109975,34 @@ Appears In:
-Replace Scale
+Replace Scale
kubectl Command
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
@@ -105143,39 +110066,43 @@ Appears In:
-200 Scale
-OK
-
-
201 Scale
Created
+
+200 Scale
+OK
+
-Patch Scale
+Patch Scale
kubectl Command
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 StatefulSet
HTTP Request
@@ -105439,32 +110366,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a StatefulSet
HTTP Request
@@ -105524,10 +110455,6 @@ Appears In:
-200 StatefulSet
-OK
-
-
201 StatefulSet
Created
@@ -105535,32 +110462,40 @@ Appears In:
202 StatefulSet
Accepted
+
+200 StatefulSet
+OK
+
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified StatefulSet
HTTP Request
@@ -105629,30 +110564,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified StatefulSet
HTTP Request
@@ -105716,39 +110655,43 @@ Appears In:
-200 StatefulSet
-OK
-
-
201 StatefulSet
Created
+
+200 StatefulSet
+OK
+
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a StatefulSet
HTTP Request
@@ -105829,30 +110772,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
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
@@ -105911,7 +110858,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
@@ -105934,32 +110881,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 StatefulSet
HTTP Request
@@ -106021,30 +110972,34 @@ Appears In:
-List
+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 StatefulSet
HTTP Request
@@ -106103,7 +111058,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
@@ -106126,30 +111081,34 @@ Appears In:
-List All Namespaces
+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 StatefulSet
HTTP Request
@@ -106193,7 +111152,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
@@ -106216,30 +111175,34 @@ Appears In:
-Watch
+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 StatefulSet
HTTP Request
@@ -106302,7 +111265,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
@@ -106325,30 +111288,34 @@ Appears In:
-Watch List
+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 StatefulSet
HTTP Request
@@ -106407,7 +111374,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
@@ -106430,30 +111397,34 @@ Appears In:
-Watch List All Namespaces
+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 StatefulSet
HTTP Request
@@ -106497,7 +111468,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
@@ -106520,32 +111491,36 @@ Appears In:
-Status Operations
+Status Operations
See supported operations below...
-Patch Status
+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 StatefulSet
HTTP Request
@@ -106614,30 +111589,34 @@ Appears In:
-Read Status
+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 StatefulSet
HTTP Request
@@ -106691,30 +111670,34 @@ Appears In:
-Replace Status
+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 StatefulSet
HTTP Request
@@ -106787,32 +111770,36 @@ Appears In:
-Misc Operations
+Misc Operations
See supported operations below...
-Read Scale
+Read Scale
kubectl Command
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
@@ -106866,30 +111853,34 @@ Appears In:
-Replace Scale
+Replace Scale
kubectl Command
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
@@ -106962,30 +111953,34 @@ Appears In:
-Patch Scale
+Patch Scale
kubectl Command
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 StatefulSet
HTTP Request
@@ -107369,32 +112364,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+Create
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
create a StorageClass
HTTP Request
@@ -107439,10 +112438,6 @@ Appears In:
-202 StorageClass
-Accepted
-
-
200 StorageClass
OK
@@ -107450,32 +112445,40 @@ Appears In:
201 StorageClass
Created
+
+202 StorageClass
+Accepted
+
-Patch
+Patch
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
partially update the specified StorageClass
HTTP Request
@@ -107540,30 +112543,34 @@ Appears In:
-Replace
+Replace
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
replace the specified StorageClass
HTTP Request
@@ -107623,39 +112630,43 @@ Appears In:
-200 StorageClass
-OK
-
-
201 StorageClass
Created
+
+200 StorageClass
+OK
+
-Delete
+Delete
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete a StorageClass
HTTP Request
@@ -107732,30 +112743,34 @@ Appears In:
-Delete Collection
+Delete Collection
kubectl Command
Coming Soon
+
curl Command (requires kubectl proxy to be running )
Coming Soon
+
Output
Coming Soon
+
Response Body
Coming Soon
+
delete collection of StorageClass
HTTP Request
@@ -107799,7 +112814,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
@@ -107822,32 +112837,36 @@ Appears In:
-Read Operations
+Read Operations
See supported operations below...
-Read
+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 StorageClass
HTTP Request
@@ -107905,30 +112924,34 @@ Appears In:
-List
+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 StorageClass
HTTP Request
@@ -107972,7 +112995,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
@@ -107995,30 +113018,34 @@ Appears In:
-Watch
+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 StorageClass
HTTP Request
@@ -108077,7 +113104,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
@@ -108100,30 +113127,34 @@ Appears In:
-Watch List
+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 StorageClass
HTTP Request
@@ -108167,7 +113198,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
@@ -108433,32 +113464,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+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
@@ -108503,10 +113538,6 @@ Appears In:
-200 SubjectAccessReview
-OK
-
-
201 SubjectAccessReview
Created
@@ -108514,6 +113545,10 @@ Appears In:
202 SubjectAccessReview
Accepted
+
+200 SubjectAccessReview
+OK
+
@@ -108572,6 +113607,50 @@ Appears In:
+SupplementalGroupsStrategyOptions v1beta1 policy
+
+
+
+Group
+Version
+Kind
+
+
+
+
+policy
+v1beta1
+SupplementalGroupsStrategyOptions
+
+
+
+SupplementalGroupsStrategyOptions defines the strategy type and options used to create the strategy.
+
+
+
+
+
+Field
+Description
+
+
+
+
+ranges IDRange array
+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.
+
+
+
+
TokenReview v1beta1 authentication
@@ -108675,32 +113754,36 @@ Appears In:
-Write Operations
+Write Operations
See supported operations below...
-Create
+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
@@ -108745,6 +113828,10 @@ Appears In:
+201 TokenReview
+Created
+
+
202 TokenReview
Accepted
@@ -108752,10 +113839,6 @@ Appears In:
200 TokenReview
OK
-
-201 TokenReview
-Created
-
@@ -108813,6 +113896,1104 @@ Appears In:
+
+VolumeAttachment v1alpha1 storage
+
+
+
+Group
+Version
+Kind
+
+
+
+
+storage
+v1alpha1
+VolumeAttachment
+
+
+
+Other api versions of this object exist: v1beta1
+
+
+VolumeAttachment captures the intent to attach or detach the specified volume to/from the specified node.
+VolumeAttachment objects are non-namespaced.
+
+
+
+VolumeAttachmentSpec v1alpha1 storage
+
+
+
+
+
+Field
+Description
+
+
+
+
+attacher string
+Attacher indicates the name of the volume driver that MUST handle this request. This is the name returned by GetPluginName().
+
+
+nodeName string
+The node that the volume should be attached to.
+
+
+source VolumeAttachmentSource
+Source represents the volume that should be attached.
+
+
+
+VolumeAttachmentStatus v1alpha1 storage
+
+
+
+
+
+Field
+Description
+
+
+
+
+attachError VolumeError
+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.
+
+
+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.
+
+
+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.
+
+
+detachError VolumeError
+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.
+
+
+
+VolumeAttachmentList v1alpha1 storage
+
+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 VolumeAttachment
+HTTP Request
+POST /apis/storage.k8s.io/v1alpha1/volumeattachments
+Query Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+pretty
+If 'true', then the output is pretty printed.
+
+
+
+Body Parameters
+
+Response
+
+Patch
+
+ kubectl Command
+
+
+Coming Soon
+
+
+
+ curl Command (requires kubectl proxy to be running )
+
+
+Coming Soon
+
+
+
+ Output
+
+
+Coming Soon
+
+
+
+ Response Body
+
+
+Coming Soon
+
+
+partially update the specified VolumeAttachment
+HTTP Request
+PATCH /apis/storage.k8s.io/v1alpha1/volumeattachments/{name}
+Path Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+name
+name of the VolumeAttachment
+
+
+
+Query Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+pretty
+If 'true', then the output is pretty printed.
+
+
+
+Body Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+body Patch
+
+
+
+
+Response
+
+Replace
+
+ kubectl Command
+
+
+Coming Soon
+
+
+
+ curl Command (requires kubectl proxy to be running )
+
+
+Coming Soon
+
+
+
+ Output
+
+
+Coming Soon
+
+
+
+ Response Body
+
+
+Coming Soon
+
+
+replace the specified VolumeAttachment
+HTTP Request
+PUT /apis/storage.k8s.io/v1alpha1/volumeattachments/{name}
+Path Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+name
+name of the VolumeAttachment
+
+
+
+Query Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+pretty
+If 'true', then the output is pretty printed.
+
+
+
+Body Parameters
+
+Response
+
+Delete
+
+ kubectl Command
+
+
+Coming Soon
+
+
+
+ curl Command (requires kubectl proxy to be running )
+
+
+Coming Soon
+
+
+
+ Output
+
+
+Coming Soon
+
+
+
+ Response Body
+
+
+Coming Soon
+
+
+delete a VolumeAttachment
+HTTP Request
+DELETE /apis/storage.k8s.io/v1alpha1/volumeattachments/{name}
+Path Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+name
+name of the VolumeAttachment
+
+
+
+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.
+
+
+
+Body Parameters
+
+Response
+
+
+
+Code
+Description
+
+
+
+
+200 Status
+OK
+
+
+
+Delete Collection
+
+ kubectl Command
+
+
+Coming Soon
+
+
+
+ curl Command (requires kubectl proxy to be running )
+
+
+Coming Soon
+
+
+
+ Output
+
+
+Coming Soon
+
+
+
+ Response Body
+
+
+Coming Soon
+
+
+delete collection of VolumeAttachment
+HTTP Request
+DELETE /apis/storage.k8s.io/v1alpha1/volumeattachments
+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.
+
+
+
+Response
+
+
+
+Code
+Description
+
+
+
+
+200 Status
+OK
+
+
+
+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 VolumeAttachment
+HTTP Request
+GET /apis/storage.k8s.io/v1alpha1/volumeattachments/{name}
+Path Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+name
+name of the VolumeAttachment
+
+
+
+Query Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+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.
+
+
+
+Response
+
+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 VolumeAttachment
+HTTP Request
+GET /apis/storage.k8s.io/v1alpha1/volumeattachments
+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.
+
+
+
+Response
+
+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 VolumeAttachment
+HTTP Request
+GET /apis/storage.k8s.io/v1alpha1/watch/volumeattachments/{name}
+Path Parameters
+
+
+
+Parameter
+Description
+
+
+
+
+name
+name of the VolumeAttachment
+
+
+
+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.
+
+
+
+Response
+
+
+
+Code
+Description
+
+
+
+
+200 WatchEvent
+OK
+
+
+
+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 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.
+
+
+
+Response
+
+
+
+Code
+Description
+
+
+
+
+200 WatchEvent
+OK
+
+
+
+
+VolumeAttachmentSource v1alpha1 storage
+
+
+
+Group
+Version
+Kind
+
+
+
+
+storage
+v1alpha1
+VolumeAttachmentSource
+
+
+
+Other api versions of this object exist: v1beta1
+
+
+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
+Description
+
+
+
+
+persistentVolumeName string
+Name of the persistent volume to attach.
+
+
+
+
+VolumeError v1alpha1 storage
+
+
+
+Group
+Version
+Kind
+
+
+
+
+storage
+v1alpha1
+VolumeError
+
+
+
+Other api versions of this object exist: v1beta1
+
+
+VolumeError captures an error encountered during a volume operation.
+
+
+
+
+
+Field
+Description
+
+
+
+
+message string
+String detailing the error encountered during Attach or Detach operation. This string maybe logged, so it should not contain sensitive information.
+
+
+time Time
+Time the error was encountered.
+
+
+