kubernetes.api.extensions-v1beta1 — nubank/kubernetes-api 1.6.0

create-namespaced-daemon-set clj

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

Calls POST on /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets create a DaemonSet Parameters: - ctx: required server context - body: required v1beta1.DaemonSet Options: - body: required v1beta1.DaemonSet - namespace: required string object name and auth scope, such as for teams and projects Returns v1beta1.DaemonSet

create-namespaced-deployment clj

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

Calls POST on /apis/extensions/v1beta1/namespaces/{namespace}/deployments create a Deployment Parameters: - ctx: required server context - body: required v1beta1.Deployment Options: - body: required v1beta1.Deployment - namespace: required string object name and auth scope, such as for teams and projects Returns v1beta1.Deployment

create-namespaced-deployment-rollback clj

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

Calls POST on /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}/rollback create rollback of a Deployment Parameters: - ctx: required server context - body: required v1beta1.DeploymentRollback Options: - body: required v1beta1.DeploymentRollback - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the DeploymentRollback Returns v1beta1.DeploymentRollback

create-namespaced-ingress clj

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

Calls POST on /apis/extensions/v1beta1/namespaces/{namespace}/ingresses create an Ingress Parameters: - ctx: required server context - body: required v1beta1.Ingress Options: - body: required v1beta1.Ingress - namespace: required string object name and auth scope, such as for teams and projects Returns v1beta1.Ingress

create-namespaced-network-policy clj

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

Calls POST on /apis/extensions/v1beta1/namespaces/{namespace}/networkpolicies create a NetworkPolicy Parameters: - ctx: required server context - body: required v1beta1.NetworkPolicy Options: - body: required v1beta1.NetworkPolicy - namespace: required string object name and auth scope, such as for teams and projects Returns v1beta1.NetworkPolicy

create-namespaced-replica-set clj

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

Calls POST on /apis/extensions/v1beta1/namespaces/{namespace}/replicasets create a ReplicaSet Parameters: - ctx: required server context - body: required v1beta1.ReplicaSet Options: - body: required v1beta1.ReplicaSet - namespace: required string object name and auth scope, such as for teams and projects Returns v1beta1.ReplicaSet

create-pod-security-policy clj

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

Calls POST on /apis/extensions/v1beta1/podsecuritypolicies create a PodSecurityPolicy Parameters: - ctx: required server context - body: required v1beta1.PodSecurityPolicy Options: - body: required v1beta1.PodSecurityPolicy Returns v1beta1.PodSecurityPolicy

delete-namespaced-daemon-set clj

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

Calls DELETE on /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets/{name} delete a DaemonSet 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 DaemonSet Returns v1.Status

delete-namespaced-deployment clj

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

Calls DELETE on /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name} delete a Deployment 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 Deployment Returns v1.Status

delete-namespaced-ingress clj

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

Calls DELETE on /apis/extensions/v1beta1/namespaces/{namespace}/ingresses/{name} delete an Ingress 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 Ingress Returns v1.Status

delete-namespaced-network-policy clj

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

Calls DELETE on /apis/extensions/v1beta1/namespaces/{namespace}/networkpolicies/{name} delete a NetworkPolicy 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 NetworkPolicy Returns v1.Status

delete-namespaced-replica-set clj

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

Calls DELETE on /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name} delete a ReplicaSet 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 ReplicaSet Returns v1.Status

delete-pod-security-policy clj

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

Calls DELETE on /apis/extensions/v1beta1/podsecuritypolicies/{name} delete a PodSecurityPolicy 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 PodSecurityPolicy Returns v1.Status

deletecollection-namespaced-daemon-set clj

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

Calls DELETE on /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets delete collection of DaemonSet 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-deployment clj

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

Calls DELETE on /apis/extensions/v1beta1/namespaces/{namespace}/deployments delete collection of Deployment 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-ingress clj

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

Calls DELETE on /apis/extensions/v1beta1/namespaces/{namespace}/ingresses delete collection of Ingress 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-network-policy clj

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

Calls DELETE on /apis/extensions/v1beta1/namespaces/{namespace}/networkpolicies delete collection of NetworkPolicy 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-replica-set clj

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

Calls DELETE on /apis/extensions/v1beta1/namespaces/{namespace}/replicasets delete collection of ReplicaSet 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-pod-security-policy clj

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

Calls DELETE on /apis/extensions/v1beta1/podsecuritypolicies delete collection of PodSecurityPolicy 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 /apis/extensions/v1beta1 get available resources Parameters: - ctx: required server context Returns

list-daemon-set-for-all-namespaces clj

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

Calls GET on /apis/extensions/v1beta1/daemonsets list or watch objects of kind DaemonSet 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 v1beta1.DaemonSetList

list-deployment-for-all-namespaces clj

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

Calls GET on /apis/extensions/v1beta1/deployments list or watch objects of kind Deployment 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 v1beta1.DeploymentList

