kubernetes.api.networking-k8s-io-v1 — nubank/kubernetes-api 1.8.0

create-networking-v1ingress-class clj

(create-networking-v1ingress-class ctx__10944__auto__
                                   &
                                   [body?__10945__auto__ opts?__10946__auto__])

Calls POST on /apis/networking.k8s.io/v1/ingressclasses create an IngressClass Parameters: - ctx: required server context - body: required Options: - body: required
- dry-run: optional string When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed - field-manager: optional string fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. Returns

create-networking-v1namespaced-ingress clj

(create-networking-v1namespaced-ingress ctx__10944__auto__
                                        &
                                        [body?__10945__auto__
                                         opts?__10946__auto__])

Calls POST on /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses create an Ingress Parameters: - ctx: required server context - body: required Options: - namespace: required string object name and auth scope, such as for teams and projects - body: required
- dry-run: optional string When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed - field-manager: optional string fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. Returns

create-networking-v1namespaced-network-policy clj

(create-networking-v1namespaced-network-policy ctx__10944__auto__
                                               &
                                               [body?__10945__auto__
                                                opts?__10946__auto__])

Calls POST on /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies create a NetworkPolicy Parameters: - ctx: required server context - body: required Options: - namespace: required string object name and auth scope, such as for teams and projects - body: required
- dry-run: optional string When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed - field-manager: optional string fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. Returns

delete-networking-v1collection-ingress-class clj

(delete-networking-v1collection-ingress-class ctx__10944__auto__
                                              &
                                              [body?__10945__auto__
                                               opts?__10946__auto__])

Calls DELETE on /apis/networking.k8s.io/v1/ingressclasses delete collection of IngressClass Parameters: - ctx: required server context - body: required Options: - body: optional
- 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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".

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. - dry-run: optional string When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - 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. - 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. - 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. - resource-version-match: optional string resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.

Defaults to unset Returns

delete-networking-v1collection-namespaced-ingress clj

(delete-networking-v1collection-namespaced-ingress ctx__10944__auto__
                                                   &
                                                   [body?__10945__auto__
                                                    opts?__10946__auto__])

Calls DELETE on /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses delete collection of Ingress Parameters: - ctx: required server context - body: required Options: - namespace: required string object name and auth scope, such as for teams and projects - body: optional
- 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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".

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. - dry-run: optional string When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - 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. - 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. - 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. - resource-version-match: optional string resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.

Defaults to unset Returns

delete-networking-v1collection-namespaced-network-policy clj

(delete-networking-v1collection-namespaced-network-policy
  ctx__10944__auto__
  &
  [body?__10945__auto__ opts?__10946__auto__])

Calls DELETE on /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies delete collection of NetworkPolicy Parameters: - ctx: required server context - body: required Options: - namespace: required string object name and auth scope, such as for teams and projects - body: optional
- 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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".

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. - dry-run: optional string When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed - field-selector: optional string A selector to restrict the list of returned objects by their fields. Defaults to everything. - 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. - 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. - 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. - resource-version-match: optional string resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.

Defaults to unset Returns

delete-networking-v1ingress-class clj

(delete-networking-v1ingress-class ctx__10944__auto__
                                   &
                                   [body?__10945__auto__ opts?__10946__auto__])

Calls DELETE on /apis/networking.k8s.io/v1/ingressclasses/{name} delete an IngressClass Parameters: - ctx: required server context - body: required Options: - name: required string name of the IngressClass - body: optional
- dry-run: optional string When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed - 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. Returns

delete-networking-v1namespaced-ingress clj

(delete-networking-v1namespaced-ingress ctx__10944__auto__
                                        &
                                        [body?__10945__auto__
                                         opts?__10946__auto__])

Calls DELETE on /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name} delete an Ingress Parameters: - ctx: required server context - body: required Options: - name: required string name of the Ingress - namespace: required string object name and auth scope, such as for teams and projects - body: optional
- dry-run: optional string When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed - 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. Returns

delete-networking-v1namespaced-network-policy clj

(delete-networking-v1namespaced-network-policy ctx__10944__auto__
                                               &
                                               [body?__10945__auto__
                                                opts?__10946__auto__])

