@pulumi/kubernetes 3.23.0 → 3.23.1

package/flowcontrol/v1beta1/priorityLevelConfigurationPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * PriorityLevelConfiguration represents the configuration of a priority level.
  */

package/flowcontrol/v1beta2/flowSchemaPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * FlowSchema defines the schema of a group of flows. Note that a flow is made up of a set of inbound API requests with similar attributes and is identified by a pair of strings: the name of the FlowSchema and a "flow distinguisher".
  */

package/flowcontrol/v1beta2/flowSchemaPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * FlowSchema defines the schema of a group of flows. Note that a flow is made up of a set of inbound API requests with similar attributes and is identified by a pair of strings: the name of the FlowSchema and a "flow distinguisher".
  */

package/flowcontrol/v1beta2/priorityLevelConfigurationPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * PriorityLevelConfiguration represents the configuration of a priority level.
  */

package/flowcontrol/v1beta2/priorityLevelConfigurationPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * PriorityLevelConfiguration represents the configuration of a priority level.
  */

package/flowcontrol/v1beta3/flowSchemaPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * FlowSchema defines the schema of a group of flows. Note that a flow is made up of a set of inbound API requests with similar attributes and is identified by a pair of strings: the name of the FlowSchema and a "flow distinguisher".
  */

package/flowcontrol/v1beta3/flowSchemaPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * FlowSchema defines the schema of a group of flows. Note that a flow is made up of a set of inbound API requests with similar attributes and is identified by a pair of strings: the name of the FlowSchema and a "flow distinguisher".
  */

package/flowcontrol/v1beta3/priorityLevelConfigurationPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * PriorityLevelConfiguration represents the configuration of a priority level.
  */

package/flowcontrol/v1beta3/priorityLevelConfigurationPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * PriorityLevelConfiguration represents the configuration of a priority level.
  */

package/meta/v1/statusPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * Status is a return value for calls that don't return other objects.
  */

package/meta/v1/statusPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * Status is a return value for calls that don't return other objects.
  */

package/networking/v1/ingressClassPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * IngressClass represents the class of the Ingress, referenced by the Ingress Spec. The `ingressclass.kubernetes.io/is-default-class` annotation can be used to indicate that an IngressClass should be considered default. When a single IngressClass resource has this annotation set to true, new Ingress resources without a class specified will be assigned this default class.
  */

package/networking/v1/ingressClassPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * IngressClass represents the class of the Ingress, referenced by the Ingress Spec. The `ingressclass.kubernetes.io/is-default-class` annotation can be used to indicate that an IngressClass should be considered default. When a single IngressClass resource has this annotation set to true, new Ingress resources without a class specified will be assigned this default class.
  */

package/networking/v1/ingressPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * Ingress is a collection of rules that allow inbound connections to reach the endpoints defined by a backend. An Ingress can be configured to give services externally-reachable urls, load balance traffic, terminate SSL, offer name based virtual hosting etc.
  *

package/networking/v1/ingressPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * Ingress is a collection of rules that allow inbound connections to reach the endpoints defined by a backend. An Ingress can be configured to give services externally-reachable urls, load balance traffic, terminate SSL, offer name based virtual hosting etc.
  *

package/networking/v1/networkPolicyPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * NetworkPolicy describes what network traffic is allowed for a set of Pods
  */

package/networking/v1/networkPolicyPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * NetworkPolicy describes what network traffic is allowed for a set of Pods
  */

package/networking/v1alpha1/clusterCIDRPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * ClusterCIDR represents a single configuration for per-Node Pod CIDR allocations when the MultiCIDRRangeAllocator is enabled (see the config for kube-controller-manager).  A cluster may have any number of ClusterCIDR resources, all of which will be considered when allocating a CIDR for a Node.  A ClusterCIDR is eligible to be used for a given Node when the node selector matches the node in question and has free CIDRs to allocate.  In case of multiple matching ClusterCIDR resources, the allocator will attempt to break ties using internal heuristics, but any ClusterCIDR whose node selector matches the Node may be used.
  */

package/networking/v1alpha1/clusterCIDRPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * ClusterCIDR represents a single configuration for per-Node Pod CIDR allocations when the MultiCIDRRangeAllocator is enabled (see the config for kube-controller-manager).  A cluster may have any number of ClusterCIDR resources, all of which will be considered when allocating a CIDR for a Node.  A ClusterCIDR is eligible to be used for a given Node when the node selector matches the node in question and has free CIDRs to allocate.  In case of multiple matching ClusterCIDR resources, the allocator will attempt to break ties using internal heuristics, but any ClusterCIDR whose node selector matches the Node may be used.
  */

package/networking/v1beta1/ingressClassPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * IngressClass represents the class of the Ingress, referenced by the Ingress Spec. The `ingressclass.kubernetes.io/is-default-class` annotation can be used to indicate that an IngressClass should be considered default. When a single IngressClass resource has this annotation set to true, new Ingress resources without a class specified will be assigned this default class.
  */

package/networking/v1beta1/ingressClassPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * IngressClass represents the class of the Ingress, referenced by the Ingress Spec. The `ingressclass.kubernetes.io/is-default-class` annotation can be used to indicate that an IngressClass should be considered default. When a single IngressClass resource has this annotation set to true, new Ingress resources without a class specified will be assigned this default class.
  */

package/networking/v1beta1/ingressPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * Ingress is a collection of rules that allow inbound connections to reach the endpoints defined by a backend. An Ingress can be configured to give services externally-reachable urls, load balance traffic, terminate SSL, offer name based virtual hosting etc.
  *

package/networking/v1beta1/ingressPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * Ingress is a collection of rules that allow inbound connections to reach the endpoints defined by a backend. An Ingress can be configured to give services externally-reachable urls, load balance traffic, terminate SSL, offer name based virtual hosting etc.
  *

package/node/v1/runtimeClassPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * RuntimeClass defines a class of container runtime supported in the cluster. The RuntimeClass is used to determine which container runtime is used to run all containers in a pod. RuntimeClasses are manually defined by a user or cluster provisioner, and referenced in the PodSpec. The Kubelet is responsible for resolving the RuntimeClassName reference before running the pod.  For more details, see https://kubernetes.io/docs/concepts/containers/runtime-class/
  */

package/node/v1/runtimeClassPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * RuntimeClass defines a class of container runtime supported in the cluster. The RuntimeClass is used to determine which container runtime is used to run all containers in a pod. RuntimeClasses are manually defined by a user or cluster provisioner, and referenced in the PodSpec. The Kubelet is responsible for resolving the RuntimeClassName reference before running the pod.  For more details, see https://kubernetes.io/docs/concepts/containers/runtime-class/
  */

package/node/v1alpha1/runtimeClassPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * RuntimeClass defines a class of container runtime supported in the cluster. The RuntimeClass is used to determine which container runtime is used to run all containers in a pod. RuntimeClasses are (currently) manually defined by a user or cluster provisioner, and referenced in the PodSpec. The Kubelet is responsible for resolving the RuntimeClassName reference before running the pod.  For more details, see https://git.k8s.io/enhancements/keps/sig-node/runtime-class.md
  */

package/node/v1alpha1/runtimeClassPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * RuntimeClass defines a class of container runtime supported in the cluster. The RuntimeClass is used to determine which container runtime is used to run all containers in a pod. RuntimeClasses are (currently) manually defined by a user or cluster provisioner, and referenced in the PodSpec. The Kubelet is responsible for resolving the RuntimeClassName reference before running the pod.  For more details, see https://git.k8s.io/enhancements/keps/sig-node/runtime-class.md
  */

package/node/v1beta1/runtimeClassPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * RuntimeClass defines a class of container runtime supported in the cluster. The RuntimeClass is used to determine which container runtime is used to run all containers in a pod. RuntimeClasses are (currently) manually defined by a user or cluster provisioner, and referenced in the PodSpec. The Kubelet is responsible for resolving the RuntimeClassName reference before running the pod.  For more details, see https://git.k8s.io/enhancements/keps/sig-node/runtime-class.md
  */

package/node/v1beta1/runtimeClassPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * RuntimeClass defines a class of container runtime supported in the cluster. The RuntimeClass is used to determine which container runtime is used to run all containers in a pod. RuntimeClasses are (currently) manually defined by a user or cluster provisioner, and referenced in the PodSpec. The Kubelet is responsible for resolving the RuntimeClassName reference before running the pod.  For more details, see https://git.k8s.io/enhancements/keps/sig-node/runtime-class.md
  */

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@pulumi/kubernetes",
-    "version": "v3.23.0",
+    "version": "v3.23.1",
     "keywords": [
         "pulumi",
         "kubernetes",
@@ -12,7 +12,7 @@
     "license": "Apache-2.0",
     "scripts": {
         "build": "tsc",
-        "install": "node scripts/install-pulumi-plugin.js resource kubernetes v3.23.0"
+        "install": "node scripts/install-pulumi-plugin.js resource kubernetes v3.23.1"
     },
     "dependencies": {
         "@pulumi/pulumi": "^3.25.0",

package/package.json.dev

@@ -1,6 +1,6 @@
 {
     "name": "@pulumi/kubernetes",
-    "version": "v3.23.0",
+    "version": "v3.23.1",
     "keywords": [
         "pulumi",
         "kubernetes",
@@ -12,7 +12,7 @@
     "license": "Apache-2.0",
     "scripts": {
         "build": "tsc",
-        "install": "node scripts/install-pulumi-plugin.js resource kubernetes v3.23.0"
+        "install": "node scripts/install-pulumi-plugin.js resource kubernetes v3.23.1"
     },
     "dependencies": {
         "@pulumi/pulumi": "^3.25.0",

package/policy/v1/podDisruptionBudgetPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * PodDisruptionBudget is an object to define the max disruption that can be caused to a collection of pods
  */

package/policy/v1/podDisruptionBudgetPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * PodDisruptionBudget is an object to define the max disruption that can be caused to a collection of pods
  */

package/policy/v1beta1/podDisruptionBudgetPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * PodDisruptionBudget is an object to define the max disruption that can be caused to a collection of pods
  */

package/policy/v1beta1/podDisruptionBudgetPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * PodDisruptionBudget is an object to define the max disruption that can be caused to a collection of pods
  */

package/policy/v1beta1/podSecurityPolicyPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * PodSecurityPolicy governs the ability to make requests that affect the Security Context that will be applied to a pod and container.
  */

package/policy/v1beta1/podSecurityPolicyPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * PodSecurityPolicy governs the ability to make requests that affect the Security Context that will be applied to a pod and container.
  */

package/rbac/v1/clusterRoleBindingPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * ClusterRoleBinding references a ClusterRole, but not contain it.  It can reference a ClusterRole in the global namespace, and adds who information via Subject.
  */

package/rbac/v1/clusterRoleBindingPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * ClusterRoleBinding references a ClusterRole, but not contain it.  It can reference a ClusterRole in the global namespace, and adds who information via Subject.
  */

package/rbac/v1/clusterRolePatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * ClusterRole is a cluster level, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding or ClusterRoleBinding.
  */

package/rbac/v1/clusterRolePatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * ClusterRole is a cluster level, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding or ClusterRoleBinding.
  */

package/rbac/v1/roleBindingPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * RoleBinding references a role, but does not contain it.  It can reference a Role in the same namespace or a ClusterRole in the global namespace. It adds who information via Subjects and namespace information by which namespace it exists in.  RoleBindings in a given namespace only have effect in that namespace.
  */

package/rbac/v1/roleBindingPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * RoleBinding references a role, but does not contain it.  It can reference a Role in the same namespace or a ClusterRole in the global namespace. It adds who information via Subjects and namespace information by which namespace it exists in.  RoleBindings in a given namespace only have effect in that namespace.
  */

package/rbac/v1/rolePatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * Role is a namespaced, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding.
  */

package/rbac/v1/rolePatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * Role is a namespaced, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding.
  */

package/rbac/v1alpha1/clusterRoleBindingPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * ClusterRoleBinding references a ClusterRole, but not contain it.  It can reference a ClusterRole in the global namespace, and adds who information via Subject. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 ClusterRoleBinding, and will no longer be served in v1.20.
  */

package/rbac/v1alpha1/clusterRoleBindingPatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * ClusterRoleBinding references a ClusterRole, but not contain it.  It can reference a ClusterRole in the global namespace, and adds who information via Subject. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 ClusterRoleBinding, and will no longer be served in v1.20.
  */

package/rbac/v1alpha1/clusterRolePatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * ClusterRole is a cluster level, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding or ClusterRoleBinding. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 ClusterRole, and will no longer be served in v1.20.
  */

package/rbac/v1alpha1/clusterRolePatch.js

@@ -10,7 +10,7 @@ const utilities = require("../../utilities");
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * ClusterRole is a cluster level, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding or ClusterRoleBinding. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 ClusterRole, and will no longer be served in v1.20.
  */

package/rbac/v1alpha1/roleBindingPatch.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../../types/output";
  * Server-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than
  * one patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.
  * Conflicts will result in an error by default, but can be forced using the "pulumi.com/patchForce" annotation. See the
- * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#server-side-apply) for
+ * [Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for
  * additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.
  * RoleBinding references a role, but does not contain it.  It can reference a Role in the same namespace or a ClusterRole in the global namespace. It adds who information via Subjects and namespace information by which namespace it exists in.  RoleBindings in a given namespace only have effect in that namespace. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 RoleBinding, and will no longer be served in v1.20.
  */