list-ingress-for-all-namespaces clj

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

Calls GET on /apis/extensions/v1beta1/ingresses list or watch objects of kind Ingress 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 v1beta1.IngressList

list-namespaced-daemon-set clj

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

Calls GET on /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets list or watch objects of kind DaemonSet 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 v1beta1.DaemonSetList

list-namespaced-deployment clj

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

Calls GET on /apis/extensions/v1beta1/namespaces/{namespace}/deployments list or watch objects of kind Deployment 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 v1beta1.DeploymentList

list-namespaced-ingress clj

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

Calls GET on /apis/extensions/v1beta1/namespaces/{namespace}/ingresses list or watch objects of kind Ingress 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 v1beta1.IngressList

list-namespaced-network-policy clj

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

Calls GET on /apis/extensions/v1beta1/namespaces/{namespace}/networkpolicies list or watch objects of kind NetworkPolicy 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 v1beta1.NetworkPolicyList

list-namespaced-replica-set clj

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

Calls GET on /apis/extensions/v1beta1/namespaces/{namespace}/replicasets list or watch objects of kind ReplicaSet 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 v1beta1.ReplicaSetList

list-network-policy-for-all-namespaces clj

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

Calls GET on /apis/extensions/v1beta1/networkpolicies list or watch objects of kind NetworkPolicy 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 v1beta1.NetworkPolicyList

list-pod-security-policy clj

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

Calls GET on /apis/extensions/v1beta1/podsecuritypolicies list or watch objects of kind PodSecurityPolicy 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 v1beta1.PodSecurityPolicyList

list-replica-set-for-all-namespaces clj

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

Calls GET on /apis/extensions/v1beta1/replicasets list or watch objects of kind ReplicaSet 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 v1beta1.ReplicaSetList

make-context clj

patch-namespaced-daemon-set clj

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

Calls PATCH on /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets/{name} partially update the specified DaemonSet 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 DaemonSet Returns v1beta1.DaemonSet

patch-namespaced-daemon-set-status clj

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

Calls PATCH on /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets/{name}/status partially update status of the specified DaemonSet 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 DaemonSet Returns v1beta1.DaemonSet

patch-namespaced-deployment clj

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

Calls PATCH on /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name} partially update the specified Deployment 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 Deployment Returns v1beta1.Deployment

patch-namespaced-deployment-scale clj

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

Calls PATCH on /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}/scale partially update scale of the specified Deployment 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 v1beta1.Scale

patch-namespaced-deployment-status clj

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

Calls PATCH on /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}/status partially update status of the specified Deployment 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 Deployment Returns v1beta1.Deployment

patch-namespaced-ingress clj

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

Calls PATCH on /apis/extensions/v1beta1/namespaces/{namespace}/ingresses/{name} partially update the specified Ingress 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 Ingress Returns v1beta1.Ingress

patch-namespaced-ingress-status clj

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

Calls PATCH on /apis/extensions/v1beta1/namespaces/{namespace}/ingresses/{name}/status partially update status of the specified Ingress 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 Ingress Returns v1beta1.Ingress

patch-namespaced-network-policy clj

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

Calls PATCH on /apis/extensions/v1beta1/namespaces/{namespace}/networkpolicies/{name} partially update the specified NetworkPolicy 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 NetworkPolicy Returns v1beta1.NetworkPolicy

patch-namespaced-replica-set clj

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

Calls PATCH on /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name} partially update the specified ReplicaSet 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 ReplicaSet Returns v1beta1.ReplicaSet

patch-namespaced-replica-set-scale clj

(patch-namespaced-replica-set-scale ctx__10517__auto__
                                    &
                                    [body?__10518__auto__ opts?__10519__auto__])

Calls PATCH on /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}/scale partially update scale of the specified ReplicaSet 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 v1beta1.Scale

patch-namespaced-replica-set-status clj

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

Calls PATCH on /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}/status partially update status of the specified ReplicaSet 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 ReplicaSet Returns v1beta1.ReplicaSet

patch-namespaced-replication-controller-dummy-scale clj

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

Calls PATCH on /apis/extensions/v1beta1/namespaces/{namespace}/replicationcontrollers/{name}/scale partially update scale of the specified ReplicationControllerDummy 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 v1beta1.Scale

patch-pod-security-policy clj

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

Calls PATCH on /apis/extensions/v1beta1/podsecuritypolicies/{name} partially update the specified PodSecurityPolicy Parameters: - ctx: required server context - body: required v1.Patch Options: - body: required v1.Patch - name: required string name of the PodSecurityPolicy Returns v1beta1.PodSecurityPolicy

read-namespaced-daemon-set clj

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

Calls GET on /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets/{name} read the specified DaemonSet 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 DaemonSet Returns v1beta1.DaemonSet