Calls DELETE on /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name} delete a NetworkPolicy Parameters: - ctx: required server context - body: required Options: - name: required string name of the NetworkPolicy - namespace: required string object name and auth scope, such as for teams and projects - body: optional
- dry-run: optional string When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed - 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. Returns

list-networking-v1ingress-class clj

(list-networking-v1ingress-class ctx__10944__auto__
                                 &
                                 [body?__10945__auto__ opts?__10946__auto__])

Calls GET on /apis/networking.k8s.io/v1/ingressclasses list or watch objects of kind IngressClass Parameters: - ctx: required server context Options: - allow-watch-bookmarks: optional boolean allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored. - 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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".

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. - resource-version-match: optional string resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.

Defaults to unset Returns

list-networking-v1ingress-for-all-namespaces clj

(list-networking-v1ingress-for-all-namespaces ctx__10944__auto__
                                              &
                                              [body?__10945__auto__
                                               opts?__10946__auto__])

Calls GET on /apis/networking.k8s.io/v1/ingresses list or watch objects of kind Ingress Parameters: - ctx: required server context Options: - allow-watch-bookmarks: optional boolean allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored. - 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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".

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. - resource-version-match: optional string resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.

Defaults to unset Returns

list-networking-v1namespaced-ingress clj

(list-networking-v1namespaced-ingress ctx__10944__auto__
                                      &
                                      [body?__10945__auto__
                                       opts?__10946__auto__])

Calls GET on /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses list or watch objects of kind Ingress Parameters: - ctx: required server context Options: - namespace: required string object name and auth scope, such as for teams and projects - allow-watch-bookmarks: optional boolean allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored. - 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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".

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. - resource-version-match: optional string resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.

Defaults to unset Returns

list-networking-v1namespaced-network-policy clj

(list-networking-v1namespaced-network-policy ctx__10944__auto__
                                             &
                                             [body?__10945__auto__
                                              opts?__10946__auto__])

Calls GET on /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies list or watch objects of kind NetworkPolicy Parameters: - ctx: required server context Options: - namespace: required string object name and auth scope, such as for teams and projects - allow-watch-bookmarks: optional boolean allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored. - 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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".

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. - resource-version-match: optional string resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.

Defaults to unset Returns

list-networking-v1network-policy-for-all-namespaces clj

(list-networking-v1network-policy-for-all-namespaces ctx__10944__auto__
                                                     &
                                                     [body?__10945__auto__
                                                      opts?__10946__auto__])

Calls GET on /apis/networking.k8s.io/v1/networkpolicies list or watch objects of kind NetworkPolicy Parameters: - ctx: required server context Options: - allow-watch-bookmarks: optional boolean allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored. - 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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".

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. - resource-version-match: optional string resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.

Defaults to unset Returns

make-context clj

patch-networking-v1ingress-class clj

(patch-networking-v1ingress-class ctx__10944__auto__
                                  &
                                  [body?__10945__auto__ opts?__10946__auto__])

Calls PATCH on /apis/networking.k8s.io/v1/ingressclasses/{name} partially update the specified IngressClass Parameters: - ctx: required server context - body: required Options: - name: required string name of the IngressClass - body: required
- dry-run: optional string When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed - field-manager: optional string fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch). - force: optional boolean Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests. Returns

patch-networking-v1namespaced-ingress clj

(patch-networking-v1namespaced-ingress ctx__10944__auto__
                                       &
                                       [body?__10945__auto__
                                        opts?__10946__auto__])

Calls PATCH on /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name} partially update the specified Ingress Parameters: - ctx: required server context - body: required Options: - name: required string name of the Ingress - namespace: required string object name and auth scope, such as for teams and projects - body: required
- dry-run: optional string When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed - field-manager: optional string fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch). - force: optional boolean Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests. Returns

patch-networking-v1namespaced-ingress-status clj

(patch-networking-v1namespaced-ingress-status ctx__10944__auto__
                                              &
                                              [body?__10945__auto__
                                               opts?__10946__auto__])

