Deploying to gh-pages - 05:20:38

snapshot/api/io/micronaut/kubernetes/client/openapi/api/AdmissionregistrationApi.html

@@ -118,7 +118,8 @@ <h3>getAPIGroup</h3>
 <div class="block">get information of a group</div>
 <dl class="notes">
 <dt>Returns:</dt>
-<dd>V1APIGroup</dd>
+<dd>OK (status code 200)
+         or Unauthorized (status code 401)</dd>
 </dl>
 </section>
 </li>

snapshot/api/io/micronaut/kubernetes/client/openapi/api/AdmissionregistrationV1Api.html

@@ -293,7 +293,10 @@ <h3>createMutatingWebhookConfiguration</h3>
 <dd><code>fieldManager</code> - fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. (optional)</dd>
 <dd><code>fieldValidation</code> - fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. (optional)</dd>
 <dt>Returns:</dt>
-<dd>V1MutatingWebhookConfiguration</dd>
+<dd>OK (status code 200)
+         or Created (status code 201)
+         or Accepted (status code 202)
+         or Unauthorized (status code 401)</dd>
 </dl>
 </section>
 </li>
@@ -321,7 +324,10 @@ <h3>createValidatingWebhookConfiguration</h3>
 <dd><code>fieldManager</code> - fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. (optional)</dd>
 <dd><code>fieldValidation</code> - fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. (optional)</dd>
 <dt>Returns:</dt>
-<dd>V1ValidatingWebhookConfiguration</dd>
+<dd>OK (status code 200)
+         or Created (status code 201)
+         or Accepted (status code 202)
+         or Unauthorized (status code 401)</dd>
 </dl>
 </section>
 </li>
@@ -376,7 +382,8 @@ <h3>deleteCollectionMutatingWebhookConfiguration</h3>
 <dd><code>timeoutSeconds</code> - Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. (optional)</dd>
 <dd><code>body</code> - (optional)</dd>
 <dt>Returns:</dt>
-<dd>V1Status</dd>
+<dd>OK (status code 200)
+         or Unauthorized (status code 401)</dd>
 </dl>
 </section>
 </li>
@@ -431,7 +438,8 @@ <h3>deleteCollectionValidatingWebhookConfiguration</h3>
 <dd><code>timeoutSeconds</code> - Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. (optional)</dd>
 <dd><code>body</code> - (optional)</dd>
 <dt>Returns:</dt>
-<dd>V1Status</dd>
+<dd>OK (status code 200)
+         or Unauthorized (status code 401)</dd>
 </dl>
 </section>
 </li>
@@ -465,7 +473,9 @@ <h3>deleteMutatingWebhookConfiguration</h3>
 <dd><code>propagationPolicy</code> - Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: &#39;Orphan&#39; - orphan the dependents; &#39;Background&#39; - allow the garbage collector to delete the dependents in the background; &#39;Foreground&#39; - a cascading policy that deletes all dependents in the foreground. (optional)</dd>
 <dd><code>body</code> - (optional)</dd>
 <dt>Returns:</dt>
-<dd>V1Status</dd>
+<dd>OK (status code 200)
+         or Accepted (status code 202)
+         or Unauthorized (status code 401)</dd>
 </dl>
 </section>
 </li>
@@ -499,7 +509,9 @@ <h3>deleteValidatingWebhookConfiguration</h3>
 <dd><code>propagationPolicy</code> - Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: &#39;Orphan&#39; - orphan the dependents; &#39;Background&#39; - allow the garbage collector to delete the dependents in the background; &#39;Foreground&#39; - a cascading policy that deletes all dependents in the foreground. (optional)</dd>
 <dd><code>body</code> - (optional)</dd>
 <dt>Returns:</dt>
-<dd>V1Status</dd>
+<dd>OK (status code 200)
+         or Accepted (status code 202)
+         or Unauthorized (status code 401)</dd>
 </dl>
 </section>
 </li>
@@ -512,7 +524,8 @@ <h3>getAPIResources</h3>
 <div class="block">get available resources</div>
 <dl class="notes">
 <dt>Returns:</dt>
