kubernetes.api.v1 — nubank/kubernetes-api 1.6.0

create-namespace clj

(create-namespace ctx__10517__auto__
                  &
                  [body?__10518__auto__ opts?__10519__auto__])

Calls POST on /api/v1/namespaces create a Namespace Parameters: - ctx: required server context - body: required v1.Namespace Options: - body: required v1.Namespace Returns v1.Namespace

create-namespaced-binding clj

(create-namespaced-binding ctx__10517__auto__
                           &
                           [body?__10518__auto__ opts?__10519__auto__])

Calls POST on /api/v1/namespaces/{namespace}/bindings create a Binding Parameters: - ctx: required server context - body: required v1.Binding Options: - body: required v1.Binding - namespace: required string object name and auth scope, such as for teams and projects Returns v1.Binding

create-namespaced-config-map clj

(create-namespaced-config-map ctx__10517__auto__
                              &
                              [body?__10518__auto__ opts?__10519__auto__])

Calls POST on /api/v1/namespaces/{namespace}/configmaps create a ConfigMap Parameters: - ctx: required server context - body: required v1.ConfigMap Options: - body: required v1.ConfigMap - namespace: required string object name and auth scope, such as for teams and projects Returns v1.ConfigMap

create-namespaced-endpoints clj

(create-namespaced-endpoints ctx__10517__auto__
                             &
                             [body?__10518__auto__ opts?__10519__auto__])

Calls POST on /api/v1/namespaces/{namespace}/endpoints create Endpoints Parameters: - ctx: required server context - body: required v1.Endpoints Options: - body: required v1.Endpoints - namespace: required string object name and auth scope, such as for teams and projects Returns v1.Endpoints

create-namespaced-event clj

(create-namespaced-event ctx__10517__auto__
                         &
                         [body?__10518__auto__ opts?__10519__auto__])

Calls POST on /api/v1/namespaces/{namespace}/events create an Event Parameters: - ctx: required server context - body: required v1.Event Options: - body: required v1.Event - namespace: required string object name and auth scope, such as for teams and projects Returns v1.Event

create-namespaced-limit-range clj

(create-namespaced-limit-range ctx__10517__auto__
                               &
                               [body?__10518__auto__ opts?__10519__auto__])

Calls POST on /api/v1/namespaces/{namespace}/limitranges create a LimitRange Parameters: - ctx: required server context - body: required v1.LimitRange Options: - body: required v1.LimitRange - namespace: required string object name and auth scope, such as for teams and projects Returns v1.LimitRange

create-namespaced-persistent-volume-claim clj

(create-namespaced-persistent-volume-claim ctx__10517__auto__
                                           &
                                           [body?__10518__auto__
                                            opts?__10519__auto__])

Calls POST on /api/v1/namespaces/{namespace}/persistentvolumeclaims create a PersistentVolumeClaim Parameters: - ctx: required server context - body: required v1.PersistentVolumeClaim Options: - body: required v1.PersistentVolumeClaim - namespace: required string object name and auth scope, such as for teams and projects Returns v1.PersistentVolumeClaim

create-namespaced-pod clj

(create-namespaced-pod ctx__10517__auto__
                       &
                       [body?__10518__auto__ opts?__10519__auto__])

Calls POST on /api/v1/namespaces/{namespace}/pods create a Pod Parameters: - ctx: required server context - body: required v1.Pod Options: - body: required v1.Pod - namespace: required string object name and auth scope, such as for teams and projects Returns v1.Pod

create-namespaced-pod-binding clj

(create-namespaced-pod-binding ctx__10517__auto__
                               &
                               [body?__10518__auto__ opts?__10519__auto__])

Calls POST on /api/v1/namespaces/{namespace}/pods/{name}/binding create binding of a Pod Parameters: - ctx: required server context - body: required v1.Binding Options: - body: required v1.Binding - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Binding Returns v1.Binding

create-namespaced-pod-eviction clj

(create-namespaced-pod-eviction ctx__10517__auto__
                                &
                                [body?__10518__auto__ opts?__10519__auto__])

Calls POST on /api/v1/namespaces/{namespace}/pods/{name}/eviction create eviction of a Pod Parameters: - ctx: required server context - body: required v1beta1.Eviction Options: - body: required v1beta1.Eviction - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Eviction Returns v1beta1.Eviction

create-namespaced-pod-template clj

(create-namespaced-pod-template ctx__10517__auto__
                                &
                                [body?__10518__auto__ opts?__10519__auto__])

Calls POST on /api/v1/namespaces/{namespace}/podtemplates create a PodTemplate Parameters: - ctx: required server context - body: required v1.PodTemplate Options: - body: required v1.PodTemplate - namespace: required string object name and auth scope, such as for teams and projects Returns v1.PodTemplate

create-namespaced-replication-controller clj

(create-namespaced-replication-controller ctx__10517__auto__
                                          &
                                          [body?__10518__auto__
                                           opts?__10519__auto__])

Calls POST on /api/v1/namespaces/{namespace}/replicationcontrollers create a ReplicationController Parameters: - ctx: required server context - body: required v1.ReplicationController Options: - body: required v1.ReplicationController - namespace: required string object name and auth scope, such as for teams and projects Returns v1.ReplicationController

create-namespaced-resource-quota clj

(create-namespaced-resource-quota ctx__10517__auto__
                                  &
                                  [body?__10518__auto__ opts?__10519__auto__])

Calls POST on /api/v1/namespaces/{namespace}/resourcequotas create a ResourceQuota Parameters: - ctx: required server context - body: required v1.ResourceQuota Options: - body: required v1.ResourceQuota - namespace: required string object name and auth scope, such as for teams and projects Returns v1.ResourceQuota

create-namespaced-secret clj

(create-namespaced-secret ctx__10517__auto__
                          &
                          [body?__10518__auto__ opts?__10519__auto__])