Calls PATCH on /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name}/status partially update status of the specified Ingress Parameters: - ctx: required server context - body: required Options: - name: required string name of the Ingress - namespace: required string object name and auth scope, such as for teams and projects - body: required
- dry-run: optional string When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed - field-manager: optional string fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch). - force: optional boolean Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests. Returns

patch-networking-v1namespaced-network-policy clj

(patch-networking-v1namespaced-network-policy ctx__10944__auto__
                                              &
                                              [body?__10945__auto__
                                               opts?__10946__auto__])

Calls PATCH on /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name} partially update the specified NetworkPolicy Parameters: - ctx: required server context - body: required Options: - name: required string name of the NetworkPolicy - namespace: required string object name and auth scope, such as for teams and projects - body: required
- dry-run: optional string When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed - field-manager: optional string fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch). - force: optional boolean Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests. Returns

read-networking-v1ingress-class clj

(read-networking-v1ingress-class ctx__10944__auto__
                                 &
                                 [body?__10945__auto__ opts?__10946__auto__])

Calls GET on /apis/networking.k8s.io/v1/ingressclasses/{name} read the specified IngressClass Parameters: - ctx: required server context Options: - name: required string name of the IngressClass Returns

read-networking-v1namespaced-ingress clj

(read-networking-v1namespaced-ingress ctx__10944__auto__
                                      &
                                      [body?__10945__auto__
                                       opts?__10946__auto__])

Calls GET on /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name} read the specified Ingress Parameters: - ctx: required server context Options: - name: required string name of the Ingress - namespace: required string object name and auth scope, such as for teams and projects Returns

read-networking-v1namespaced-ingress-status clj

(read-networking-v1namespaced-ingress-status ctx__10944__auto__
                                             &
                                             [body?__10945__auto__
                                              opts?__10946__auto__])

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

read-networking-v1namespaced-network-policy clj

(read-networking-v1namespaced-network-policy ctx__10944__auto__
                                             &
                                             [body?__10945__auto__
                                              opts?__10946__auto__])

Calls GET on /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name} read the specified NetworkPolicy Parameters: - ctx: required server context Options: - name: required string name of the NetworkPolicy - namespace: required string object name and auth scope, such as for teams and projects Returns

replace-networking-v1ingress-class clj

(replace-networking-v1ingress-class ctx__10944__auto__
                                    &
                                    [body?__10945__auto__ opts?__10946__auto__])

Calls PUT on /apis/networking.k8s.io/v1/ingressclasses/{name} replace the specified IngressClass Parameters: - ctx: required server context - body: required Options: - name: required string name of the IngressClass - body: required
- dry-run: optional string When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed - field-manager: optional string fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. Returns

replace-networking-v1namespaced-ingress clj

(replace-networking-v1namespaced-ingress ctx__10944__auto__
                                         &
                                         [body?__10945__auto__
                                          opts?__10946__auto__])

Calls PUT on /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name} replace the specified Ingress Parameters: - ctx: required server context - body: required Options: - name: required string name of the Ingress - namespace: required string object name and auth scope, such as for teams and projects - body: required
- dry-run: optional string When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed - field-manager: optional string fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. Returns

replace-networking-v1namespaced-ingress-status clj

(replace-networking-v1namespaced-ingress-status ctx__10944__auto__
                                                &
                                                [body?__10945__auto__
                                                 opts?__10946__auto__])

Calls PUT on /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name}/status replace status of the specified Ingress Parameters: - ctx: required server context - body: required Options: - name: required string name of the Ingress - namespace: required string object name and auth scope, such as for teams and projects - body: required
- dry-run: optional string When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed - field-manager: optional string fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. Returns

replace-networking-v1namespaced-network-policy clj

(replace-networking-v1namespaced-network-policy ctx__10944__auto__
                                                &
                                                [body?__10945__auto__
                                                 opts?__10946__auto__])

Calls PUT on /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name} replace the specified NetworkPolicy Parameters: - ctx: required server context - body: required Options: - name: required string name of the NetworkPolicy - namespace: required string object name and auth scope, such as for teams and projects - body: required
- dry-run: optional string When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed - field-manager: optional string fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. Returns