read-namespaced-daemon-set-status clj

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

Calls GET on /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets/{name}/status read status of the specified DaemonSet 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 DaemonSet Returns v1beta1.DaemonSet

read-namespaced-deployment clj

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

Calls GET on /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name} read the specified Deployment 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 Deployment Returns v1beta1.Deployment

read-namespaced-deployment-scale clj

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

Calls GET on /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}/scale read scale of the specified Deployment 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 v1beta1.Scale

read-namespaced-deployment-status clj

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

Calls GET on /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}/status read status of the specified Deployment 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 Deployment Returns v1beta1.Deployment

read-namespaced-ingress clj

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

Calls GET on /apis/extensions/v1beta1/namespaces/{namespace}/ingresses/{name} read the specified Ingress 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 Ingress Returns v1beta1.Ingress

read-namespaced-ingress-status clj

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

Calls GET on /apis/extensions/v1beta1/namespaces/{namespace}/ingresses/{name}/status read status of the specified Ingress 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 Ingress Returns v1beta1.Ingress

read-namespaced-network-policy clj

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

Calls GET on /apis/extensions/v1beta1/namespaces/{namespace}/networkpolicies/{name} read the specified NetworkPolicy 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 NetworkPolicy Returns v1beta1.NetworkPolicy

read-namespaced-replica-set clj

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

Calls GET on /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name} read the specified ReplicaSet 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 ReplicaSet Returns v1beta1.ReplicaSet

read-namespaced-replica-set-scale clj

(read-namespaced-replica-set-scale ctx__10517__auto__
                                   &
                                   [body?__10518__auto__ opts?__10519__auto__])

Calls GET on /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}/scale read scale of the specified ReplicaSet 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 v1beta1.Scale

read-namespaced-replica-set-status clj

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

Calls GET on /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}/status read status of the specified ReplicaSet 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 ReplicaSet Returns v1beta1.ReplicaSet

read-namespaced-replication-controller-dummy-scale clj

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

Calls GET on /apis/extensions/v1beta1/namespaces/{namespace}/replicationcontrollers/{name}/scale read scale of the specified ReplicationControllerDummy 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 v1beta1.Scale

read-pod-security-policy clj

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

Calls GET on /apis/extensions/v1beta1/podsecuritypolicies/{name} read the specified PodSecurityPolicy 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 PodSecurityPolicy Returns v1beta1.PodSecurityPolicy

replace-namespaced-daemon-set clj

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

Calls PUT on /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets/{name} replace the specified DaemonSet Parameters: - ctx: required server context - body: required v1beta1.DaemonSet Options: - body: required v1beta1.DaemonSet - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the DaemonSet Returns v1beta1.DaemonSet

replace-namespaced-daemon-set-status clj

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

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

replace-namespaced-deployment clj

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

Calls PUT on /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name} replace the specified Deployment Parameters: - ctx: required server context - body: required v1beta1.Deployment Options: - body: required v1beta1.Deployment - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Deployment Returns v1beta1.Deployment

replace-namespaced-deployment-scale clj

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

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

replace-namespaced-deployment-status clj

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

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

replace-namespaced-ingress clj

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

Calls PUT on /apis/extensions/v1beta1/namespaces/{namespace}/ingresses/{name} replace the specified Ingress Parameters: - ctx: required server context - body: required v1beta1.Ingress Options: - body: required v1beta1.Ingress - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Ingress Returns v1beta1.Ingress

replace-namespaced-ingress-status clj

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

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

replace-namespaced-network-policy clj

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

Calls PUT on /apis/extensions/v1beta1/namespaces/{namespace}/networkpolicies/{name} replace the specified NetworkPolicy Parameters: - ctx: required server context - body: required v1beta1.NetworkPolicy Options: - body: required v1beta1.NetworkPolicy - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the NetworkPolicy Returns v1beta1.NetworkPolicy

replace-namespaced-replica-set clj

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

Calls PUT on /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name} replace the specified ReplicaSet Parameters: - ctx: required server context - body: required v1beta1.ReplicaSet Options: - body: required v1beta1.ReplicaSet - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the ReplicaSet Returns v1beta1.ReplicaSet

replace-namespaced-replica-set-scale clj

(replace-namespaced-replica-set-scale ctx__10517__auto__
                                      &
                                      [body?__10518__auto__
                                       opts?__10519__auto__])

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

replace-namespaced-replica-set-status clj

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

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

replace-namespaced-replication-controller-dummy-scale clj

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

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

replace-pod-security-policy clj

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

Calls PUT on /apis/extensions/v1beta1/podsecuritypolicies/{name} replace the specified PodSecurityPolicy Parameters: - ctx: required server context - body: required v1beta1.PodSecurityPolicy Options: - body: required v1beta1.PodSecurityPolicy - name: required string name of the PodSecurityPolicy Returns v1beta1.PodSecurityPolicy