Calls POST on /api/v1/namespaces/{namespace}/secrets create a Secret Parameters: - ctx: required server context - body: required v1.Secret Options: - body: required v1.Secret - namespace: required string object name and auth scope, such as for teams and projects Returns v1.Secret

create-namespaced-service clj

(create-namespaced-service ctx__10517__auto__
                           &
                           [body?__10518__auto__ opts?__10519__auto__])

Calls POST on /api/v1/namespaces/{namespace}/services create a Service Parameters: - ctx: required server context - body: required v1.Service Options: - body: required v1.Service - namespace: required string object name and auth scope, such as for teams and projects Returns v1.Service

create-namespaced-service-account clj

(create-namespaced-service-account ctx__10517__auto__
                                   &
                                   [body?__10518__auto__ opts?__10519__auto__])

Calls POST on /api/v1/namespaces/{namespace}/serviceaccounts create a ServiceAccount Parameters: - ctx: required server context - body: required v1.ServiceAccount Options: - body: required v1.ServiceAccount - namespace: required string object name and auth scope, such as for teams and projects Returns v1.ServiceAccount

create-node clj

(create-node ctx__10517__auto__ & [body?__10518__auto__ opts?__10519__auto__])

Calls POST on /api/v1/nodes create a Node Parameters: - ctx: required server context - body: required v1.Node Options: - body: required v1.Node Returns v1.Node

create-persistent-volume clj

(create-persistent-volume ctx__10517__auto__
                          &
                          [body?__10518__auto__ opts?__10519__auto__])

Calls POST on /api/v1/persistentvolumes create a PersistentVolume Parameters: - ctx: required server context - body: required v1.PersistentVolume Options: - body: required v1.PersistentVolume Returns v1.PersistentVolume

delete-namespace clj

