POST /api/v1/pods HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close Content-Type: application/json' { "kind": "Pod", "apiVersion": "v1", ... }
Pod is a collection of containers that can run on a host. This resource is created by clients and scheduled onto hosts.
Expand or mouse-over a field for more information about it.
apiVersion:kind:metadata:
annotations:
[string]:clusterName:creationTimestamp:deletionGracePeriodSeconds:deletionTimestamp:finalizers:
- [string]:generateName:generation:initializers:
pending:
- name:result:
apiVersion:code:details:
causes:
- field:message:reason:group:kind:name:retryAfterSeconds:uid:kind:message:metadata:
continue:resourceVersion:selfLink:reason:status:labels:
[string]:name:namespace:ownerReferences:
- apiVersion:blockOwnerDeletion:controller:kind:name:uid:resourceVersion:selfLink:uid:spec:
activeDeadlineSeconds:affinity:
nodeAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- preference:
- matchExpressions:
- - key:operator:values:
- [string]:weight:requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- - key:operator:values:
- [string]:podAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- podAffinityTerm:
- labelSelector:
- matchExpressions:
- - key:operator:values:
- [string]:matchLabels:
[string]:namespaces:
- [string]:topologyKey:weight:requiredDuringSchedulingIgnoredDuringExecution:
- labelSelector:
- matchExpressions:
- - key:operator:values:
- [string]:matchLabels:
[string]:namespaces:
- [string]:topologyKey:podAntiAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- podAffinityTerm:
- labelSelector:
- matchExpressions:
- - key:operator:values:
- [string]:matchLabels:
[string]:namespaces:
- [string]:topologyKey:weight:requiredDuringSchedulingIgnoredDuringExecution:
- labelSelector:
- matchExpressions:
- - key:operator:values:
- [string]:matchLabels:
[string]:namespaces:
- [string]:topologyKey:automountServiceAccountToken:containers:
- args:
- - [string]:command:
- [string]:env:
- name:value:valueFrom:
configMapKeyRef:
key:name:optional:fieldRef:
apiVersion:fieldPath:resourceFieldRef:
containerName:divisor:resource:secretKeyRef:
key:name:optional:envFrom:
- configMapRef:
- name:optional:prefix:secretRef:
name:optional:image:imagePullPolicy:lifecycle:
postStart:
exec:
command:
- [string]:httpGet:
host:httpHeaders:
- name:value:path:port:scheme:tcpSocket:
host:port:preStop:
exec:
command:
- [string]:httpGet:
host:httpHeaders:
- name:value:path:port:scheme:tcpSocket:
host:port:livenessProbe:
exec:
command:
- [string]:failureThreshold:httpGet:
host:httpHeaders:
- name:value:path:port:scheme:initialDelaySeconds:periodSeconds:successThreshold:tcpSocket:
host:port:timeoutSeconds:name:ports:
- containerPort:hostIP:hostPort:name:protocol:readinessProbe:
exec:
command:
- [string]:failureThreshold:httpGet:
host:httpHeaders:
- name:value:path:port:scheme:initialDelaySeconds:periodSeconds:successThreshold:tcpSocket:
host:port:timeoutSeconds:resources:
limits:
[string]:requests:
[string]:securityContext:
allowPrivilegeEscalation:capabilities:
add:
- [string]:drop:
- [string]:privileged:readOnlyRootFilesystem:runAsNonRoot:runAsUser:seLinuxOptions:
level:role:type:user:stdin:stdinOnce:terminationMessagePath:terminationMessagePolicy:tty:volumeDevices:
- devicePath:name:volumeMounts:
- mountPath:mountPropagation:name:readOnly:subPath:workingDir:dnsConfig:
nameservers:
- [string]:options:
- name:value:searches:
- [string]:dnsPolicy:hostAliases:
- hostnames:
- - [string]:ip:hostIPC:hostNetwork:hostPID:hostname:imagePullSecrets:
- name:initContainers:
- args:
- - [string]:command:
- [string]:env:
- name:value:valueFrom:
configMapKeyRef:
key:name:optional:fieldRef:
apiVersion:fieldPath:resourceFieldRef:
containerName:divisor:resource:secretKeyRef:
key:name:optional:envFrom:
- configMapRef:
- name:optional:prefix:secretRef:
name:optional:image:imagePullPolicy:lifecycle:
postStart:
exec:
command:
- [string]:httpGet:
host:httpHeaders:
- name:value:path:port:scheme:tcpSocket:
host:port:preStop:
exec:
command:
- [string]:httpGet:
host:httpHeaders:
- name:value:path:port:scheme:tcpSocket:
host:port:livenessProbe:
exec:
command:
- [string]:failureThreshold:httpGet:
host:httpHeaders:
- name:value:path:port:scheme:initialDelaySeconds:periodSeconds:successThreshold:tcpSocket:
host:port:timeoutSeconds:name:ports:
- containerPort:hostIP:hostPort:name:protocol:readinessProbe:
exec:
command:
- [string]:failureThreshold:httpGet:
host:httpHeaders:
- name:value:path:port:scheme:initialDelaySeconds:periodSeconds:successThreshold:tcpSocket:
host:port:timeoutSeconds:resources:
limits:
[string]:requests:
[string]:securityContext:
allowPrivilegeEscalation:capabilities:
add:
- [string]:drop:
- [string]:privileged:readOnlyRootFilesystem:runAsNonRoot:runAsUser:seLinuxOptions:
level:role:type:user:stdin:stdinOnce:terminationMessagePath:terminationMessagePolicy:tty:volumeDevices:
- devicePath:name:volumeMounts:
- mountPath:mountPropagation:name:readOnly:subPath:workingDir:nodeName:nodeSelector:
[string]:priority:priorityClassName:restartPolicy:schedulerName:securityContext:
fsGroup:runAsNonRoot:runAsUser:seLinuxOptions:
level:role:type:user:supplementalGroups:
- [integer]:serviceAccount:serviceAccountName:subdomain:terminationGracePeriodSeconds:tolerations:
- effect:key:operator:tolerationSeconds:value:volumes:
- awsElasticBlockStore:
- fsType:partition:readOnly:volumeID:azureDisk:
cachingMode:diskName:diskURI:fsType:kind:readOnly:azureFile:
readOnly:secretName:shareName:cephfs:
monitors:
- [string]:path:readOnly:secretFile:secretRef:
name:user:cinder:
fsType:readOnly:volumeID:configMap:
defaultMode:items:
- key:mode:path:name:optional:downwardAPI:
defaultMode:items:
- fieldRef:
- apiVersion:fieldPath:mode:path:resourceFieldRef:
containerName:divisor:resource:emptyDir:
medium:sizeLimit:fc:
fsType:lun:readOnly:targetWWNs:
- [string]:wwids:
- [string]:flexVolume:
driver:fsType:options:
[string]:readOnly:secretRef:
name:flocker:
datasetName:datasetUUID:gcePersistentDisk:
fsType:partition:pdName:readOnly:gitRepo:
directory:repository:revision:glusterfs:
endpoints:path:readOnly:hostPath:
path:type:iscsi:
chapAuthDiscovery:chapAuthSession:fsType:initiatorName:iqn:iscsiInterface:lun:portals:
- [string]:readOnly:secretRef:
name:targetPortal:name:nfs:
path:readOnly:server:persistentVolumeClaim:
claimName:readOnly:photonPersistentDisk:
fsType:pdID:portworxVolume:
fsType:readOnly:volumeID:projected:
defaultMode:sources:
- configMap:
- items:
- - key:mode:path:name:optional:downwardAPI:
items:
- fieldRef:
- apiVersion:fieldPath:mode:path:resourceFieldRef:
containerName:divisor:resource:secret:
items:
- key:mode:path:name:optional:quobyte:
group:readOnly:registry:user:volume:rbd:
fsType:image:keyring:monitors:
- [string]:pool:readOnly:secretRef:
name:user:scaleIO:
fsType:gateway:protectionDomain:readOnly:secretRef:
name:sslEnabled:storageMode:storagePool:system:volumeName:secret:
defaultMode:items:
- key:mode:path:optional:secretName:storageos:
fsType:readOnly:secretRef:
name:volumeName:volumeNamespace:vsphereVolume:
fsType:storagePolicyID:storagePolicyName:volumePath:status:
conditions:
- lastProbeTime:lastTransitionTime:message:reason:status:type:containerStatuses:
- containerID:image:imageID:lastState:
running:
startedAt:terminated:
containerID:exitCode:finishedAt:message:reason:signal:startedAt:waiting:
message:reason:name:ready:restartCount:state:
running:
startedAt:terminated:
containerID:exitCode:finishedAt:message:reason:signal:startedAt:waiting:
message:reason:hostIP:initContainerStatuses:
- containerID:image:imageID:lastState:
running:
startedAt:terminated:
containerID:exitCode:finishedAt:message:reason:signal:startedAt:waiting:
message:reason:name:ready:restartCount:state:
running:
startedAt:terminated:
containerID:exitCode:finishedAt:message:reason:signal:startedAt:waiting:
message:reason:message:phase:podIP:qosClass:reason:startTime:
Create a Pod
POST /api/v1/pods HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close Content-Type: application/json' { "kind": "Pod", "apiVersion": "v1", ... }
Create a Pod
POST /api/v1/namespaces/$NAMESPACE/pods HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close Content-Type: application/json' { "kind": "Pod", "apiVersion": "v1", ... }
$ curl -k \ -X POST \ -d @- \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ -H 'Content-Type: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods <<'EOF' { "kind": "Pod", "apiVersion": "v1", ... } EOF
Read the specified Pod
GET /api/v1/namespaces/$NAMESPACE/pods/$NAME HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
List or watch objects of kind Pod
GET /api/v1/pods HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/pods
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 The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. |
resourceVersion |
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it’s 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv. |
timeoutSeconds |
Timeout for the list/watch call. |
watch |
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. |
List or watch objects of kind Pod
GET /api/v1/namespaces/$NAMESPACE/pods HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods
Parameter | Description |
---|---|
namespace |
object name and auth scope, such as for teams and projects |
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 The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. |
resourceVersion |
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it’s 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv. |
timeoutSeconds |
Timeout for the list/watch call. |
watch |
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. |
Watch changes to an object of kind Pod
GET /api/v1/watch/namespaces/$NAMESPACE/pods/$NAME HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/watch/namespaces/$NAMESPACE/pods/$NAME
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
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 The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. |
pretty |
If 'true', then the output is pretty printed. |
resourceVersion |
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it’s 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv. |
timeoutSeconds |
Timeout for the list/watch call. |
watch |
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. |
Watch individual changes to a list of Pod
GET /api/v1/watch/pods HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/watch/pods
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 The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. |
pretty |
If 'true', then the output is pretty printed. |
resourceVersion |
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it’s 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv. |
timeoutSeconds |
Timeout for the list/watch call. |
watch |
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. |
Watch individual changes to a list of Pod
GET /api/v1/watch/namespaces/$NAMESPACE/pods HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/watch/namespaces/$NAMESPACE/pods
Parameter | Description |
---|---|
namespace |
object name and auth scope, such as for teams and projects |
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 The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. |
pretty |
If 'true', then the output is pretty printed. |
resourceVersion |
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it’s 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv. |
timeoutSeconds |
Timeout for the list/watch call. |
watch |
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. |
Replace the specified Pod
PUT /api/v1/namespaces/$NAMESPACE/pods/$NAME HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close Content-Type: application/json' { "kind": "Pod", "apiVersion": "v1", ... }
$ curl -k \ -X PUT \ -d @- \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ -H 'Content-Type: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME <<'EOF' { "kind": "Pod", "apiVersion": "v1", ... } EOF
Partially update the specified Pod
PATCH /api/v1/namespaces/$NAMESPACE/pods/$NAME HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close Content-Type: application/json-patch+json' { ... }
$ curl -k \ -X PATCH \ -d @- \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ -H 'Content-Type: application/json-patch+json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME <<'EOF' { ... } EOF
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
Delete a Pod
DELETE /api/v1/namespaces/$NAMESPACE/pods/$NAME HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close Content-Type: application/json' { ... }
$ curl -k \ -X DELETE \ -d @- \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ -H 'Content-Type: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME <<'EOF' { ... } EOF
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
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. |
Delete collection of Pod
DELETE /api/v1/namespaces/$NAMESPACE/pods HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -X DELETE \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods
Parameter | Description |
---|---|
namespace |
object name and auth scope, such as for teams and projects |
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 The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. |
resourceVersion |
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it’s 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv. |
timeoutSeconds |
Timeout for the list/watch call. |
watch |
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. |
Connect POST requests to attach of Pod
POST /api/v1/namespaces/$NAMESPACE/pods/$NAME/attach HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -X POST \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/attach
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
Parameter | Description |
---|---|
container |
The container in which to execute the command. Defaults to only container if there is only one container in the pod. |
stderr |
Stderr if true indicates that stderr is to be redirected for the attach call. Defaults to true. |
stdin |
Stdin if true, redirects the standard input stream of the pod for this call. Defaults to false. |
stdout |
Stdout if true indicates that stdout is to be redirected for the attach call. Defaults to true. |
tty |
TTY if true indicates that a tty will be allocated for the attach call. This is passed through the container runtime so the tty is allocated on the worker node by the container runtime. Defaults to false. |
Connect GET requests to attach of Pod
GET /api/v1/namespaces/$NAMESPACE/pods/$NAME/attach HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/attach
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
Parameter | Description |
---|---|
container |
The container in which to execute the command. Defaults to only container if there is only one container in the pod. |
stderr |
Stderr if true indicates that stderr is to be redirected for the attach call. Defaults to true. |
stdin |
Stdin if true, redirects the standard input stream of the pod for this call. Defaults to false. |
stdout |
Stdout if true indicates that stdout is to be redirected for the attach call. Defaults to true. |
tty |
TTY if true indicates that a tty will be allocated for the attach call. This is passed through the container runtime so the tty is allocated on the worker node by the container runtime. Defaults to false. |
Create binding of a Pod
POST /api/v1/namespaces/$NAMESPACE/pods/$NAME/binding HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close Content-Type: application/json' { "kind": "Binding", "apiVersion": "v1", ... }
$ curl -k \ -X POST \ -d @- \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ -H 'Content-Type: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/binding <<'EOF' { "kind": "Binding", "apiVersion": "v1", ... } EOF
Parameter | Description |
---|---|
name |
name of the Binding |
namespace |
object name and auth scope, such as for teams and projects |
Create eviction of a Pod
POST /api/v1/namespaces/$NAMESPACE/pods/$NAME/eviction HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close Content-Type: application/json' { "kind": "Eviction", "apiVersion": "policy/v1beta1", ... }
$ curl -k \ -X POST \ -d @- \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ -H 'Content-Type: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/eviction <<'EOF' { "kind": "Eviction", "apiVersion": "policy/v1beta1", ... } EOF
Parameter | Description |
---|---|
name |
name of the Eviction |
namespace |
object name and auth scope, such as for teams and projects |
Connect POST requests to exec of Pod
POST /api/v1/namespaces/$NAMESPACE/pods/$NAME/exec HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -X POST \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/exec
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
Parameter | Description |
---|---|
command |
Command is the remote command to execute. argv array. Not executed within a shell. |
container |
Container in which to execute the command. Defaults to only container if there is only one container in the pod. |
stderr |
Redirect the standard error stream of the pod for this call. Defaults to true. |
stdin |
Redirect the standard input stream of the pod for this call. Defaults to false. |
stdout |
Redirect the standard output stream of the pod for this call. Defaults to true. |
tty |
TTY if true indicates that a tty will be allocated for the exec call. Defaults to false. |
Connect GET requests to exec of Pod
GET /api/v1/namespaces/$NAMESPACE/pods/$NAME/exec HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/exec
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
Parameter | Description |
---|---|
command |
Command is the remote command to execute. argv array. Not executed within a shell. |
container |
Container in which to execute the command. Defaults to only container if there is only one container in the pod. |
stderr |
Redirect the standard error stream of the pod for this call. Defaults to true. |
stdin |
Redirect the standard input stream of the pod for this call. Defaults to false. |
stdout |
Redirect the standard output stream of the pod for this call. Defaults to true. |
tty |
TTY if true indicates that a tty will be allocated for the exec call. Defaults to false. |
Read log of the specified Pod
GET /api/v1/namespaces/$NAMESPACE/pods/$NAME/log HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/log
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
Parameter | Description |
---|---|
container |
The container for which to stream logs. Defaults to only container if there is one container in the pod. |
follow |
Follow the log stream of the pod. Defaults to false. |
limitBytes |
If set, the number of bytes to read from the server before terminating the log output. This may not display a complete final line of logging, and may return slightly more or slightly less than the specified limit. |
pretty |
If 'true', then the output is pretty printed. |
previous |
Return previous terminated container logs. Defaults to false. |
sinceSeconds |
A relative time in seconds before the current time from which to show logs. If this value precedes the time a pod was started, only logs since the pod start will be returned. If this value is in the future, no logs will be returned. Only one of sinceSeconds or sinceTime may be specified. |
tailLines |
If set, the number of lines from the end of the logs to show. If not specified, logs are shown from the creation of the container or sinceSeconds or sinceTime |
timestamps |
If true, add an RFC3339 or RFC3339Nano timestamp at the beginning of every line of log output. Defaults to false. |
Connect POST requests to portforward of Pod
POST /api/v1/namespaces/$NAMESPACE/pods/$NAME/portforward HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -X POST \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/portforward
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
Connect GET requests to portforward of Pod
GET /api/v1/namespaces/$NAMESPACE/pods/$NAME/portforward HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/portforward
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
Read status of the specified Pod
GET /api/v1/namespaces/$NAMESPACE/pods/$NAME/status HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/status
Replace status of the specified Pod
PUT /api/v1/namespaces/$NAMESPACE/pods/$NAME/status HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close Content-Type: application/json' { "kind": "Pod", "apiVersion": "v1", ... }
$ curl -k \ -X PUT \ -d @- \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ -H 'Content-Type: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/status <<'EOF' { "kind": "Pod", "apiVersion": "v1", ... } EOF
Partially update status of the specified Pod
PATCH /api/v1/namespaces/$NAMESPACE/pods/$NAME/status HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close Content-Type: application/json-patch+json' { ... }
$ curl -k \ -X PATCH \ -d @- \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ -H 'Content-Type: application/json-patch+json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/status <<'EOF' { ... } EOF
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
Connect OPTIONS requests to proxy of Pod
OPTIONS /api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -X OPTIONS \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
Connect POST requests to proxy of Pod
POST /api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -X POST \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
Connect HEAD requests to proxy of Pod
HEAD /api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -X HEAD \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
Connect GET requests to proxy of Pod
GET /api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
Connect PUT requests to proxy of Pod
PUT /api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -X PUT \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
Connect PATCH requests to proxy of Pod
PATCH /api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -X PATCH \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
Connect DELETE requests to proxy of Pod
DELETE /api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -X DELETE \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
Connect OPTIONS requests to proxy of Pod
OPTIONS /api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy/$PATH HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -X OPTIONS \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy/$PATH
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
path |
path to the resource |
Connect POST requests to proxy of Pod
POST /api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy/$PATH HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -X POST \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy/$PATH
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
path |
path to the resource |
Connect HEAD requests to proxy of Pod
HEAD /api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy/$PATH HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -X HEAD \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy/$PATH
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
path |
path to the resource |
Connect GET requests to proxy of Pod
GET /api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy/$PATH HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy/$PATH
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
path |
path to the resource |
Connect PUT requests to proxy of Pod
PUT /api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy/$PATH HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -X PUT \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy/$PATH
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
path |
path to the resource |
Connect PATCH requests to proxy of Pod
PATCH /api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy/$PATH HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -X PATCH \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy/$PATH
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
path |
path to the resource |
Connect DELETE requests to proxy of Pod
DELETE /api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy/$PATH HTTP/1.1 Authorization: Bearer $TOKEN Accept: application/json Connection: close
$ curl -k \ -X DELETE \ -H "Authorization: Bearer $TOKEN" \ -H 'Accept: application/json' \ https://$ENDPOINT/api/v1/namespaces/$NAMESPACE/pods/$NAME/proxy/$PATH
Parameter | Description |
---|---|
name |
name of the Pod |
namespace |
object name and auth scope, such as for teams and projects |
path |
path to the resource |