(create-networking-istio-io-v1beta1namespaced-destination-rule
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls POST on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules
create a DestinationRule
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
Calls POST on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules
create a DestinationRule
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-istio-io-v1beta1namespaced-gateway ctx__11560__auto__
&
[body?__11561__auto__
opts?__11562__auto__])Calls POST on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways
create a Gateway
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
Calls POST on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways
create a Gateway
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-istio-io-v1beta1namespaced-proxy-config
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls POST on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs
create a ProxyConfig
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
Calls POST on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs
create a ProxyConfig
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-istio-io-v1beta1namespaced-service-entry
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls POST on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries
create a ServiceEntry
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
Calls POST on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries
create a ServiceEntry
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-istio-io-v1beta1namespaced-sidecar ctx__11560__auto__
&
[body?__11561__auto__
opts?__11562__auto__])Calls POST on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars
create a Sidecar
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
Calls POST on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars
create a Sidecar
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-istio-io-v1beta1namespaced-virtual-service
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls POST on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices
create a VirtualService
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
Calls POST on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices
create a VirtualService
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-istio-io-v1beta1namespaced-workload-entry
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls POST on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries
create a WorkloadEntry
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
Calls POST on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries
create a WorkloadEntry
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-istio-io-v1beta1namespaced-workload-group
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls POST on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups
create a WorkloadGroup
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
Calls POST on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups
create a WorkloadGroup
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-istio-io-v1beta1collection-namespaced-destination-rule
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules delete collection of DestinationRule Parameters: - ctx: required server context - body: required 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. - 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
Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules
delete collection of DestinationRule
Parameters:
- ctx: required server context
- body: required
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.
- 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 (delete-networking-istio-io-v1beta1collection-namespaced-gateway
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways delete collection of Gateway Parameters: - ctx: required server context - body: required 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. - 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
Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways
delete collection of Gateway
Parameters:
- ctx: required server context
- body: required
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.
- 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 (delete-networking-istio-io-v1beta1collection-namespaced-proxy-config
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs delete collection of ProxyConfig Parameters: - ctx: required server context - body: required 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. - 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
Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs
delete collection of ProxyConfig
Parameters:
- ctx: required server context
- body: required
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.
- 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 (delete-networking-istio-io-v1beta1collection-namespaced-service-entry
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries delete collection of ServiceEntry Parameters: - ctx: required server context - body: required 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. - 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
Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries
delete collection of ServiceEntry
Parameters:
- ctx: required server context
- body: required
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.
- 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 (delete-networking-istio-io-v1beta1collection-namespaced-sidecar
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars delete collection of Sidecar Parameters: - ctx: required server context - body: required 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. - 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
Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars
delete collection of Sidecar
Parameters:
- ctx: required server context
- body: required
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.
- 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 (delete-networking-istio-io-v1beta1collection-namespaced-virtual-service
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices delete collection of VirtualService Parameters: - ctx: required server context - body: required 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. - 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
Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices
delete collection of VirtualService
Parameters:
- ctx: required server context
- body: required
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.
- 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 (delete-networking-istio-io-v1beta1collection-namespaced-workload-entry
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries delete collection of WorkloadEntry Parameters: - ctx: required server context - body: required 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. - 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
Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries
delete collection of WorkloadEntry
Parameters:
- ctx: required server context
- body: required
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.
- 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 (delete-networking-istio-io-v1beta1collection-namespaced-workload-group
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups delete collection of WorkloadGroup Parameters: - ctx: required server context - body: required 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. - 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
Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups
delete collection of WorkloadGroup
Parameters:
- ctx: required server context
- body: required
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.
- 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 (delete-networking-istio-io-v1beta1namespaced-destination-rule
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules/{name}
delete a DestinationRule
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the DestinationRule
- 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
Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules/{name}
delete a DestinationRule
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the DestinationRule
- 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-istio-io-v1beta1namespaced-gateway ctx__11560__auto__
&
[body?__11561__auto__
opts?__11562__auto__])Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways/{name}
delete a Gateway
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Gateway
- 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
Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways/{name}
delete a Gateway
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Gateway
- 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-istio-io-v1beta1namespaced-proxy-config
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs/{name}
delete a ProxyConfig
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ProxyConfig
- 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
Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs/{name}
delete a ProxyConfig
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ProxyConfig
- 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-istio-io-v1beta1namespaced-service-entry
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries/{name}
delete a ServiceEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ServiceEntry
- 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
Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries/{name}
delete a ServiceEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ServiceEntry
- 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-istio-io-v1beta1namespaced-sidecar ctx__11560__auto__
&
[body?__11561__auto__
opts?__11562__auto__])Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars/{name}
delete a Sidecar
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Sidecar
- 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
Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars/{name}
delete a Sidecar
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Sidecar
- 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-istio-io-v1beta1namespaced-virtual-service
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices/{name}
delete a VirtualService
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the VirtualService
- 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
Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices/{name}
delete a VirtualService
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the VirtualService
- 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-istio-io-v1beta1namespaced-workload-entry
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries/{name}
delete a WorkloadEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadEntry
- 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
Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries/{name}
delete a WorkloadEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadEntry
- 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-istio-io-v1beta1namespaced-workload-group
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups/{name}
delete a WorkloadGroup
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadGroup
- 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
Calls DELETE on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups/{name}
delete a WorkloadGroup
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadGroup
- 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-istio-io-v1beta1destination-rule-for-all-namespaces
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/destinationrules list objects of kind DestinationRule 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. - 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
Calls GET on /apis/networking.istio.io/v1beta1/destinationrules list objects of kind DestinationRule 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. - 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-istio-io-v1beta1gateway-for-all-namespaces
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/gateways list objects of kind Gateway 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. - 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
Calls GET on /apis/networking.istio.io/v1beta1/gateways list objects of kind Gateway 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. - 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-istio-io-v1beta1namespaced-destination-rule
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules list objects of kind DestinationRule 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. - 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
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules
list objects of kind DestinationRule
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.
- 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-istio-io-v1beta1namespaced-gateway ctx__11560__auto__
&
[body?__11561__auto__
opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways list objects of kind Gateway 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. - 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
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways
list objects of kind Gateway
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.
- 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-istio-io-v1beta1namespaced-proxy-config ctx__11560__auto__
&
[body?__11561__auto__
opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs list objects of kind ProxyConfig 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. - 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
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs
list objects of kind ProxyConfig
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.
- 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-istio-io-v1beta1namespaced-service-entry
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries list objects of kind ServiceEntry 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. - 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
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries
list objects of kind ServiceEntry
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.
- 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-istio-io-v1beta1namespaced-sidecar ctx__11560__auto__
&
[body?__11561__auto__
opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars list objects of kind Sidecar 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. - 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
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars
list objects of kind Sidecar
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.
- 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-istio-io-v1beta1namespaced-virtual-service
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices list objects of kind VirtualService 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. - 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
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices
list objects of kind VirtualService
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.
- 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-istio-io-v1beta1namespaced-workload-entry
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries list objects of kind WorkloadEntry 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. - 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
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries
list objects of kind WorkloadEntry
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.
- 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-istio-io-v1beta1namespaced-workload-group
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups list objects of kind WorkloadGroup 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. - 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
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups
list objects of kind WorkloadGroup
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.
- 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-istio-io-v1beta1proxy-config-for-all-namespaces
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/proxyconfigs list objects of kind ProxyConfig 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. - 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
Calls GET on /apis/networking.istio.io/v1beta1/proxyconfigs list objects of kind ProxyConfig 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. - 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-istio-io-v1beta1service-entry-for-all-namespaces
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/serviceentries list objects of kind ServiceEntry 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. - 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
Calls GET on /apis/networking.istio.io/v1beta1/serviceentries list objects of kind ServiceEntry 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. - 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-istio-io-v1beta1sidecar-for-all-namespaces
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/sidecars list objects of kind Sidecar 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. - 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
Calls GET on /apis/networking.istio.io/v1beta1/sidecars list objects of kind Sidecar 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. - 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-istio-io-v1beta1virtual-service-for-all-namespaces
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/virtualservices list objects of kind VirtualService 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. - 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
Calls GET on /apis/networking.istio.io/v1beta1/virtualservices list objects of kind VirtualService 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. - 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-istio-io-v1beta1workload-entry-for-all-namespaces
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/workloadentries list objects of kind WorkloadEntry 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. - 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
Calls GET on /apis/networking.istio.io/v1beta1/workloadentries list objects of kind WorkloadEntry 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. - 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-istio-io-v1beta1workload-group-for-all-namespaces
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/workloadgroups list objects of kind WorkloadGroup 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. - 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
Calls GET on /apis/networking.istio.io/v1beta1/workloadgroups list objects of kind WorkloadGroup 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. - 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
(patch-networking-istio-io-v1beta1namespaced-destination-rule
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules/{name}
partially update the specified DestinationRule
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the DestinationRule
- 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
Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules/{name}
partially update the specified DestinationRule
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the DestinationRule
- 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 (patch-networking-istio-io-v1beta1namespaced-destination-rule-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules/{name}/status
partially update status of the specified DestinationRule
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the DestinationRule
- 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
Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules/{name}/status
partially update status of the specified DestinationRule
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the DestinationRule
- 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 (patch-networking-istio-io-v1beta1namespaced-gateway ctx__11560__auto__
&
[body?__11561__auto__
opts?__11562__auto__])Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways/{name}
partially update the specified Gateway
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Gateway
- 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
Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways/{name}
partially update the specified Gateway
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Gateway
- 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 (patch-networking-istio-io-v1beta1namespaced-gateway-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways/{name}/status
partially update status of the specified Gateway
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Gateway
- 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
Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways/{name}/status
partially update status of the specified Gateway
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Gateway
- 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 (patch-networking-istio-io-v1beta1namespaced-proxy-config
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs/{name}
partially update the specified ProxyConfig
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ProxyConfig
- 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
Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs/{name}
partially update the specified ProxyConfig
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ProxyConfig
- 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 (patch-networking-istio-io-v1beta1namespaced-proxy-config-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs/{name}/status
partially update status of the specified ProxyConfig
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ProxyConfig
- 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
Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs/{name}/status
partially update status of the specified ProxyConfig
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ProxyConfig
- 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 (patch-networking-istio-io-v1beta1namespaced-service-entry
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries/{name}
partially update the specified ServiceEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ServiceEntry
- 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
Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries/{name}
partially update the specified ServiceEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ServiceEntry
- 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 (patch-networking-istio-io-v1beta1namespaced-service-entry-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries/{name}/status
partially update status of the specified ServiceEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ServiceEntry
- 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
Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries/{name}/status
partially update status of the specified ServiceEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ServiceEntry
- 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 (patch-networking-istio-io-v1beta1namespaced-sidecar ctx__11560__auto__
&
[body?__11561__auto__
opts?__11562__auto__])Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars/{name}
partially update the specified Sidecar
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Sidecar
- 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
Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars/{name}
partially update the specified Sidecar
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Sidecar
- 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 (patch-networking-istio-io-v1beta1namespaced-sidecar-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars/{name}/status
partially update status of the specified Sidecar
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Sidecar
- 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
Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars/{name}/status
partially update status of the specified Sidecar
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Sidecar
- 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 (patch-networking-istio-io-v1beta1namespaced-virtual-service
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices/{name}
partially update the specified VirtualService
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the VirtualService
- 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
Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices/{name}
partially update the specified VirtualService
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the VirtualService
- 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 (patch-networking-istio-io-v1beta1namespaced-virtual-service-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices/{name}/status
partially update status of the specified VirtualService
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the VirtualService
- 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
Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices/{name}/status
partially update status of the specified VirtualService
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the VirtualService
- 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 (patch-networking-istio-io-v1beta1namespaced-workload-entry
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries/{name}
partially update the specified WorkloadEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadEntry
- 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
Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries/{name}
partially update the specified WorkloadEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadEntry
- 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 (patch-networking-istio-io-v1beta1namespaced-workload-entry-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries/{name}/status
partially update status of the specified WorkloadEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadEntry
- 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
Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries/{name}/status
partially update status of the specified WorkloadEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadEntry
- 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 (patch-networking-istio-io-v1beta1namespaced-workload-group
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups/{name}
partially update the specified WorkloadGroup
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadGroup
- 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
Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups/{name}
partially update the specified WorkloadGroup
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadGroup
- 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 (patch-networking-istio-io-v1beta1namespaced-workload-group-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups/{name}/status
partially update status of the specified WorkloadGroup
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadGroup
- 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
Calls PATCH on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups/{name}/status
partially update status of the specified WorkloadGroup
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadGroup
- 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 (read-networking-istio-io-v1beta1namespaced-destination-rule
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules/{name} read the specified DestinationRule Parameters: - ctx: required server context Options: - name: required string name of the DestinationRule - namespace: required string object name and auth scope, such as for teams and projects Returns
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules/{name}
read the specified DestinationRule
Parameters:
- ctx: required server context
Options:
- name: required string name of the DestinationRule
- namespace: required string object name and auth scope, such as for teams and projects
Returns (read-networking-istio-io-v1beta1namespaced-destination-rule-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules/{name}/status read status of the specified DestinationRule Parameters: - ctx: required server context Options: - name: required string name of the DestinationRule - namespace: required string object name and auth scope, such as for teams and projects Returns
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules/{name}/status
read status of the specified DestinationRule
Parameters:
- ctx: required server context
Options:
- name: required string name of the DestinationRule
- namespace: required string object name and auth scope, such as for teams and projects
Returns (read-networking-istio-io-v1beta1namespaced-gateway ctx__11560__auto__
&
[body?__11561__auto__
opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways/{name} read the specified Gateway Parameters: - ctx: required server context Options: - name: required string name of the Gateway - namespace: required string object name and auth scope, such as for teams and projects Returns
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways/{name}
read the specified Gateway
Parameters:
- ctx: required server context
Options:
- name: required string name of the Gateway
- namespace: required string object name and auth scope, such as for teams and projects
Returns (read-networking-istio-io-v1beta1namespaced-gateway-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways/{name}/status read status of the specified Gateway Parameters: - ctx: required server context Options: - name: required string name of the Gateway - namespace: required string object name and auth scope, such as for teams and projects Returns
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways/{name}/status
read status of the specified Gateway
Parameters:
- ctx: required server context
Options:
- name: required string name of the Gateway
- namespace: required string object name and auth scope, such as for teams and projects
Returns (read-networking-istio-io-v1beta1namespaced-proxy-config ctx__11560__auto__
&
[body?__11561__auto__
opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs/{name} read the specified ProxyConfig Parameters: - ctx: required server context Options: - name: required string name of the ProxyConfig - namespace: required string object name and auth scope, such as for teams and projects Returns
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs/{name}
read the specified ProxyConfig
Parameters:
- ctx: required server context
Options:
- name: required string name of the ProxyConfig
- namespace: required string object name and auth scope, such as for teams and projects
Returns (read-networking-istio-io-v1beta1namespaced-proxy-config-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs/{name}/status read status of the specified ProxyConfig Parameters: - ctx: required server context Options: - name: required string name of the ProxyConfig - namespace: required string object name and auth scope, such as for teams and projects Returns
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs/{name}/status
read status of the specified ProxyConfig
Parameters:
- ctx: required server context
Options:
- name: required string name of the ProxyConfig
- namespace: required string object name and auth scope, such as for teams and projects
Returns (read-networking-istio-io-v1beta1namespaced-service-entry
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries/{name} read the specified ServiceEntry Parameters: - ctx: required server context Options: - name: required string name of the ServiceEntry - namespace: required string object name and auth scope, such as for teams and projects Returns
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries/{name}
read the specified ServiceEntry
Parameters:
- ctx: required server context
Options:
- name: required string name of the ServiceEntry
- namespace: required string object name and auth scope, such as for teams and projects
Returns (read-networking-istio-io-v1beta1namespaced-service-entry-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries/{name}/status read status of the specified ServiceEntry Parameters: - ctx: required server context Options: - name: required string name of the ServiceEntry - namespace: required string object name and auth scope, such as for teams and projects Returns
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries/{name}/status
read status of the specified ServiceEntry
Parameters:
- ctx: required server context
Options:
- name: required string name of the ServiceEntry
- namespace: required string object name and auth scope, such as for teams and projects
Returns (read-networking-istio-io-v1beta1namespaced-sidecar ctx__11560__auto__
&
[body?__11561__auto__
opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars/{name} read the specified Sidecar Parameters: - ctx: required server context Options: - name: required string name of the Sidecar - namespace: required string object name and auth scope, such as for teams and projects Returns
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars/{name}
read the specified Sidecar
Parameters:
- ctx: required server context
Options:
- name: required string name of the Sidecar
- namespace: required string object name and auth scope, such as for teams and projects
Returns (read-networking-istio-io-v1beta1namespaced-sidecar-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars/{name}/status read status of the specified Sidecar Parameters: - ctx: required server context Options: - name: required string name of the Sidecar - namespace: required string object name and auth scope, such as for teams and projects Returns
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars/{name}/status
read status of the specified Sidecar
Parameters:
- ctx: required server context
Options:
- name: required string name of the Sidecar
- namespace: required string object name and auth scope, such as for teams and projects
Returns (read-networking-istio-io-v1beta1namespaced-virtual-service
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices/{name} read the specified VirtualService Parameters: - ctx: required server context Options: - name: required string name of the VirtualService - namespace: required string object name and auth scope, such as for teams and projects Returns
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices/{name}
read the specified VirtualService
Parameters:
- ctx: required server context
Options:
- name: required string name of the VirtualService
- namespace: required string object name and auth scope, such as for teams and projects
Returns (read-networking-istio-io-v1beta1namespaced-virtual-service-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices/{name}/status read status of the specified VirtualService Parameters: - ctx: required server context Options: - name: required string name of the VirtualService - namespace: required string object name and auth scope, such as for teams and projects Returns
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices/{name}/status
read status of the specified VirtualService
Parameters:
- ctx: required server context
Options:
- name: required string name of the VirtualService
- namespace: required string object name and auth scope, such as for teams and projects
Returns (read-networking-istio-io-v1beta1namespaced-workload-entry
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries/{name} read the specified WorkloadEntry Parameters: - ctx: required server context Options: - name: required string name of the WorkloadEntry - namespace: required string object name and auth scope, such as for teams and projects Returns
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries/{name}
read the specified WorkloadEntry
Parameters:
- ctx: required server context
Options:
- name: required string name of the WorkloadEntry
- namespace: required string object name and auth scope, such as for teams and projects
Returns (read-networking-istio-io-v1beta1namespaced-workload-entry-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries/{name}/status read status of the specified WorkloadEntry Parameters: - ctx: required server context Options: - name: required string name of the WorkloadEntry - namespace: required string object name and auth scope, such as for teams and projects Returns
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries/{name}/status
read status of the specified WorkloadEntry
Parameters:
- ctx: required server context
Options:
- name: required string name of the WorkloadEntry
- namespace: required string object name and auth scope, such as for teams and projects
Returns (read-networking-istio-io-v1beta1namespaced-workload-group
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups/{name} read the specified WorkloadGroup Parameters: - ctx: required server context Options: - name: required string name of the WorkloadGroup - namespace: required string object name and auth scope, such as for teams and projects Returns
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups/{name}
read the specified WorkloadGroup
Parameters:
- ctx: required server context
Options:
- name: required string name of the WorkloadGroup
- namespace: required string object name and auth scope, such as for teams and projects
Returns (read-networking-istio-io-v1beta1namespaced-workload-group-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups/{name}/status read status of the specified WorkloadGroup Parameters: - ctx: required server context Options: - name: required string name of the WorkloadGroup - namespace: required string object name and auth scope, such as for teams and projects Returns
Calls GET on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups/{name}/status
read status of the specified WorkloadGroup
Parameters:
- ctx: required server context
Options:
- name: required string name of the WorkloadGroup
- namespace: required string object name and auth scope, such as for teams and projects
Returns (replace-networking-istio-io-v1beta1namespaced-destination-rule
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules/{name}
replace the specified DestinationRule
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the DestinationRule
- 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
Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules/{name}
replace the specified DestinationRule
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the DestinationRule
- 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-istio-io-v1beta1namespaced-destination-rule-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules/{name}/status
replace status of the specified DestinationRule
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the DestinationRule
- 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
Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/destinationrules/{name}/status
replace status of the specified DestinationRule
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the DestinationRule
- 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-istio-io-v1beta1namespaced-gateway ctx__11560__auto__
&
[body?__11561__auto__
opts?__11562__auto__])Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways/{name}
replace the specified Gateway
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Gateway
- 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
Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways/{name}
replace the specified Gateway
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Gateway
- 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-istio-io-v1beta1namespaced-gateway-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways/{name}/status
replace status of the specified Gateway
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Gateway
- 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
Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/gateways/{name}/status
replace status of the specified Gateway
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Gateway
- 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-istio-io-v1beta1namespaced-proxy-config
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs/{name}
replace the specified ProxyConfig
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ProxyConfig
- 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
Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs/{name}
replace the specified ProxyConfig
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ProxyConfig
- 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-istio-io-v1beta1namespaced-proxy-config-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs/{name}/status
replace status of the specified ProxyConfig
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ProxyConfig
- 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
Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/proxyconfigs/{name}/status
replace status of the specified ProxyConfig
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ProxyConfig
- 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-istio-io-v1beta1namespaced-service-entry
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries/{name}
replace the specified ServiceEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ServiceEntry
- 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
Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries/{name}
replace the specified ServiceEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ServiceEntry
- 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-istio-io-v1beta1namespaced-service-entry-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries/{name}/status
replace status of the specified ServiceEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ServiceEntry
- 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
Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/serviceentries/{name}/status
replace status of the specified ServiceEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the ServiceEntry
- 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-istio-io-v1beta1namespaced-sidecar ctx__11560__auto__
&
[body?__11561__auto__
opts?__11562__auto__])Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars/{name}
replace the specified Sidecar
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Sidecar
- 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
Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars/{name}
replace the specified Sidecar
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Sidecar
- 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-istio-io-v1beta1namespaced-sidecar-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars/{name}/status
replace status of the specified Sidecar
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Sidecar
- 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
Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/sidecars/{name}/status
replace status of the specified Sidecar
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the Sidecar
- 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-istio-io-v1beta1namespaced-virtual-service
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices/{name}
replace the specified VirtualService
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the VirtualService
- 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
Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices/{name}
replace the specified VirtualService
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the VirtualService
- 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-istio-io-v1beta1namespaced-virtual-service-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices/{name}/status
replace status of the specified VirtualService
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the VirtualService
- 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
Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/virtualservices/{name}/status
replace status of the specified VirtualService
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the VirtualService
- 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-istio-io-v1beta1namespaced-workload-entry
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries/{name}
replace the specified WorkloadEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadEntry
- 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
Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries/{name}
replace the specified WorkloadEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadEntry
- 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-istio-io-v1beta1namespaced-workload-entry-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries/{name}/status
replace status of the specified WorkloadEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadEntry
- 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
Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadentries/{name}/status
replace status of the specified WorkloadEntry
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadEntry
- 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-istio-io-v1beta1namespaced-workload-group
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups/{name}
replace the specified WorkloadGroup
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadGroup
- 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
Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups/{name}
replace the specified WorkloadGroup
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadGroup
- 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-istio-io-v1beta1namespaced-workload-group-status
ctx__11560__auto__
&
[body?__11561__auto__ opts?__11562__auto__])Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups/{name}/status
replace status of the specified WorkloadGroup
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadGroup
- 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
Calls PUT on /apis/networking.istio.io/v1beta1/namespaces/{namespace}/workloadgroups/{name}/status
replace status of the specified WorkloadGroup
Parameters:
- ctx: required server context
- body: required
Options:
- name: required string name of the WorkloadGroup
- 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 cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |