kubernetes.api.kedash-v1alpha1 — nubank/kubernetes-api 1.6.0

create-namespaced-scaled-object clj

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

Calls POST on /apis/keda.sh/v1alpha1/namespaces/{namespace}/scaledobjects Create a ScaledObject Parameters: - ctx: required server context - body: required v1alpha1.ScaledObject Options: - body: required v1alpha1.ScaledObject - namespace: required string object name and auth scope, such as for teams and projects Returns

delete-namespaced-scaled-object clj

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

Calls DELETE on /apis/keda.sh/v1alpha1/namespaces/{namespace}/scaledobjects/{name} delete a ScaledObject Parameters: - ctx: required server context - body: required v1.DeleteOptions_v2 Options: - body: required v1.DeleteOptions_v2 - 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

deletecollection-namespaced-scaled-object clj

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

Calls DELETE on /apis/keda.sh/v1alpha1/namespaces/{namespace}/scaledobjects delete collection of ScaledObject Parameters: - ctx: required server context - body: required Options: - 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. - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - 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. - namespace: required string object name and auth scope, such as for teams and projects Returns

list-namespaced-scaled-object clj

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

Calls GET on /apis/keda.sh/v1alpha1/namespaces/{namespace}/scaledobjects Get ScaledObject List Parameters: - ctx: required server context Options: - namespace: required string object name and auth scope, such as for teams and projects - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - label-selector: optional string A selector to restrict the list of returned objects by their labels. Defaults to everything. - 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

make-context clj

read-namespaced-scaled-object clj

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

Calls GET on /apis/keda.sh/v1alpha1/namespaces/{namespace}/scaledobjects/{name} Get specific ScaledObject 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

replace-namespaced-scaled-object clj

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

Calls PUT on /apis/keda.sh/v1alpha1/namespaces/{namespace}/scaledobjects/{name} Replace the specified ScaledObject Parameters: - ctx: required server context - body: required v1alpha1.ScaledObject Options: - body: required v1alpha1.ScaledObject - namespace: required string object name and auth scope, such as for teams and projects - name: required string name of the Pod Returns