diff --git a/csharp.settings b/csharp.settings
index abd5677ab..a0072500d 100644
--- a/csharp.settings
+++ b/csharp.settings
@@ -1,3 +1,3 @@
-export KUBERNETES_BRANCH=v1.16.0
+export KUBERNETES_BRANCH=v1.18.0
export CLIENT_VERSION=0.0.1
export PACKAGE_NAME=k8s
diff --git a/src/KubernetesClient/generated/.openapi-generator/COMMIT b/src/KubernetesClient/generated/.openapi-generator/COMMIT
new file mode 100644
index 000000000..768730d96
--- /dev/null
+++ b/src/KubernetesClient/generated/.openapi-generator/COMMIT
@@ -0,0 +1,2 @@
+Requested Commit: v3.3.4
+Actual Commit: 2353d71d4b02be6dbabe25aac1a9e56eb3b812a2
diff --git a/src/KubernetesClient/generated/.swagger-codegen/COMMIT b/src/KubernetesClient/generated/.swagger-codegen/COMMIT
deleted file mode 100644
index a25cb6336..000000000
--- a/src/KubernetesClient/generated/.swagger-codegen/COMMIT
+++ /dev/null
@@ -1,2 +0,0 @@
-Requested Commit: v2.2.3
-Actual Commit: 049b1b2bcc904e1179a0e9b11124ed8fa0e3be2e
diff --git a/src/KubernetesClient/generated/IKubernetes.Watch.cs b/src/KubernetesClient/generated/IKubernetes.Watch.cs
index 69dbc42f9..6c9e640df 100644
--- a/src/KubernetesClient/generated/IKubernetes.Watch.cs
+++ b/src/KubernetesClient/generated/IKubernetes.Watch.cs
@@ -19,8 +19,6 @@ public partial interface IKubernetes
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -97,8 +95,6 @@ Task> WatchNamespacedConfigMapAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -175,8 +171,6 @@ Task> WatchNamespacedEndpointsAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -253,8 +247,6 @@ Task> WatchNamespacedEventAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -331,8 +323,6 @@ Task> WatchNamespacedLimitRangeAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -409,8 +399,6 @@ Task> WatchNamespacedPersistentVolumeClaimAsync
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -487,8 +475,6 @@ Task> WatchNamespacedPodAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -565,8 +551,6 @@ Task> WatchNamespacedPodTemplateAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -643,8 +627,6 @@ Task> WatchNamespacedReplicationControllerAsync
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -721,8 +703,6 @@ Task> WatchNamespacedResourceQuotaAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -799,8 +779,6 @@ Task> WatchNamespacedSecretAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -877,8 +855,6 @@ Task> WatchNamespacedServiceAccountAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -952,8 +928,6 @@ Task> WatchNamespacedServiceAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -1026,8 +1000,6 @@ Task> WatchNamespaceAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -1100,8 +1072,6 @@ Task> WatchNodeAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -1174,8 +1144,6 @@ Task> WatchPersistentVolumeAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -1248,8 +1216,6 @@ Task> WatchMutatingWebhookConfigurationA
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -1322,8 +1288,6 @@ Task> WatchValidatingWebhookConfigurat
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -1396,8 +1360,6 @@ Task> WatchMutatingWebhookConfigura
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -1470,8 +1432,6 @@ Task> WatchValidatingWebhookConfi
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -1544,8 +1504,6 @@ Task> WatchCustomResourceDefinitionAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -1618,8 +1576,6 @@ Task> WatchCustomResourceDefinitionAsyn
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -1692,8 +1648,6 @@ Task> WatchAPIServiceAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -1769,8 +1723,6 @@ Task> WatchAPIServiceAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -1847,8 +1799,6 @@ Task> WatchNamespacedControllerRevisionAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -1925,8 +1875,6 @@ Task> WatchNamespacedDaemonSetAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -2003,8 +1951,6 @@ Task> WatchNamespacedDeploymentAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -2081,8 +2027,6 @@ Task> WatchNamespacedReplicaSetAsync(
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -2149,18 +2093,13 @@ Task> WatchNamespacedStatefulSetAsync(
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind ControllerRevision. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind AuditSink. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the ControllerRevision
- ///
- ///
- /// object name and auth scope, such as for teams and projects
+ /// name of the AuditSink
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -2208,9 +2147,8 @@ Task> WatchNamespacedStatefulSetAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedControllerRevisionAsync(
+ Task> WatchAuditSinkAsync(
string name,
- string @namespace,
bool? allowWatchBookmarks = null,
string @continue = null,
string fieldSelector = null,
@@ -2221,24 +2159,22 @@ Task> WatchNamespacedControllerRevisionAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind Deployment. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the Deployment
+ /// name of the HorizontalPodAutoscaler
///
///
/// object name and auth scope, such as for teams and projects
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -2286,7 +2222,7 @@ Task> WatchNamespacedControllerRevisionAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedDeploymentAsync(
+ Task> WatchNamespacedHorizontalPodAutoscalerAsync(
string name,
string @namespace,
bool? allowWatchBookmarks = null,
@@ -2299,24 +2235,22 @@ Task> WatchNamespacedDeploymentAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind StatefulSet. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the StatefulSet
+ /// name of the HorizontalPodAutoscaler
///
///
/// object name and auth scope, such as for teams and projects
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -2364,7 +2298,7 @@ Task> WatchNamespacedDeploymentAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedStatefulSetAsync(
+ Task> WatchNamespacedHorizontalPodAutoscalerAsync(
string name,
string @namespace,
bool? allowWatchBookmarks = null,
@@ -2377,24 +2311,22 @@ Task> WatchNamespacedStatefulSetAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind ControllerRevision. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the ControllerRevision
+ /// name of the HorizontalPodAutoscaler
///
///
/// object name and auth scope, such as for teams and projects
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -2442,7 +2374,7 @@ Task> WatchNamespacedStatefulSetAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedControllerRevisionAsync(
+ Task> WatchNamespacedHorizontalPodAutoscalerAsync(
string name,
string @namespace,
bool? allowWatchBookmarks = null,
@@ -2455,24 +2387,22 @@ Task> WatchNamespacedControllerRevisionAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind DaemonSet. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind Job. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the DaemonSet
+ /// name of the Job
///
///
/// object name and auth scope, such as for teams and projects
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -2520,7 +2450,7 @@ Task> WatchNamespacedControllerRevisionAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedDaemonSetAsync(
+ Task> WatchNamespacedJobAsync(
string name,
string @namespace,
bool? allowWatchBookmarks = null,
@@ -2533,24 +2463,22 @@ Task> WatchNamespacedDaemonSetAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind Deployment. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind CronJob. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the Deployment
+ /// name of the CronJob
///
///
/// object name and auth scope, such as for teams and projects
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -2598,7 +2526,7 @@ Task> WatchNamespacedDaemonSetAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedDeploymentAsync(
+ Task> WatchNamespacedCronJobAsync(
string name,
string @namespace,
bool? allowWatchBookmarks = null,
@@ -2611,24 +2539,22 @@ Task> WatchNamespacedDeploymentAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind ReplicaSet. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind CronJob. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the ReplicaSet
+ /// name of the CronJob
///
///
/// object name and auth scope, such as for teams and projects
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -2676,7 +2602,7 @@ Task> WatchNamespacedDeploymentAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedReplicaSetAsync(
+ Task> WatchNamespacedCronJobAsync(
string name,
string @namespace,
bool? allowWatchBookmarks = null,
@@ -2689,24 +2615,19 @@ Task> WatchNamespacedReplicaSetAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind StatefulSet. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind CertificateSigningRequest. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the StatefulSet
- ///
- ///
- /// object name and auth scope, such as for teams and projects
+ /// name of the CertificateSigningRequest
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -2754,9 +2675,8 @@ Task> WatchNamespacedReplicaSetAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedStatefulSetAsync(
+ Task> WatchCertificateSigningRequestAsync(
string name,
- string @namespace,
bool? allowWatchBookmarks = null,
string @continue = null,
string fieldSelector = null,
@@ -2767,21 +2687,22 @@ Task> WatchNamespacedStatefulSetAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind AuditSink. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind Lease. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the AuditSink
+ /// name of the Lease
+ ///
+ ///
+ /// object name and auth scope, such as for teams and projects
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -2829,8 +2750,9 @@ Task> WatchNamespacedStatefulSetAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchAuditSinkAsync(
+ Task> WatchNamespacedLeaseAsync(
string name,
+ string @namespace,
bool? allowWatchBookmarks = null,
string @continue = null,
string fieldSelector = null,
@@ -2841,24 +2763,22 @@ Task> WatchAuditSinkAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind Lease. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the HorizontalPodAutoscaler
+ /// name of the Lease
///
///
/// object name and auth scope, such as for teams and projects
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -2906,7 +2826,7 @@ Task> WatchAuditSinkAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedHorizontalPodAutoscalerAsync(
+ Task> WatchNamespacedLeaseAsync(
string name,
string @namespace,
bool? allowWatchBookmarks = null,
@@ -2919,24 +2839,22 @@ Task> WatchNamespacedHorizontalPodAutoscalerA
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind EndpointSlice. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the HorizontalPodAutoscaler
+ /// name of the EndpointSlice
///
///
/// object name and auth scope, such as for teams and projects
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -2984,7 +2902,7 @@ Task> WatchNamespacedHorizontalPodAutoscalerA
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedHorizontalPodAutoscalerAsync(
+ Task> WatchNamespacedEndpointSliceAsync(
string name,
string @namespace,
bool? allowWatchBookmarks = null,
@@ -2997,24 +2915,22 @@ Task> WatchNamespacedHorizontalPodAutosc
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind Event. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the HorizontalPodAutoscaler
+ /// name of the Event
///
///
/// object name and auth scope, such as for teams and projects
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -3062,7 +2978,7 @@ Task> WatchNamespacedHorizontalPodAutosc
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedHorizontalPodAutoscalerAsync(
+ Task> WatchNamespacedEventAsync(
string name,
string @namespace,
bool? allowWatchBookmarks = null,
@@ -3075,24 +2991,22 @@ Task> WatchNamespacedHorizontalPodAutosc
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind Job. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind Ingress. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the Job
+ /// name of the Ingress
///
///
/// object name and auth scope, such as for teams and projects
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -3140,7 +3054,7 @@ Task> WatchNamespacedHorizontalPodAutosc
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedJobAsync(
+ Task> WatchNamespacedIngressAsync(
string name,
string @namespace,
bool? allowWatchBookmarks = null,
@@ -3153,24 +3067,19 @@ Task> WatchNamespacedJobAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind CronJob. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind FlowSchema. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the CronJob
- ///
- ///
- /// object name and auth scope, such as for teams and projects
+ /// name of the FlowSchema
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -3218,9 +3127,8 @@ Task> WatchNamespacedJobAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedCronJobAsync(
+ Task> WatchFlowSchemaAsync(
string name,
- string @namespace,
bool? allowWatchBookmarks = null,
string @continue = null,
string fieldSelector = null,
@@ -3231,24 +3139,19 @@ Task> WatchNamespacedCronJobAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind CronJob. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind PriorityLevelConfiguration. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the CronJob
- ///
- ///
- /// object name and auth scope, such as for teams and projects
+ /// name of the PriorityLevelConfiguration
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -3296,9 +3199,8 @@ Task> WatchNamespacedCronJobAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedCronJobAsync(
+ Task> WatchPriorityLevelConfigurationAsync(
string name,
- string @namespace,
bool? allowWatchBookmarks = null,
string @continue = null,
string fieldSelector = null,
@@ -3309,21 +3211,22 @@ Task> WatchNamespacedCronJobAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind CertificateSigningRequest. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind NetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the CertificateSigningRequest
+ /// name of the NetworkPolicy
+ ///
+ ///
+ /// object name and auth scope, such as for teams and projects
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -3371,8 +3274,9 @@ Task> WatchNamespacedCronJobAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchCertificateSigningRequestAsync(
+ Task> WatchNamespacedNetworkPolicyAsync(
string name,
+ string @namespace,
bool? allowWatchBookmarks = null,
string @continue = null,
string fieldSelector = null,
@@ -3383,24 +3287,19 @@ Task> WatchCertificateSigningRequestAs
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind Lease. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind IngressClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the Lease
- ///
- ///
- /// object name and auth scope, such as for teams and projects
+ /// name of the IngressClass
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -3448,9 +3347,8 @@ Task> WatchCertificateSigningRequestAs
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedLeaseAsync(
+ Task> WatchIngressClassAsync(
string name,
- string @namespace,
bool? allowWatchBookmarks = null,
string @continue = null,
string fieldSelector = null,
@@ -3461,24 +3359,22 @@ Task> WatchNamespacedLeaseAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind Lease. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind Ingress. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the Lease
+ /// name of the Ingress
///
///
/// object name and auth scope, such as for teams and projects
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -3526,7 +3422,7 @@ Task> WatchNamespacedLeaseAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedLeaseAsync(
+ Task> WatchNamespacedIngressAsync(
string name,
string @namespace,
bool? allowWatchBookmarks = null,
@@ -3539,24 +3435,19 @@ Task> WatchNamespacedLeaseAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind EndpointSlice. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind RuntimeClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the EndpointSlice
- ///
- ///
- /// object name and auth scope, such as for teams and projects
+ /// name of the RuntimeClass
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -3604,9 +3495,8 @@ Task> WatchNamespacedLeaseAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedEndpointSliceAsync(
+ Task> WatchRuntimeClassAsync(
string name,
- string @namespace,
bool? allowWatchBookmarks = null,
string @continue = null,
string fieldSelector = null,
@@ -3617,24 +3507,19 @@ Task> WatchNamespacedEndpointSliceAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind Event. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind RuntimeClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the Event
- ///
- ///
- /// object name and auth scope, such as for teams and projects
+ /// name of the RuntimeClass
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -3682,9 +3567,8 @@ Task> WatchNamespacedEndpointSliceAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedEventAsync(
+ Task> WatchRuntimeClassAsync(
string name,
- string @namespace,
bool? allowWatchBookmarks = null,
string @continue = null,
string fieldSelector = null,
@@ -3695,24 +3579,22 @@ Task> WatchNamespacedEventAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind DaemonSet. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind PodDisruptionBudget. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the DaemonSet
+ /// name of the PodDisruptionBudget
///
///
/// object name and auth scope, such as for teams and projects
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -3760,7 +3642,7 @@ Task> WatchNamespacedEventAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedDaemonSetAsync(
+ Task> WatchNamespacedPodDisruptionBudgetAsync(
string name,
string @namespace,
bool? allowWatchBookmarks = null,
@@ -3773,24 +3655,19 @@ Task> WatchNamespacedDaemonSetAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind Deployment. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind PodSecurityPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the Deployment
- ///
- ///
- /// object name and auth scope, such as for teams and projects
+ /// name of the PodSecurityPolicy
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -3838,9 +3715,8 @@ Task> WatchNamespacedDaemonSetAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedDeploymentAsync(
+ Task> WatchPodSecurityPolicyAsync(
string name,
- string @namespace,
bool? allowWatchBookmarks = null,
string @continue = null,
string fieldSelector = null,
@@ -3851,24 +3727,19 @@ Task> WatchNamespacedDeploymentAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind Ingress. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind ClusterRoleBinding. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the Ingress
- ///
- ///
- /// object name and auth scope, such as for teams and projects
+ /// name of the ClusterRoleBinding
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -3916,9 +3787,8 @@ Task> WatchNamespacedDeploymentAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedIngressAsync(
+ Task> WatchClusterRoleBindingAsync(
string name,
- string @namespace,
bool? allowWatchBookmarks = null,
string @continue = null,
string fieldSelector = null,
@@ -3929,24 +3799,19 @@ Task> WatchNamespacedIngressAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind NetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind ClusterRole. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the NetworkPolicy
- ///
- ///
- /// object name and auth scope, such as for teams and projects
+ /// name of the ClusterRole
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -3994,9 +3859,8 @@ Task> WatchNamespacedIngressAsync(
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchNamespacedNetworkPolicyAsync(
+ Task> WatchClusterRoleAsync(
string name,
- string @namespace,
bool? allowWatchBookmarks = null,
string @continue = null,
string fieldSelector = null,
@@ -4007,555 +3871,22 @@ Task> WatchNamespacedNetworkPolicyAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action onEvent = null,
Action onError = null,
Action onClosed = null,
CancellationToken cancellationToken = default(CancellationToken));
///
- /// watch changes to an object of kind ReplicaSet. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
+ /// watch changes to an object of kind RoleBinding. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
///
///
- /// name of the ReplicaSet
+ /// name of the RoleBinding
///
///
/// object name and auth scope, such as for teams and projects
///
///
/// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
- ///
- ///
- /// 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.
- ///
- ///
- /// A selector to restrict the list of returned objects by their fields. Defaults to everything.
- ///
- ///
- /// A selector to restrict the list of returned objects by their labels. Defaults to everything.
- ///
- ///
- /// 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.
- ///
- ///
- /// If 'true', then the output is pretty printed.
- ///
- ///
- /// When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
- ///
- ///
- /// Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
- ///
- ///
- /// Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
- ///
- ///
- /// The headers that will be added to request.
- ///
- ///
- /// The action to invoke when the server sends a new event.
- ///
- ///
- /// The action to invoke when an error occurs.
- ///
- ///
- /// The action to invoke when the server closes the connection.
- ///
- ///
- /// A which can be used to cancel the asynchronous operation.
- ///
- ///
- /// A which represents the asynchronous operation, and returns a new watcher.
- ///
- Task> WatchNamespacedReplicaSetAsync(
- string name,
- string @namespace,
- bool? allowWatchBookmarks = null,
- string @continue = null,
- string fieldSelector = null,
- string labelSelector = null,
- int? limit = null,
- bool? pretty = null,
- string resourceVersion = null,
- int? timeoutSeconds = null,
- bool? watch = null,
- Dictionary> customHeaders = null,
- Action onEvent = null,
- Action onError = null,
- Action onClosed = null,
- CancellationToken cancellationToken = default(CancellationToken));
-
- ///
- /// watch changes to an object of kind PodSecurityPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
- ///
- ///
- /// name of the PodSecurityPolicy
- ///
- ///
- /// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
- ///
- ///
- /// 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.
- ///
- ///
- /// A selector to restrict the list of returned objects by their fields. Defaults to everything.
- ///
- ///
- /// A selector to restrict the list of returned objects by their labels. Defaults to everything.
- ///
- ///
- /// 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.
- ///
- ///
- /// If 'true', then the output is pretty printed.
- ///
- ///
- /// When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
- ///
- ///
- /// Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
- ///
- ///
- /// Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
- ///
- ///
- /// The headers that will be added to request.
- ///
- ///
- /// The action to invoke when the server sends a new event.
- ///
- ///
- /// The action to invoke when an error occurs.
- ///
- ///
- /// The action to invoke when the server closes the connection.
- ///
- ///
- /// A which can be used to cancel the asynchronous operation.
- ///
- ///
- /// A which represents the asynchronous operation, and returns a new watcher.
- ///
- Task> WatchPodSecurityPolicyAsync(
- string name,
- bool? allowWatchBookmarks = null,
- string @continue = null,
- string fieldSelector = null,
- string labelSelector = null,
- int? limit = null,
- bool? pretty = null,
- string resourceVersion = null,
- int? timeoutSeconds = null,
- bool? watch = null,
- Dictionary> customHeaders = null,
- Action onEvent = null,
- Action onError = null,
- Action onClosed = null,
- CancellationToken cancellationToken = default(CancellationToken));
-
- ///
- /// watch changes to an object of kind NetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
- ///
- ///
- /// name of the NetworkPolicy
- ///
- ///
- /// object name and auth scope, such as for teams and projects
- ///
- ///
- /// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
- ///
- ///
- /// 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.
- ///
- ///
- /// A selector to restrict the list of returned objects by their fields. Defaults to everything.
- ///
- ///
- /// A selector to restrict the list of returned objects by their labels. Defaults to everything.
- ///
- ///
- /// 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.
- ///
- ///
- /// If 'true', then the output is pretty printed.
- ///
- ///
- /// When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
- ///
- ///
- /// Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
- ///
- ///
- /// Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
- ///
- ///
- /// The headers that will be added to request.
- ///
- ///
- /// The action to invoke when the server sends a new event.
- ///
- ///
- /// The action to invoke when an error occurs.
- ///
- ///
- /// The action to invoke when the server closes the connection.
- ///
- ///
- /// A which can be used to cancel the asynchronous operation.
- ///
- ///
- /// A which represents the asynchronous operation, and returns a new watcher.
- ///
- Task> WatchNamespacedNetworkPolicyAsync(
- string name,
- string @namespace,
- bool? allowWatchBookmarks = null,
- string @continue = null,
- string fieldSelector = null,
- string labelSelector = null,
- int? limit = null,
- bool? pretty = null,
- string resourceVersion = null,
- int? timeoutSeconds = null,
- bool? watch = null,
- Dictionary> customHeaders = null,
- Action onEvent = null,
- Action onError = null,
- Action onClosed = null,
- CancellationToken cancellationToken = default(CancellationToken));
-
- ///
- /// watch changes to an object of kind Ingress. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
- ///
- ///
- /// name of the Ingress
- ///
- ///
- /// object name and auth scope, such as for teams and projects
- ///
- ///
- /// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
- ///
- ///
- /// 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.
- ///
- ///
- /// A selector to restrict the list of returned objects by their fields. Defaults to everything.
- ///
- ///
- /// A selector to restrict the list of returned objects by their labels. Defaults to everything.
- ///
- ///
- /// 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.
- ///
- ///
- /// If 'true', then the output is pretty printed.
- ///
- ///
- /// When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
- ///
- ///
- /// Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
- ///
- ///
- /// Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
- ///
- ///
- /// The headers that will be added to request.
- ///
- ///
- /// The action to invoke when the server sends a new event.
- ///
- ///
- /// The action to invoke when an error occurs.
- ///
- ///
- /// The action to invoke when the server closes the connection.
- ///
- ///
- /// A which can be used to cancel the asynchronous operation.
- ///
- ///
- /// A which represents the asynchronous operation, and returns a new watcher.
- ///
- Task> WatchNamespacedIngressAsync(
- string name,
- string @namespace,
- bool? allowWatchBookmarks = null,
- string @continue = null,
- string fieldSelector = null,
- string labelSelector = null,
- int? limit = null,
- bool? pretty = null,
- string resourceVersion = null,
- int? timeoutSeconds = null,
- bool? watch = null,
- Dictionary> customHeaders = null,
- Action onEvent = null,
- Action onError = null,
- Action onClosed = null,
- CancellationToken cancellationToken = default(CancellationToken));
-
- ///
- /// watch changes to an object of kind RuntimeClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
- ///
- ///
- /// name of the RuntimeClass
- ///
- ///
- /// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
- ///
- ///
- /// 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.
- ///
- ///
- /// A selector to restrict the list of returned objects by their fields. Defaults to everything.
- ///
- ///
- /// A selector to restrict the list of returned objects by their labels. Defaults to everything.
- ///
- ///
- /// 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.
- ///
- ///
- /// If 'true', then the output is pretty printed.
- ///
- ///
- /// When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
- ///
- ///
- /// Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
- ///
- ///
- /// Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
- ///
- ///
- /// The headers that will be added to request.
- ///
- ///
- /// The action to invoke when the server sends a new event.
- ///
- ///
- /// The action to invoke when an error occurs.
- ///
- ///
- /// The action to invoke when the server closes the connection.
- ///
- ///
- /// A which can be used to cancel the asynchronous operation.
- ///
- ///
- /// A which represents the asynchronous operation, and returns a new watcher.
- ///
- Task> WatchRuntimeClassAsync(
- string name,
- bool? allowWatchBookmarks = null,
- string @continue = null,
- string fieldSelector = null,
- string labelSelector = null,
- int? limit = null,
- bool? pretty = null,
- string resourceVersion = null,
- int? timeoutSeconds = null,
- bool? watch = null,
- Dictionary> customHeaders = null,
- Action onEvent = null,
- Action onError = null,
- Action onClosed = null,
- CancellationToken cancellationToken = default(CancellationToken));
-
- ///
- /// watch changes to an object of kind RuntimeClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
- ///
- ///
- /// name of the RuntimeClass
- ///
- ///
- /// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
- ///
- ///
- /// 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.
- ///
- ///
- /// A selector to restrict the list of returned objects by their fields. Defaults to everything.
- ///
- ///
- /// A selector to restrict the list of returned objects by their labels. Defaults to everything.
- ///
- ///
- /// 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.
- ///
- ///
- /// If 'true', then the output is pretty printed.
- ///
- ///
- /// When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
- ///
- ///
- /// Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
- ///
- ///
- /// Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
- ///
- ///
- /// The headers that will be added to request.
- ///
- ///
- /// The action to invoke when the server sends a new event.
- ///
- ///
- /// The action to invoke when an error occurs.
- ///
- ///
- /// The action to invoke when the server closes the connection.
- ///
- ///
- /// A which can be used to cancel the asynchronous operation.
- ///
- ///
- /// A which represents the asynchronous operation, and returns a new watcher.
- ///
- Task> WatchRuntimeClassAsync(
- string name,
- bool? allowWatchBookmarks = null,
- string @continue = null,
- string fieldSelector = null,
- string labelSelector = null,
- int? limit = null,
- bool? pretty = null,
- string resourceVersion = null,
- int? timeoutSeconds = null,
- bool? watch = null,
- Dictionary> customHeaders = null,
- Action onEvent = null,
- Action onError = null,
- Action onClosed = null,
- CancellationToken cancellationToken = default(CancellationToken));
-
- ///
- /// watch changes to an object of kind PodDisruptionBudget. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
- ///
- ///
- /// name of the PodDisruptionBudget
- ///
- ///
- /// object name and auth scope, such as for teams and projects
- ///
- ///
- /// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
- ///
- ///
- /// 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.
- ///
- ///
- /// A selector to restrict the list of returned objects by their fields. Defaults to everything.
- ///
- ///
- /// A selector to restrict the list of returned objects by their labels. Defaults to everything.
- ///
- ///
- /// 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.
- ///
- ///
- /// If 'true', then the output is pretty printed.
- ///
- ///
- /// When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
- ///
- ///
- /// Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
- ///
- ///
- /// Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
- ///
- ///
- /// The headers that will be added to request.
- ///
- ///
- /// The action to invoke when the server sends a new event.
- ///
- ///
- /// The action to invoke when an error occurs.
- ///
- ///
- /// The action to invoke when the server closes the connection.
- ///
- ///
- /// A which can be used to cancel the asynchronous operation.
- ///
- ///
- /// A which represents the asynchronous operation, and returns a new watcher.
- ///
- Task> WatchNamespacedPodDisruptionBudgetAsync(
- string name,
- string @namespace,
- bool? allowWatchBookmarks = null,
- string @continue = null,
- string fieldSelector = null,
- string labelSelector = null,
- int? limit = null,
- bool? pretty = null,
- string resourceVersion = null,
- int? timeoutSeconds = null,
- bool? watch = null,
- Dictionary> customHeaders = null,
- Action onEvent = null,
- Action onError = null,
- Action onClosed = null,
- CancellationToken cancellationToken = default(CancellationToken));
-
- ///
- /// watch changes to an object of kind PodSecurityPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
- ///
- ///
- /// name of the PodSecurityPolicy
- ///
- ///
- /// allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
- ///
- /// This field is beta.
///
///
/// 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".
@@ -4603,8 +3934,9 @@ Task> WatchNamespacedPodDisruptionBudgetAsyn
///
/// A which represents the asynchronous operation, and returns a new watcher.
///
- Task> WatchPodSecurityPolicyAsync(
+ Task> WatchNamespacedRoleBindingAsync(
string name,
+ string @namespace,
bool? allowWatchBookmarks = null,
string @continue = null,
string fieldSelector = null,
@@ -4615,21 +3947,22 @@ Task> WatchPodSecurityPolicyAsync(
int? timeoutSeconds = null,
bool? watch = null,
Dictionary> customHeaders = null,
- Action onEvent = null,
+ Action