-<dd>V1APIResourceList</dd>
+<dd>OK (status code 200)
+         or Unauthorized (status code 401)</dd>
 </dl>
 </section>
 </li>
@@ -558,7 +571,8 @@ <h3>listMutatingWebhookConfiguration</h3>
 <dd><code>timeoutSeconds</code> - Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. (optional)</dd>
 <dd><code>watch</code> - Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. (optional)</dd>
 <dt>Returns:</dt>
-<dd>V1MutatingWebhookConfigurationList</dd>
+<dd>OK (status code 200)
+         or Unauthorized (status code 401)</dd>
 </dl>
 </section>
 </li>
@@ -604,7 +618,8 @@ <h3>listValidatingWebhookConfiguration</h3>
 <dd><code>timeoutSeconds</code> - Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. (optional)</dd>
 <dd><code>watch</code> - Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. (optional)</dd>
 <dt>Returns:</dt>
-<dd>V1ValidatingWebhookConfigurationList</dd>
+<dd>OK (status code 200)
+         or Unauthorized (status code 401)</dd>
 </dl>
 </section>
 </li>
@@ -639,7 +654,9 @@ <h3>patchMutatingWebhookConfiguration</h3>
 <dd><code>fieldValidation</code> - fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. (optional)</dd>
 <dd><code>force</code> - Force is going to \&quot;force\&quot; Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests. (optional)</dd>
 <dt>Returns:</dt>
-<dd>V1MutatingWebhookConfiguration</dd>
+<dd>OK (status code 200)
+         or Created (status code 201)
+         or Unauthorized (status code 401)</dd>
 </dl>
 </section>
 </li>
@@ -674,7 +691,9 @@ <h3>patchValidatingWebhookConfiguration</h3>
 <dd><code>fieldValidation</code> - fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. (optional)</dd>
 <dd><code>force</code> - Force is going to \&quot;force\&quot; Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests. (optional)</dd>
 <dt>Returns:</dt>
-<dd>V1ValidatingWebhookConfiguration</dd>
+<dd>OK (status code 200)
+         or Created (status code 201)
+         or Unauthorized (status code 401)</dd>
 </dl>
 </section>
 </li>
@@ -693,7 +712,8 @@ <h3>readMutatingWebhookConfiguration</h3>
 <dd><code>name</code> - name of the MutatingWebhookConfiguration (required)</dd>
 <dd><code>pretty</code> - If &#39;true&#39;, then the output is pretty printed. (optional)</dd>
 <dt>Returns:</dt>
-<dd>V1MutatingWebhookConfiguration</dd>
+<dd>OK (status code 200)
+         or Unauthorized (status code 401)</dd>
 </dl>
 </section>
 </li>
@@ -712,7 +732,8 @@ <h3>readValidatingWebhookConfiguration</h3>
 <dd><code>name</code> - name of the ValidatingWebhookConfiguration (required)</dd>
 <dd><code>pretty</code> - If &#39;true&#39;, then the output is pretty printed. (optional)</dd>
 <dt>Returns:</dt>
-<dd>V1ValidatingWebhookConfiguration</dd>
+<dd>OK (status code 200)
+         or Unauthorized (status code 401)</dd>
 </dl>
 </section>
 </li>
@@ -743,7 +764,9 @@ <h3>replaceMutatingWebhookConfiguration</h3>
 <dd><code>fieldManager</code> - fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. (optional)</dd>
 <dd><code>fieldValidation</code> - fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. (optional)</dd>
 <dt>Returns:</dt>
-<dd>V1MutatingWebhookConfiguration</dd>
+<dd>OK (status code 200)
+         or Created (status code 201)
+         or Unauthorized (status code 401)</dd>
 </dl>
 </section>
 </li>
@@ -774,7 +797,9 @@ <h3>replaceValidatingWebhookConfiguration</h3>
 <dd><code>fieldManager</code> - fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. (optional)</dd>
 <dd><code>fieldValidation</code> - fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. (optional)</dd>
 <dt>Returns:</dt>
-<dd>V1ValidatingWebhookConfiguration</dd>
+<dd>OK (status code 200)
+         or Created (status code 201)
+         or Unauthorized (status code 401)</dd>
 </dl>
 </section>
 </li>