(delete-namespace ctx__10517__auto__
                  &
                  [body?__10518__auto__ opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{name} delete a Namespace Parameters: - ctx: required server context - body: required v1.DeleteOptions Options: - body: required v1.DeleteOptions - grace-period-seconds: optional integer 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. - orphan-dependents: optional boolean 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. - propagation-policy: optional string Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. - name: required string name of the Namespace Returns v1.Status

delete-namespaced-config-map clj

(delete-namespaced-config-map ctx__10517__auto__
                              &
                              [body?__10518__auto__ opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/configmaps/{name} delete a ConfigMap Parameters: - ctx: required server context - body: required v1.DeleteOptions Options: - body: required v1.DeleteOptions - grace-period-seconds: optional integer 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. - orphan-dependents: optional boolean 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. - propagation-policy: optional string Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ConfigMap Returns v1.Status

delete-namespaced-endpoints clj

(delete-namespaced-endpoints ctx__10517__auto__
                             &
                             [body?__10518__auto__ opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/endpoints/{name} delete Endpoints Parameters: - ctx: required server context - body: required v1.DeleteOptions Options: - body: required v1.DeleteOptions - grace-period-seconds: optional integer 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. - orphan-dependents: optional boolean 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. - propagation-policy: optional string Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Endpoints Returns v1.Status

delete-namespaced-event clj

(delete-namespaced-event ctx__10517__auto__
                         &
                         [body?__10518__auto__ opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/events/{name} delete an Event Parameters: - ctx: required server context - body: required v1.DeleteOptions Options: - body: required v1.DeleteOptions - grace-period-seconds: optional integer 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. - orphan-dependents: optional boolean 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. - propagation-policy: optional string Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Event Returns v1.Status

delete-namespaced-limit-range clj

(delete-namespaced-limit-range ctx__10517__auto__
                               &
                               [body?__10518__auto__ opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/limitranges/{name} delete a LimitRange Parameters: - ctx: required server context - body: required v1.DeleteOptions Options: - body: required v1.DeleteOptions - grace-period-seconds: optional integer 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. - orphan-dependents: optional boolean 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. - propagation-policy: optional string Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the LimitRange Returns v1.Status

delete-namespaced-persistent-volume-claim clj

(delete-namespaced-persistent-volume-claim ctx__10517__auto__
                                           &
                                           [body?__10518__auto__
                                            opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name} delete a PersistentVolumeClaim Parameters: - ctx: required server context - body: required v1.DeleteOptions Options: - body: required v1.DeleteOptions - grace-period-seconds: optional integer 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. - orphan-dependents: optional boolean 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. - propagation-policy: optional string Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the PersistentVolumeClaim Returns v1.Status

delete-namespaced-pod clj

(delete-namespaced-pod ctx__10517__auto__
                       &
                       [body?__10518__auto__ opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/pods/{name} delete a Pod Parameters: - ctx: required server context - body: required v1.DeleteOptions Options: - body: required v1.DeleteOptions - grace-period-seconds: optional integer 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. - orphan-dependents: optional boolean 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. - propagation-policy: optional string Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Pod Returns v1.Status

delete-namespaced-pod-template clj

(delete-namespaced-pod-template ctx__10517__auto__
                                &
                                [body?__10518__auto__ opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/podtemplates/{name} delete a PodTemplate Parameters: - ctx: required server context - body: required v1.DeleteOptions Options: - body: required v1.DeleteOptions - grace-period-seconds: optional integer 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. - orphan-dependents: optional boolean 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. - propagation-policy: optional string Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the PodTemplate Returns v1.Status

delete-namespaced-replication-controller clj

(delete-namespaced-replication-controller ctx__10517__auto__
                                          &
                                          [body?__10518__auto__
                                           opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/replicationcontrollers/{name} delete a ReplicationController Parameters: - ctx: required server context - body: required v1.DeleteOptions Options: - body: required v1.DeleteOptions - grace-period-seconds: optional integer 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. - orphan-dependents: optional boolean 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. - propagation-policy: optional string Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ReplicationController Returns v1.Status

delete-namespaced-resource-quota clj

(delete-namespaced-resource-quota ctx__10517__auto__
                                  &
                                  [body?__10518__auto__ opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/resourcequotas/{name} delete a ResourceQuota Parameters: - ctx: required server context - body: required v1.DeleteOptions Options: - body: required v1.DeleteOptions - grace-period-seconds: optional integer 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. - orphan-dependents: optional boolean 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. - propagation-policy: optional string Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ResourceQuota Returns v1.Status

delete-namespaced-secret clj

(delete-namespaced-secret ctx__10517__auto__
                          &
                          [body?__10518__auto__ opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/secrets/{name} delete a Secret Parameters: - ctx: required server context - body: required v1.DeleteOptions Options: - body: required v1.DeleteOptions - grace-period-seconds: optional integer 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. - orphan-dependents: optional boolean 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. - propagation-policy: optional string Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Secret Returns v1.Status

delete-namespaced-service clj

(delete-namespaced-service ctx__10517__auto__
                           &
                           [body?__10518__auto__ opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/services/{name} delete a Service Parameters: - ctx: required server context - body: required v1.DeleteOptions Options: - body: required v1.DeleteOptions - grace-period-seconds: optional integer 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. - orphan-dependents: optional boolean 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. - propagation-policy: optional string Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Service Returns v1.Status

delete-namespaced-service-account clj

(delete-namespaced-service-account ctx__10517__auto__
                                   &
                                   [body?__10518__auto__ opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/serviceaccounts/{name} delete a ServiceAccount Parameters: - ctx: required server context - body: required v1.DeleteOptions Options: - body: required v1.DeleteOptions - grace-period-seconds: optional integer 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. - orphan-dependents: optional boolean 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. - propagation-policy: optional string Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ServiceAccount Returns v1.Status

delete-node clj

(delete-node ctx__10517__auto__ & [body?__10518__auto__ opts?__10519__auto__])

Calls DELETE on /api/v1/nodes/{name} delete a Node Parameters: - ctx: required server context - body: required v1.DeleteOptions Options: - body: required v1.DeleteOptions - grace-period-seconds: optional integer 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. - orphan-dependents: optional boolean 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. - propagation-policy: optional string Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. - name: required string name of the Node Returns v1.Status

delete-persistent-volume clj

(delete-persistent-volume ctx__10517__auto__
                          &
                          [body?__10518__auto__ opts?__10519__auto__])

Calls DELETE on /api/v1/persistentvolumes/{name} delete a PersistentVolume Parameters: - ctx: required server context - body: required v1.DeleteOptions Options: - body: required v1.DeleteOptions - grace-period-seconds: optional integer 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. - orphan-dependents: optional boolean 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. - propagation-policy: optional string Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. - name: required string name of the PersistentVolume Returns v1.Status

deletecollection-namespaced-config-map clj

(deletecollection-namespaced-config-map ctx__10517__auto__
                                        &
                                        [body?__10518__auto__
                                         opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/configmaps delete collection of ConfigMap Parameters: - ctx: required server context - body: required Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.Status

deletecollection-namespaced-endpoints clj

(deletecollection-namespaced-endpoints ctx__10517__auto__
                                       &
                                       [body?__10518__auto__
                                        opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/endpoints delete collection of Endpoints Parameters: - ctx: required server context - body: required Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.Status

deletecollection-namespaced-event clj

(deletecollection-namespaced-event ctx__10517__auto__
                                   &
                                   [body?__10518__auto__ opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/events delete collection of Event Parameters: - ctx: required server context - body: required Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.Status

deletecollection-namespaced-limit-range clj

(deletecollection-namespaced-limit-range ctx__10517__auto__
                                         &
                                         [body?__10518__auto__
                                          opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/limitranges delete collection of LimitRange Parameters: - ctx: required server context - body: required Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.Status

deletecollection-namespaced-persistent-volume-claim clj

(deletecollection-namespaced-persistent-volume-claim ctx__10517__auto__
                                                     &
                                                     [body?__10518__auto__
                                                      opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/persistentvolumeclaims delete collection of PersistentVolumeClaim Parameters: - ctx: required server context - body: required Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.Status

deletecollection-namespaced-pod clj

(deletecollection-namespaced-pod ctx__10517__auto__
                                 &
                                 [body?__10518__auto__ opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/pods delete collection of Pod Parameters: - ctx: required server context - body: required Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.Status

deletecollection-namespaced-pod-template clj

(deletecollection-namespaced-pod-template ctx__10517__auto__
                                          &
                                          [body?__10518__auto__
                                           opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/podtemplates delete collection of PodTemplate Parameters: - ctx: required server context - body: required Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.Status

deletecollection-namespaced-replication-controller clj

(deletecollection-namespaced-replication-controller ctx__10517__auto__
                                                    &
                                                    [body?__10518__auto__
                                                     opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/replicationcontrollers delete collection of ReplicationController Parameters: - ctx: required server context - body: required Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.Status

deletecollection-namespaced-resource-quota clj

(deletecollection-namespaced-resource-quota ctx__10517__auto__
                                            &
                                            [body?__10518__auto__
                                             opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/resourcequotas delete collection of ResourceQuota Parameters: - ctx: required server context - body: required Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.Status

deletecollection-namespaced-secret clj

(deletecollection-namespaced-secret ctx__10517__auto__
                                    &
                                    [body?__10518__auto__ opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/secrets delete collection of Secret Parameters: - ctx: required server context - body: required Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.Status

deletecollection-namespaced-service-account clj

(deletecollection-namespaced-service-account ctx__10517__auto__
                                             &
                                             [body?__10518__auto__
                                              opts?__10519__auto__])

Calls DELETE on /api/v1/namespaces/{namespace}/serviceaccounts delete collection of ServiceAccount Parameters: - ctx: required server context - body: required Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.Status

deletecollection-node clj

(deletecollection-node ctx__10517__auto__
                       &
                       [body?__10518__auto__ opts?__10519__auto__])

Calls DELETE on /api/v1/nodes delete collection of Node Parameters: - ctx: required server context - body: required Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. Returns v1.Status

deletecollection-persistent-volume clj

(deletecollection-persistent-volume ctx__10517__auto__
                                    &
                                    [body?__10518__auto__ opts?__10519__auto__])

Calls DELETE on /api/v1/persistentvolumes delete collection of PersistentVolume Parameters: - ctx: required server context - body: required Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. Returns v1.Status

get-api-resources clj

(get-api-resources ctx__10517__auto__
                   &
                   [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1 get available resources Parameters: - ctx: required server context Returns

list-component-status clj

(list-component-status ctx__10517__auto__
                       &
                       [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/componentstatuses list objects of kind ComponentStatus Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. Returns v1.ComponentStatusList

list-config-map-for-all-namespaces clj

(list-config-map-for-all-namespaces ctx__10517__auto__
                                    &
                                    [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/configmaps list or watch objects of kind ConfigMap Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. Returns v1.ConfigMapList

list-endpoints-for-all-namespaces clj

(list-endpoints-for-all-namespaces ctx__10517__auto__
                                   &
                                   [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/endpoints list or watch objects of kind Endpoints Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. Returns v1.EndpointsList

list-event-for-all-namespaces clj

(list-event-for-all-namespaces ctx__10517__auto__
                               &
                               [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/events list or watch objects of kind Event Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. Returns v1.EventList

list-limit-range-for-all-namespaces clj

(list-limit-range-for-all-namespaces ctx__10517__auto__
                                     &
                                     [body?__10518__auto__
                                      opts?__10519__auto__])

Calls GET on /api/v1/limitranges list or watch objects of kind LimitRange Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. Returns v1.LimitRangeList

list-namespace clj

(list-namespace ctx__10517__auto__
                &
                [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces list or watch objects of kind Namespace Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. Returns v1.NamespaceList

list-namespaced-config-map clj

(list-namespaced-config-map ctx__10517__auto__
                            &
                            [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/configmaps list or watch objects of kind ConfigMap Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.ConfigMapList

list-namespaced-endpoints clj

(list-namespaced-endpoints ctx__10517__auto__
                           &
                           [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/endpoints list or watch objects of kind Endpoints Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.EndpointsList

list-namespaced-event clj

(list-namespaced-event ctx__10517__auto__
                       &
                       [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/events list or watch objects of kind Event Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.EventList

list-namespaced-limit-range clj

(list-namespaced-limit-range ctx__10517__auto__
                             &
                             [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/limitranges list or watch objects of kind LimitRange Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.LimitRangeList

list-namespaced-persistent-volume-claim clj

(list-namespaced-persistent-volume-claim ctx__10517__auto__
                                         &
                                         [body?__10518__auto__
                                          opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/persistentvolumeclaims list or watch objects of kind PersistentVolumeClaim Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.PersistentVolumeClaimList

list-namespaced-pod clj

(list-namespaced-pod ctx__10517__auto__
                     &
                     [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/pods list or watch objects of kind Pod Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.PodList

list-namespaced-pod-template clj

(list-namespaced-pod-template ctx__10517__auto__
                              &
                              [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/podtemplates list or watch objects of kind PodTemplate Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.PodTemplateList

list-namespaced-replication-controller clj

(list-namespaced-replication-controller ctx__10517__auto__
                                        &
                                        [body?__10518__auto__
                                         opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/replicationcontrollers list or watch objects of kind ReplicationController Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.ReplicationControllerList

list-namespaced-resource-quota clj

(list-namespaced-resource-quota ctx__10517__auto__
                                &
                                [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/resourcequotas list or watch objects of kind ResourceQuota Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.ResourceQuotaList

list-namespaced-secret clj

(list-namespaced-secret ctx__10517__auto__
                        &
                        [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/secrets list or watch objects of kind Secret Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.SecretList

list-namespaced-service clj

(list-namespaced-service ctx__10517__auto__
                         &
                         [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/services list or watch objects of kind Service Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.ServiceList

list-namespaced-service-account clj

(list-namespaced-service-account ctx__10517__auto__
                                 &
                                 [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/serviceaccounts list or watch objects of kind ServiceAccount Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. - namespace: required string object name and auth scope, such as for teams and projects Returns v1.ServiceAccountList

list-node clj

(list-node ctx__10517__auto__ & [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/nodes list or watch objects of kind Node Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. Returns v1.NodeList

list-persistent-volume clj

(list-persistent-volume ctx__10517__auto__
                        &
                        [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/persistentvolumes list or watch objects of kind PersistentVolume Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. Returns v1.PersistentVolumeList

list-persistent-volume-claim-for-all-namespaces clj

(list-persistent-volume-claim-for-all-namespaces ctx__10517__auto__
                                                 &
                                                 [body?__10518__auto__
                                                  opts?__10519__auto__])

Calls GET on /api/v1/persistentvolumeclaims list or watch objects of kind PersistentVolumeClaim Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. Returns v1.PersistentVolumeClaimList

list-pod-for-all-namespaces clj

(list-pod-for-all-namespaces ctx__10517__auto__
                             &
                             [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/pods list or watch objects of kind Pod Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. Returns v1.PodList

list-pod-template-for-all-namespaces clj

(list-pod-template-for-all-namespaces ctx__10517__auto__
                                      &
                                      [body?__10518__auto__
                                       opts?__10519__auto__])

Calls GET on /api/v1/podtemplates list or watch objects of kind PodTemplate Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. Returns v1.PodTemplateList

list-replication-controller-for-all-namespaces clj

(list-replication-controller-for-all-namespaces ctx__10517__auto__
                                                &
                                                [body?__10518__auto__
                                                 opts?__10519__auto__])

Calls GET on /api/v1/replicationcontrollers list or watch objects of kind ReplicationController Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. Returns v1.ReplicationControllerList

list-resource-quota-for-all-namespaces clj

(list-resource-quota-for-all-namespaces ctx__10517__auto__
                                        &
                                        [body?__10518__auto__
                                         opts?__10519__auto__])

Calls GET on /api/v1/resourcequotas list or watch objects of kind ResourceQuota Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. Returns v1.ResourceQuotaList

list-secret-for-all-namespaces clj

(list-secret-for-all-namespaces ctx__10517__auto__
                                &
                                [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/secrets list or watch objects of kind Secret Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. Returns v1.SecretList

list-service-account-for-all-namespaces clj

(list-service-account-for-all-namespaces ctx__10517__auto__
                                         &
                                         [body?__10518__auto__
                                          opts?__10519__auto__])

Calls GET on /api/v1/serviceaccounts list or watch objects of kind ServiceAccount Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. Returns v1.ServiceAccountList

list-service-for-all-namespaces clj

(list-service-for-all-namespaces ctx__10517__auto__
                                 &
                                 [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/services list or watch objects of kind Service Parameters: - ctx: required server context Options: - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - include-uninitialized: optional boolean If true, partially initialized resources are included in the response. - limit: optional integer 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. - continue: optional string 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. Returns v1.ServiceList

make-context clj

patch-namespace clj

(patch-namespace ctx__10517__auto__
                 &
                 [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{name} partially update the specified Namespace Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - name: required string name of the Namespace Returns v1.Namespace

patch-namespace-status clj

(patch-namespace-status ctx__10517__auto__
                        &
                        [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{name}/status partially update status of the specified Namespace Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - name: required string name of the Namespace Returns v1.Namespace

patch-namespaced-config-map clj

(patch-namespaced-config-map ctx__10517__auto__
                             &
                             [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{namespace}/configmaps/{name} partially update the specified ConfigMap Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ConfigMap Returns v1.ConfigMap

patch-namespaced-endpoints clj

(patch-namespaced-endpoints ctx__10517__auto__
                            &
                            [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{namespace}/endpoints/{name} partially update the specified Endpoints Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Endpoints Returns v1.Endpoints

patch-namespaced-event clj

(patch-namespaced-event ctx__10517__auto__
                        &
                        [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{namespace}/events/{name} partially update the specified Event Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Event Returns v1.Event

patch-namespaced-limit-range clj

(patch-namespaced-limit-range ctx__10517__auto__
                              &
                              [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{namespace}/limitranges/{name} partially update the specified LimitRange Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the LimitRange Returns v1.LimitRange

patch-namespaced-persistent-volume-claim clj

(patch-namespaced-persistent-volume-claim ctx__10517__auto__
                                          &
                                          [body?__10518__auto__
                                           opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name} partially update the specified PersistentVolumeClaim Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the PersistentVolumeClaim Returns v1.PersistentVolumeClaim

patch-namespaced-persistent-volume-claim-status clj

(patch-namespaced-persistent-volume-claim-status ctx__10517__auto__
                                                 &
                                                 [body?__10518__auto__
                                                  opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}/status partially update status of the specified PersistentVolumeClaim Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the PersistentVolumeClaim Returns v1.PersistentVolumeClaim

patch-namespaced-pod clj

(patch-namespaced-pod ctx__10517__auto__
                      &
                      [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{namespace}/pods/{name} partially update the specified Pod Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Pod Returns v1.Pod

patch-namespaced-pod-status clj

(patch-namespaced-pod-status ctx__10517__auto__
                             &
                             [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{namespace}/pods/{name}/status partially update status of the specified Pod Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Pod Returns v1.Pod

patch-namespaced-pod-template clj

(patch-namespaced-pod-template ctx__10517__auto__
                               &
                               [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{namespace}/podtemplates/{name} partially update the specified PodTemplate Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the PodTemplate Returns v1.PodTemplate

patch-namespaced-replication-controller clj

(patch-namespaced-replication-controller ctx__10517__auto__
                                         &
                                         [body?__10518__auto__
                                          opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{namespace}/replicationcontrollers/{name} partially update the specified ReplicationController Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ReplicationController Returns v1.ReplicationController

patch-namespaced-replication-controller-scale clj

(patch-namespaced-replication-controller-scale ctx__10517__auto__
                                               &
                                               [body?__10518__auto__
                                                opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/scale partially update scale of the specified ReplicationController Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Scale Returns v1.Scale

patch-namespaced-replication-controller-status clj

(patch-namespaced-replication-controller-status ctx__10517__auto__
                                                &
                                                [body?__10518__auto__
                                                 opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/status partially update status of the specified ReplicationController Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ReplicationController Returns v1.ReplicationController

patch-namespaced-resource-quota clj

(patch-namespaced-resource-quota ctx__10517__auto__
                                 &
                                 [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{namespace}/resourcequotas/{name} partially update the specified ResourceQuota Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ResourceQuota Returns v1.ResourceQuota

patch-namespaced-resource-quota-status clj

(patch-namespaced-resource-quota-status ctx__10517__auto__
                                        &
                                        [body?__10518__auto__
                                         opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{namespace}/resourcequotas/{name}/status partially update status of the specified ResourceQuota Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ResourceQuota Returns v1.ResourceQuota

patch-namespaced-secret clj

(patch-namespaced-secret ctx__10517__auto__
                         &
                         [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{namespace}/secrets/{name} partially update the specified Secret Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Secret Returns v1.Secret

patch-namespaced-service clj

(patch-namespaced-service ctx__10517__auto__
                          &
                          [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{namespace}/services/{name} partially update the specified Service Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Service Returns v1.Service

patch-namespaced-service-account clj

(patch-namespaced-service-account ctx__10517__auto__
                                  &
                                  [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{namespace}/serviceaccounts/{name} partially update the specified ServiceAccount Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ServiceAccount Returns v1.ServiceAccount

patch-namespaced-service-status clj

(patch-namespaced-service-status ctx__10517__auto__
                                 &
                                 [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /api/v1/namespaces/{namespace}/services/{name}/status partially update status of the specified Service Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Service Returns v1.Service

patch-node clj

(patch-node ctx__10517__auto__ & [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /api/v1/nodes/{name} partially update the specified Node Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - name: required string name of the Node Returns v1.Node

patch-node-status clj

(patch-node-status ctx__10517__auto__
                   &
                   [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /api/v1/nodes/{name}/status partially update status of the specified Node Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - name: required string name of the Node Returns v1.Node

patch-persistent-volume clj

(patch-persistent-volume ctx__10517__auto__
                         &
                         [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /api/v1/persistentvolumes/{name} partially update the specified PersistentVolume Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - name: required string name of the PersistentVolume Returns v1.PersistentVolume

patch-persistent-volume-status clj

(patch-persistent-volume-status ctx__10517__auto__
                                &
                                [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /api/v1/persistentvolumes/{name}/status partially update status of the specified PersistentVolume Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - name: required string name of the PersistentVolume Returns v1.PersistentVolume

read-component-status clj

(read-component-status ctx__10517__auto__
                       &
                       [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/componentstatuses/{name} read the specified ComponentStatus Parameters: - ctx: required server context Options: - name: required string name of the ComponentStatus Returns v1.ComponentStatus

read-namespace clj

(read-namespace ctx__10517__auto__
                &
                [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{name} read the specified Namespace Parameters: - ctx: required server context Options: - export: optional boolean Should this value be exported. Export strips fields that a user can not specify. - exact: optional boolean Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. - name: required string name of the Namespace Returns v1.Namespace

read-namespace-status clj

(read-namespace-status ctx__10517__auto__
                       &
                       [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{name}/status read status of the specified Namespace Parameters: - ctx: required server context Options: - name: required string name of the Namespace Returns v1.Namespace

read-namespaced-config-map clj

(read-namespaced-config-map ctx__10517__auto__
                            &
                            [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/configmaps/{name} read the specified ConfigMap Parameters: - ctx: required server context Options: - export: optional boolean Should this value be exported. Export strips fields that a user can not specify. - exact: optional boolean Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ConfigMap Returns v1.ConfigMap

read-namespaced-endpoints clj

(read-namespaced-endpoints ctx__10517__auto__
                           &
                           [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/endpoints/{name} read the specified Endpoints Parameters: - ctx: required server context Options: - export: optional boolean Should this value be exported. Export strips fields that a user can not specify. - exact: optional boolean Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Endpoints Returns v1.Endpoints

read-namespaced-event clj

(read-namespaced-event ctx__10517__auto__
                       &
                       [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/events/{name} read the specified Event Parameters: - ctx: required server context Options: - export: optional boolean Should this value be exported. Export strips fields that a user can not specify. - exact: optional boolean Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Event Returns v1.Event

read-namespaced-limit-range clj

(read-namespaced-limit-range ctx__10517__auto__
                             &
                             [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/limitranges/{name} read the specified LimitRange Parameters: - ctx: required server context Options: - export: optional boolean Should this value be exported. Export strips fields that a user can not specify. - exact: optional boolean Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the LimitRange Returns v1.LimitRange

read-namespaced-persistent-volume-claim clj

(read-namespaced-persistent-volume-claim ctx__10517__auto__
                                         &
                                         [body?__10518__auto__
                                          opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name} read the specified PersistentVolumeClaim Parameters: - ctx: required server context Options: - export: optional boolean Should this value be exported. Export strips fields that a user can not specify. - exact: optional boolean Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the PersistentVolumeClaim Returns v1.PersistentVolumeClaim

read-namespaced-persistent-volume-claim-status clj

(read-namespaced-persistent-volume-claim-status ctx__10517__auto__
                                                &
                                                [body?__10518__auto__
                                                 opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}/status read status of the specified PersistentVolumeClaim Parameters: - ctx: required server context Options: - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the PersistentVolumeClaim Returns v1.PersistentVolumeClaim

read-namespaced-pod clj

(read-namespaced-pod ctx__10517__auto__
                     &
                     [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/pods/{name} read the specified Pod Parameters: - ctx: required server context Options: - export: optional boolean Should this value be exported. Export strips fields that a user can not specify. - exact: optional boolean Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Pod Returns v1.Pod

read-namespaced-pod-log clj

(read-namespaced-pod-log ctx__10517__auto__
                         &
                         [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/pods/{name}/log read log of the specified Pod Parameters: - ctx: required server context Options: - container: optional string The container for which to stream logs. Defaults to only container if there is one container in the pod. - follow: optional boolean Follow the log stream of the pod. Defaults to false. - previous: optional boolean Return previous terminated container logs. Defaults to false. - since-seconds: optional integer 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. - timestamps: optional boolean If true, add an RFC3339 or RFC3339Nano timestamp at the beginning of every line of log output. Defaults to false. - tail-lines: optional integer 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 - limit-bytes: optional integer 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. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Pod Returns string

read-namespaced-pod-status clj

(read-namespaced-pod-status ctx__10517__auto__
                            &
                            [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/pods/{name}/status read status of the specified Pod Parameters: - ctx: required server context Options: - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Pod Returns v1.Pod

read-namespaced-pod-template clj

(read-namespaced-pod-template ctx__10517__auto__
                              &
                              [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/podtemplates/{name} read the specified PodTemplate Parameters: - ctx: required server context Options: - export: optional boolean Should this value be exported. Export strips fields that a user can not specify. - exact: optional boolean Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the PodTemplate Returns v1.PodTemplate

read-namespaced-replication-controller clj

(read-namespaced-replication-controller ctx__10517__auto__
                                        &
                                        [body?__10518__auto__
                                         opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/replicationcontrollers/{name} read the specified ReplicationController Parameters: - ctx: required server context Options: - export: optional boolean Should this value be exported. Export strips fields that a user can not specify. - exact: optional boolean Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ReplicationController Returns v1.ReplicationController

read-namespaced-replication-controller-scale clj

(read-namespaced-replication-controller-scale ctx__10517__auto__
                                              &
                                              [body?__10518__auto__
                                               opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/scale read scale of the specified ReplicationController Parameters: - ctx: required server context Options: - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Scale Returns v1.Scale

read-namespaced-replication-controller-status clj

(read-namespaced-replication-controller-status ctx__10517__auto__
                                               &
                                               [body?__10518__auto__
                                                opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/status read status of the specified ReplicationController Parameters: - ctx: required server context Options: - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ReplicationController Returns v1.ReplicationController

read-namespaced-resource-quota clj

(read-namespaced-resource-quota ctx__10517__auto__
                                &
                                [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/resourcequotas/{name} read the specified ResourceQuota Parameters: - ctx: required server context Options: - export: optional boolean Should this value be exported. Export strips fields that a user can not specify. - exact: optional boolean Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ResourceQuota Returns v1.ResourceQuota

read-namespaced-resource-quota-status clj

(read-namespaced-resource-quota-status ctx__10517__auto__
                                       &
                                       [body?__10518__auto__
                                        opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/resourcequotas/{name}/status read status of the specified ResourceQuota Parameters: - ctx: required server context Options: - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ResourceQuota Returns v1.ResourceQuota

read-namespaced-secret clj

(read-namespaced-secret ctx__10517__auto__
                        &
                        [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/secrets/{name} read the specified Secret Parameters: - ctx: required server context Options: - export: optional boolean Should this value be exported. Export strips fields that a user can not specify. - exact: optional boolean Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Secret Returns v1.Secret

read-namespaced-service clj

(read-namespaced-service ctx__10517__auto__
                         &
                         [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/services/{name} read the specified Service Parameters: - ctx: required server context Options: - export: optional boolean Should this value be exported. Export strips fields that a user can not specify. - exact: optional boolean Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Service Returns v1.Service

read-namespaced-service-account clj

(read-namespaced-service-account ctx__10517__auto__
                                 &
                                 [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/serviceaccounts/{name} read the specified ServiceAccount Parameters: - ctx: required server context Options: - export: optional boolean Should this value be exported. Export strips fields that a user can not specify. - exact: optional boolean Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ServiceAccount Returns v1.ServiceAccount

read-namespaced-service-status clj

(read-namespaced-service-status ctx__10517__auto__
                                &
                                [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/namespaces/{namespace}/services/{name}/status read status of the specified Service Parameters: - ctx: required server context Options: - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Service Returns v1.Service

read-node clj

(read-node ctx__10517__auto__ & [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/nodes/{name} read the specified Node Parameters: - ctx: required server context Options: - export: optional boolean Should this value be exported. Export strips fields that a user can not specify. - exact: optional boolean Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. - name: required string name of the Node Returns v1.Node

read-node-status clj

(read-node-status ctx__10517__auto__
                  &
                  [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/nodes/{name}/status read status of the specified Node Parameters: - ctx: required server context Options: - name: required string name of the Node Returns v1.Node

read-persistent-volume clj

(read-persistent-volume ctx__10517__auto__
                        &
                        [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/persistentvolumes/{name} read the specified PersistentVolume Parameters: - ctx: required server context Options: - export: optional boolean Should this value be exported. Export strips fields that a user can not specify. - exact: optional boolean Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. - name: required string name of the PersistentVolume Returns v1.PersistentVolume

read-persistent-volume-status clj

(read-persistent-volume-status ctx__10517__auto__
                               &
                               [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /api/v1/persistentvolumes/{name}/status read status of the specified PersistentVolume Parameters: - ctx: required server context Options: - name: required string name of the PersistentVolume Returns v1.PersistentVolume

replace-namespace clj

(replace-namespace ctx__10517__auto__
                   &
                   [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{name} replace the specified Namespace Parameters: - ctx: required server context - body: required v1.Namespace Options: - body: required v1.Namespace - name: required string name of the Namespace Returns v1.Namespace

replace-namespace-finalize clj

(replace-namespace-finalize ctx__10517__auto__
                            &
                            [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{name}/finalize replace finalize of the specified Namespace Parameters: - ctx: required server context - body: required v1.Namespace Options: - body: required v1.Namespace - name: required string name of the Namespace Returns v1.Namespace

replace-namespace-status clj

(replace-namespace-status ctx__10517__auto__
                          &
                          [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{name}/status replace status of the specified Namespace Parameters: - ctx: required server context - body: required v1.Namespace Options: - body: required v1.Namespace - name: required string name of the Namespace Returns v1.Namespace

replace-namespaced-config-map clj

(replace-namespaced-config-map ctx__10517__auto__
                               &
                               [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{namespace}/configmaps/{name} replace the specified ConfigMap Parameters: - ctx: required server context - body: required v1.ConfigMap Options: - body: required v1.ConfigMap - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ConfigMap Returns v1.ConfigMap

replace-namespaced-endpoints clj

(replace-namespaced-endpoints ctx__10517__auto__
                              &
                              [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{namespace}/endpoints/{name} replace the specified Endpoints Parameters: - ctx: required server context - body: required v1.Endpoints Options: - body: required v1.Endpoints - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Endpoints Returns v1.Endpoints

replace-namespaced-event clj

(replace-namespaced-event ctx__10517__auto__
                          &
                          [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{namespace}/events/{name} replace the specified Event Parameters: - ctx: required server context - body: required v1.Event Options: - body: required v1.Event - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Event Returns v1.Event

replace-namespaced-limit-range clj

(replace-namespaced-limit-range ctx__10517__auto__
                                &
                                [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{namespace}/limitranges/{name} replace the specified LimitRange Parameters: - ctx: required server context - body: required v1.LimitRange Options: - body: required v1.LimitRange - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the LimitRange Returns v1.LimitRange

replace-namespaced-persistent-volume-claim clj

(replace-namespaced-persistent-volume-claim ctx__10517__auto__
                                            &
                                            [body?__10518__auto__
                                             opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name} replace the specified PersistentVolumeClaim Parameters: - ctx: required server context - body: required v1.PersistentVolumeClaim Options: - body: required v1.PersistentVolumeClaim - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the PersistentVolumeClaim Returns v1.PersistentVolumeClaim

replace-namespaced-persistent-volume-claim-status clj

(replace-namespaced-persistent-volume-claim-status ctx__10517__auto__
                                                   &
                                                   [body?__10518__auto__
                                                    opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}/status replace status of the specified PersistentVolumeClaim Parameters: - ctx: required server context - body: required v1.PersistentVolumeClaim Options: - body: required v1.PersistentVolumeClaim - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the PersistentVolumeClaim Returns v1.PersistentVolumeClaim

replace-namespaced-pod clj

(replace-namespaced-pod ctx__10517__auto__
                        &
                        [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{namespace}/pods/{name} replace the specified Pod Parameters: - ctx: required server context - body: required v1.Pod Options: - body: required v1.Pod - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Pod Returns v1.Pod

replace-namespaced-pod-status clj

(replace-namespaced-pod-status ctx__10517__auto__
                               &
                               [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{namespace}/pods/{name}/status replace status of the specified Pod Parameters: - ctx: required server context - body: required v1.Pod Options: - body: required v1.Pod - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Pod Returns v1.Pod

replace-namespaced-pod-template clj

(replace-namespaced-pod-template ctx__10517__auto__
                                 &
                                 [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{namespace}/podtemplates/{name} replace the specified PodTemplate Parameters: - ctx: required server context - body: required v1.PodTemplate Options: - body: required v1.PodTemplate - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the PodTemplate Returns v1.PodTemplate

replace-namespaced-replication-controller clj

(replace-namespaced-replication-controller ctx__10517__auto__
                                           &
                                           [body?__10518__auto__
                                            opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{namespace}/replicationcontrollers/{name} replace the specified ReplicationController Parameters: - ctx: required server context - body: required v1.ReplicationController Options: - body: required v1.ReplicationController - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ReplicationController Returns v1.ReplicationController

replace-namespaced-replication-controller-scale clj

(replace-namespaced-replication-controller-scale ctx__10517__auto__
                                                 &
                                                 [body?__10518__auto__
                                                  opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/scale replace scale of the specified ReplicationController Parameters: - ctx: required server context - body: required v1.Scale Options: - body: required v1.Scale - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Scale Returns v1.Scale

replace-namespaced-replication-controller-status clj

(replace-namespaced-replication-controller-status ctx__10517__auto__
                                                  &
                                                  [body?__10518__auto__
                                                   opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/status replace status of the specified ReplicationController Parameters: - ctx: required server context - body: required v1.ReplicationController Options: - body: required v1.ReplicationController - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ReplicationController Returns v1.ReplicationController

replace-namespaced-resource-quota clj

(replace-namespaced-resource-quota ctx__10517__auto__
                                   &
                                   [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{namespace}/resourcequotas/{name} replace the specified ResourceQuota Parameters: - ctx: required server context - body: required v1.ResourceQuota Options: - body: required v1.ResourceQuota - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ResourceQuota Returns v1.ResourceQuota

replace-namespaced-resource-quota-status clj

(replace-namespaced-resource-quota-status ctx__10517__auto__
                                          &
                                          [body?__10518__auto__
                                           opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{namespace}/resourcequotas/{name}/status replace status of the specified ResourceQuota Parameters: - ctx: required server context - body: required v1.ResourceQuota Options: - body: required v1.ResourceQuota - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ResourceQuota Returns v1.ResourceQuota

replace-namespaced-secret clj

(replace-namespaced-secret ctx__10517__auto__
                           &
                           [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{namespace}/secrets/{name} replace the specified Secret Parameters: - ctx: required server context - body: required v1.Secret Options: - body: required v1.Secret - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Secret Returns v1.Secret

replace-namespaced-service clj

(replace-namespaced-service ctx__10517__auto__
                            &
                            [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{namespace}/services/{name} replace the specified Service Parameters: - ctx: required server context - body: required v1.Service Options: - body: required v1.Service - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Service Returns v1.Service

replace-namespaced-service-account clj

(replace-namespaced-service-account ctx__10517__auto__
                                    &
                                    [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{namespace}/serviceaccounts/{name} replace the specified ServiceAccount Parameters: - ctx: required server context - body: required v1.ServiceAccount Options: - body: required v1.ServiceAccount - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ServiceAccount Returns v1.ServiceAccount

replace-namespaced-service-status clj

(replace-namespaced-service-status ctx__10517__auto__
                                   &
                                   [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/namespaces/{namespace}/services/{name}/status replace status of the specified Service Parameters: - ctx: required server context - body: required v1.Service Options: - body: required v1.Service - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Service Returns v1.Service

replace-node clj

(replace-node ctx__10517__auto__ & [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/nodes/{name} replace the specified Node Parameters: - ctx: required server context - body: required v1.Node Options: - body: required v1.Node - name: required string name of the Node Returns v1.Node

replace-node-status clj

(replace-node-status ctx__10517__auto__
                     &
                     [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/nodes/{name}/status replace status of the specified Node Parameters: - ctx: required server context - body: required v1.Node Options: - body: required v1.Node - name: required string name of the Node Returns v1.Node

replace-persistent-volume clj

(replace-persistent-volume ctx__10517__auto__
                           &
                           [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/persistentvolumes/{name} replace the specified PersistentVolume Parameters: - ctx: required server context - body: required v1.PersistentVolume Options: - body: required v1.PersistentVolume - name: required string name of the PersistentVolume Returns v1.PersistentVolume

replace-persistent-volume-status clj

(replace-persistent-volume-status ctx__10517__auto__
                                  &
                                  [body?__10518__auto__ opts?__10519__auto__])

Calls PUT on /api/v1/persistentvolumes/{name}/status replace status of the specified PersistentVolume Parameters: - ctx: required server context - body: required v1.PersistentVolume Options: - body: required v1.PersistentVolume - name: required string name of the PersistentVolume Returns v1.PersistentVolume