From bd0a3a15f6f8d8dee23af75397fc94bc21b58032 Mon Sep 17 00:00:00 2001 From: Bryce Lampe Date: Wed, 8 May 2024 14:35:32 -0700 Subject: [PATCH 1/4] Expose config to disable upsert behavior --- CHANGELOG.md | 23 +- .../pulumi-resource-kubernetes/schema.json | 283 ++++++++++-------- provider/pkg/await/await.go | 3 +- provider/pkg/gen/schema.go | 23 +- provider/pkg/provider/provider.go | 17 ++ .../create/without-upsert/Pulumi.yaml | 30 ++ .../create/without-upsert/step2/Pulumi.yaml | 46 +++ .../create/without-upsert/step3/Pulumi.yaml | 45 +++ tests/provider/create_test.go | 30 ++ 9 files changed, 354 insertions(+), 146 deletions(-) create mode 100644 tests/provider/create/without-upsert/Pulumi.yaml create mode 100644 tests/provider/create/without-upsert/step2/Pulumi.yaml create mode 100644 tests/provider/create/without-upsert/step3/Pulumi.yaml create mode 100644 tests/provider/create_test.go diff --git a/CHANGELOG.md b/CHANGELOG.md index ae425bf7d4..6eedd13b52 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,7 @@ - Fix Release behavior to deep merge `valueYamlFiles` to match Helm. (https://github.com/pulumi/pulumi-kubernetes/pull/2963) - Add field manager's name to server-side apply conflict errors. (https://github.com/pulumi/pulumi-kubernetes/pull/2983) +- Add `enableUpsert` provider configuration to control apply behavior on resource creation. ## 4.11.0 (April 17, 2024) @@ -57,7 +58,7 @@ Note that transformations aren't supported in this release (see https://github.c - Fix option propagation in component resources (Go SDK) (https://github.com/pulumi/pulumi-kubernetes/pull/2709) ### Breaking Changes -In previous versions of the pulumi-kubernetes .NET SDK, the `ConfigFile` and `ConfigGroup` component resources inadvertently assigned the wrong parent to the child resource(s). +In previous versions of the pulumi-kubernetes .NET SDK, the `ConfigFile` and `ConfigGroup` component resources inadvertently assigned the wrong parent to the child resource(s). This would happen when the component resource itself had a parent; the child would be assigned that same parent. This also had the effect of disregarding the component resource's provider in favor of the parent's provider. For example, here's a before/after look at the component hierarchy: @@ -65,24 +66,24 @@ For example, here's a before/after look at the component hierarchy: Before: ``` -├─ pkg:index:MyComponent parent -│ ├─ kubernetes:core/v1:ConfigMap cg-options-cg-options-cm-1 +├─ pkg:index:MyComponent parent +│ ├─ kubernetes:core/v1:ConfigMap cg-options-cg-options-cm-1 │ ├─ kubernetes:yaml:ConfigFile cg-options-testdata/options/configgroup/manifest.yaml -│ ├─ kubernetes:core/v1:ConfigMap cg-options-configgroup-cm-1 -│ ├─ kubernetes:yaml:ConfigFile cg-options-testdata/options/configgroup/empty.yaml -│ └─ kubernetes:yaml:ConfigGroup cg-options +│ ├─ kubernetes:core/v1:ConfigMap cg-options-configgroup-cm-1 +│ ├─ kubernetes:yaml:ConfigFile cg-options-testdata/options/configgroup/empty.yaml +│ └─ kubernetes:yaml:ConfigGroup cg-options ``` After: ``` -└─ pkg:index:MyComponent parent - └─ kubernetes:yaml:ConfigGroup cg-options +└─ pkg:index:MyComponent parent + └─ kubernetes:yaml:ConfigGroup cg-options ├─ kubernetes:yaml:ConfigFile cg-options-testdata/options/configgroup/manifest.yaml - │ └─ kubernetes:core/v1:ConfigMap cg-options-configgroup-cm-1 - └─ kubernetes:core/v1:ConfigMap cg-options-cg-options-cm-1 + │ └─ kubernetes:core/v1:ConfigMap cg-options-configgroup-cm-1 + └─ kubernetes:core/v1:ConfigMap cg-options-cg-options-cm-1 ``` - + This release addresses this issue and attempts to heal existing stacks using aliases. This is effective at avoiding a replacement except in the case where the child was created with the wrong provider. In this case, __Pulumi will suggest a replacement of the child resource(s), such that they use the correct provider__. ## 4.6.1 (December 14, 2023) diff --git a/provider/cmd/pulumi-resource-kubernetes/schema.json b/provider/cmd/pulumi-resource-kubernetes/schema.json index 86769df94c..eed2b4ab0e 100644 --- a/provider/cmd/pulumi-resource-kubernetes/schema.json +++ b/provider/cmd/pulumi-resource-kubernetes/schema.json @@ -494,6 +494,16 @@ "type": "boolean", "description": "If present and set to false, disable Server-Side Apply mode.\nSee https://github.com/pulumi/pulumi-kubernetes/issues/2011 for additional details." }, + "enableUpsert": { + "type": "boolean", + "description": "If present and set to false, the provider will surface errors if a create operation would overwrite existing resources in the cluster.", + "default": true, + "defaultInfo": { + "environment": [ + "PULUMI_K8S_ENABLE_UPSERT" + ] + } + }, "kubeconfig": { "type": "string", "description": "The contents of a kubeconfig file or the path to a kubeconfig file. If this is set, this config will be used instead of $KUBECONFIG.", @@ -69981,6 +69991,15 @@ ] } }, + "enableUpsert": { + "type": "boolean", + "description": "If present and set to false, the provider will surface errors if a create operation would overwrite existing resources in the cluster.", + "defaultInfo": { + "environment": [ + "PULUMI_K8S_ENABLE_UPSERT" + ] + } + }, "helmReleaseSettings": { "$ref": "#/types/kubernetes:index:HelmReleaseSettings", "description": "Options to configure the Helm Release resource." @@ -70182,7 +70201,7 @@ ] }, "kubernetes:admissionregistration.k8s.io/v1:MutatingWebhookConfigurationPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nMutatingWebhookConfiguration describes the configuration of and admission webhook that accept or reject and may change the object.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nMutatingWebhookConfiguration describes the configuration of and admission webhook that accept or reject and may change the object.", "properties": { "apiVersion": { "type": "string", @@ -70454,7 +70473,7 @@ } }, "kubernetes:admissionregistration.k8s.io/v1:ValidatingAdmissionPolicyBindingPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nValidatingAdmissionPolicyBinding binds the ValidatingAdmissionPolicy with paramerized resources. ValidatingAdmissionPolicyBinding and parameter CRDs together define how cluster administrators configure policies for clusters.\n\nFor a given admission request, each binding will cause its policy to be evaluated N times, where N is 1 for policies/bindings that don't use params, otherwise N is the number of parameters selected by the binding.\n\nThe CEL expressions of a policy must have a computed CEL cost below the maximum CEL budget. Each evaluation of the policy is given an independent CEL cost budget. Adding/removing policies, bindings, or params can not affect whether a given (policy, binding, param) combination is within its own CEL budget.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nValidatingAdmissionPolicyBinding binds the ValidatingAdmissionPolicy with paramerized resources. ValidatingAdmissionPolicyBinding and parameter CRDs together define how cluster administrators configure policies for clusters.\n\nFor a given admission request, each binding will cause its policy to be evaluated N times, where N is 1 for policies/bindings that don't use params, otherwise N is the number of parameters selected by the binding.\n\nThe CEL expressions of a policy must have a computed CEL cost below the maximum CEL budget. Each evaluation of the policy is given an independent CEL cost budget. Adding/removing policies, bindings, or params can not affect whether a given (policy, binding, param) combination is within its own CEL budget.", "properties": { "apiVersion": { "type": "string", @@ -70582,7 +70601,7 @@ } }, "kubernetes:admissionregistration.k8s.io/v1:ValidatingAdmissionPolicyPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nValidatingAdmissionPolicy describes the definition of an admission validation policy that accepts or rejects an object without changing it.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nValidatingAdmissionPolicy describes the definition of an admission validation policy that accepts or rejects an object without changing it.", "properties": { "apiVersion": { "type": "string", @@ -70789,7 +70808,7 @@ ] }, "kubernetes:admissionregistration.k8s.io/v1:ValidatingWebhookConfigurationPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nValidatingWebhookConfiguration describes the configuration of and admission webhook that accept or reject and object without changing it.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nValidatingWebhookConfiguration describes the configuration of and admission webhook that accept or reject and object without changing it.", "properties": { "apiVersion": { "type": "string", @@ -71061,7 +71080,7 @@ } }, "kubernetes:admissionregistration.k8s.io/v1alpha1:ValidatingAdmissionPolicyBindingPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nValidatingAdmissionPolicyBinding binds the ValidatingAdmissionPolicy with paramerized resources. ValidatingAdmissionPolicyBinding and parameter CRDs together define how cluster administrators configure policies for clusters.\n\nFor a given admission request, each binding will cause its policy to be evaluated N times, where N is 1 for policies/bindings that don't use params, otherwise N is the number of parameters selected by the binding.\n\nThe CEL expressions of a policy must have a computed CEL cost below the maximum CEL budget. Each evaluation of the policy is given an independent CEL cost budget. Adding/removing policies, bindings, or params can not affect whether a given (policy, binding, param) combination is within its own CEL budget.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nValidatingAdmissionPolicyBinding binds the ValidatingAdmissionPolicy with paramerized resources. ValidatingAdmissionPolicyBinding and parameter CRDs together define how cluster administrators configure policies for clusters.\n\nFor a given admission request, each binding will cause its policy to be evaluated N times, where N is 1 for policies/bindings that don't use params, otherwise N is the number of parameters selected by the binding.\n\nThe CEL expressions of a policy must have a computed CEL cost below the maximum CEL budget. Each evaluation of the policy is given an independent CEL cost budget. Adding/removing policies, bindings, or params can not affect whether a given (policy, binding, param) combination is within its own CEL budget.", "properties": { "apiVersion": { "type": "string", @@ -71189,7 +71208,7 @@ } }, "kubernetes:admissionregistration.k8s.io/v1alpha1:ValidatingAdmissionPolicyPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nValidatingAdmissionPolicy describes the definition of an admission validation policy that accepts or rejects an object without changing it.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nValidatingAdmissionPolicy describes the definition of an admission validation policy that accepts or rejects an object without changing it.", "properties": { "apiVersion": { "type": "string", @@ -71396,7 +71415,7 @@ ] }, "kubernetes:admissionregistration.k8s.io/v1beta1:MutatingWebhookConfigurationPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nMutatingWebhookConfiguration describes the configuration of and admission webhook that accept or reject and may change the object. Deprecated in v1.16, planned for removal in v1.19. Use admissionregistration.k8s.io/v1 MutatingWebhookConfiguration instead.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nMutatingWebhookConfiguration describes the configuration of and admission webhook that accept or reject and may change the object. Deprecated in v1.16, planned for removal in v1.19. Use admissionregistration.k8s.io/v1 MutatingWebhookConfiguration instead.", "properties": { "apiVersion": { "type": "string", @@ -71668,7 +71687,7 @@ } }, "kubernetes:admissionregistration.k8s.io/v1beta1:ValidatingAdmissionPolicyBindingPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nValidatingAdmissionPolicyBinding binds the ValidatingAdmissionPolicy with paramerized resources. ValidatingAdmissionPolicyBinding and parameter CRDs together define how cluster administrators configure policies for clusters.\n\nFor a given admission request, each binding will cause its policy to be evaluated N times, where N is 1 for policies/bindings that don't use params, otherwise N is the number of parameters selected by the binding.\n\nThe CEL expressions of a policy must have a computed CEL cost below the maximum CEL budget. Each evaluation of the policy is given an independent CEL cost budget. Adding/removing policies, bindings, or params can not affect whether a given (policy, binding, param) combination is within its own CEL budget.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nValidatingAdmissionPolicyBinding binds the ValidatingAdmissionPolicy with paramerized resources. ValidatingAdmissionPolicyBinding and parameter CRDs together define how cluster administrators configure policies for clusters.\n\nFor a given admission request, each binding will cause its policy to be evaluated N times, where N is 1 for policies/bindings that don't use params, otherwise N is the number of parameters selected by the binding.\n\nThe CEL expressions of a policy must have a computed CEL cost below the maximum CEL budget. Each evaluation of the policy is given an independent CEL cost budget. Adding/removing policies, bindings, or params can not affect whether a given (policy, binding, param) combination is within its own CEL budget.", "properties": { "apiVersion": { "type": "string", @@ -71796,7 +71815,7 @@ } }, "kubernetes:admissionregistration.k8s.io/v1beta1:ValidatingAdmissionPolicyPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nValidatingAdmissionPolicy describes the definition of an admission validation policy that accepts or rejects an object without changing it.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nValidatingAdmissionPolicy describes the definition of an admission validation policy that accepts or rejects an object without changing it.", "properties": { "apiVersion": { "type": "string", @@ -72003,7 +72022,7 @@ ] }, "kubernetes:admissionregistration.k8s.io/v1beta1:ValidatingWebhookConfigurationPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nValidatingWebhookConfiguration describes the configuration of and admission webhook that accept or reject and object without changing it. Deprecated in v1.16, planned for removal in v1.19. Use admissionregistration.k8s.io/v1 ValidatingWebhookConfiguration instead.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nValidatingWebhookConfiguration describes the configuration of and admission webhook that accept or reject and object without changing it. Deprecated in v1.16, planned for removal in v1.19. Use admissionregistration.k8s.io/v1 ValidatingWebhookConfiguration instead.", "properties": { "apiVersion": { "type": "string", @@ -72210,7 +72229,7 @@ ] }, "kubernetes:apiextensions.k8s.io/v1:CustomResourceDefinitionPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCustomResourceDefinition represents a resource that should be exposed on the API server. Its name MUST be in the format <.spec.name>.<.spec.group>.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCustomResourceDefinition represents a resource that should be exposed on the API server. Its name MUST be in the format <.spec.name>.<.spec.group>.", "properties": { "apiVersion": { "type": "string", @@ -72412,7 +72431,7 @@ ] }, "kubernetes:apiextensions.k8s.io/v1beta1:CustomResourceDefinitionPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCustomResourceDefinition represents a resource that should be exposed on the API server. Its name MUST be in the format <.spec.name>.<.spec.group>. Deprecated in v1.16, planned for removal in v1.19. Use apiextensions.k8s.io/v1 CustomResourceDefinition instead.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCustomResourceDefinition represents a resource that should be exposed on the API server. Its name MUST be in the format <.spec.name>.<.spec.group>. Deprecated in v1.16, planned for removal in v1.19. Use apiextensions.k8s.io/v1 CustomResourceDefinition instead.", "properties": { "apiVersion": { "type": "string", @@ -72720,7 +72739,7 @@ ] }, "kubernetes:apiregistration.k8s.io/v1:APIServicePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nAPIService represents a server for a particular GroupVersion. Name must be \"version.group\".", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nAPIService represents a server for a particular GroupVersion. Name must be \"version.group\".", "properties": { "apiVersion": { "type": "string", @@ -72934,7 +72953,7 @@ ] }, "kubernetes:apiregistration.k8s.io/v1beta1:APIServicePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nAPIService represents a server for a particular GroupVersion. Name must be \"version.group\".", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nAPIService represents a server for a particular GroupVersion. Name must be \"version.group\".", "properties": { "apiVersion": { "type": "string", @@ -73154,7 +73173,7 @@ ] }, "kubernetes:apps/v1:ControllerRevisionPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nControllerRevision implements an immutable snapshot of state data. Clients are responsible for serializing and deserializing the objects that contain their internal state. Once a ControllerRevision has been successfully created, it can not be updated. The API Server will fail validation of all requests that attempt to mutate the Data field. ControllerRevisions may, however, be deleted. Note that, due to its use by both the DaemonSet and StatefulSet controllers for update and rollback, this object is beta. However, it may be subject to name and representation changes in future releases, and clients should not depend on its stability. It is primarily for internal use by controllers.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nControllerRevision implements an immutable snapshot of state data. Clients are responsible for serializing and deserializing the objects that contain their internal state. Once a ControllerRevision has been successfully created, it can not be updated. The API Server will fail validation of all requests that attempt to mutate the Data field. ControllerRevisions may, however, be deleted. Note that, due to its use by both the DaemonSet and StatefulSet controllers for update and rollback, this object is beta. However, it may be subject to name and representation changes in future releases, and clients should not depend on its stability. It is primarily for internal use by controllers.", "properties": { "apiVersion": { "type": "string", @@ -73369,7 +73388,7 @@ ] }, "kubernetes:apps/v1:DaemonSetPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDaemonSet represents the configuration of a daemon set.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDaemonSet represents the configuration of a daemon set.", "properties": { "apiVersion": { "type": "string", @@ -73581,7 +73600,7 @@ ] }, "kubernetes:apps/v1:DeploymentPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDeployment enables declarative updates for Pods and ReplicaSets.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. The Deployment has begun to be updated by the Deployment controller. If the current\n generation of the Deployment is > 1, then this means that the current generation must\n be different from the generation reported by the last outputs.\n2. There exists a ReplicaSet whose revision is equal to the current revision of the\n Deployment.\n3. The Deployment's '.status.conditions' has a status of type 'Available' whose 'status'\n member is set to 'True'.\n4. If the Deployment has generation > 1, then '.status.conditions' has a status of type\n 'Progressing', whose 'status' member is set to 'True', and whose 'reason' is\n 'NewReplicaSetAvailable'. For generation <= 1, this status field does not exist,\n because it doesn't do a rollout (i.e., it simply creates the Deployment and\n corresponding ReplicaSet), and therefore there is no rollout to mark as 'Progressing'.\n\nIf the Deployment has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDeployment enables declarative updates for Pods and ReplicaSets.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. The Deployment has begun to be updated by the Deployment controller. If the current\n generation of the Deployment is > 1, then this means that the current generation must\n be different from the generation reported by the last outputs.\n2. There exists a ReplicaSet whose revision is equal to the current revision of the\n Deployment.\n3. The Deployment's '.status.conditions' has a status of type 'Available' whose 'status'\n member is set to 'True'.\n4. If the Deployment has generation > 1, then '.status.conditions' has a status of type\n 'Progressing', whose 'status' member is set to 'True', and whose 'reason' is\n 'NewReplicaSetAvailable'. For generation <= 1, this status field does not exist,\n because it doesn't do a rollout (i.e., it simply creates the Deployment and\n corresponding ReplicaSet), and therefore there is no rollout to mark as 'Progressing'.\n\nIf the Deployment has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", "properties": { "apiVersion": { "type": "string", @@ -73793,7 +73812,7 @@ ] }, "kubernetes:apps/v1:ReplicaSetPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nReplicaSet ensures that a specified number of pod replicas are running at any given time.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nReplicaSet ensures that a specified number of pod replicas are running at any given time.", "properties": { "apiVersion": { "type": "string", @@ -74002,7 +74021,7 @@ ] }, "kubernetes:apps/v1:StatefulSetPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nStatefulSet represents a set of pods with consistent identities. Identities are defined as:\n - Network: A single stable DNS and hostname.\n - Storage: As many VolumeClaims as requested.\n\nThe StatefulSet guarantees that a given network identity will always map to the same storage identity.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. The value of 'spec.replicas' matches '.status.replicas', '.status.currentReplicas',\n and '.status.readyReplicas'.\n2. The value of '.status.updateRevision' matches '.status.currentRevision'.\n\nIf the StatefulSet has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nStatefulSet represents a set of pods with consistent identities. Identities are defined as:\n - Network: A single stable DNS and hostname.\n - Storage: As many VolumeClaims as requested.\n\nThe StatefulSet guarantees that a given network identity will always map to the same storage identity.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. The value of 'spec.replicas' matches '.status.replicas', '.status.currentReplicas',\n and '.status.readyReplicas'.\n2. The value of '.status.updateRevision' matches '.status.currentRevision'.\n\nIf the StatefulSet has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", "properties": { "apiVersion": { "type": "string", @@ -74222,7 +74241,7 @@ ] }, "kubernetes:apps/v1beta1:ControllerRevisionPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nControllerRevision implements an immutable snapshot of state data. Clients are responsible for serializing and deserializing the objects that contain their internal state. Once a ControllerRevision has been successfully created, it can not be updated. The API Server will fail validation of all requests that attempt to mutate the Data field. ControllerRevisions may, however, be deleted. Note that, due to its use by both the DaemonSet and StatefulSet controllers for update and rollback, this object is beta. However, it may be subject to name and representation changes in future releases, and clients should not depend on its stability. It is primarily for internal use by controllers.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nControllerRevision implements an immutable snapshot of state data. Clients are responsible for serializing and deserializing the objects that contain their internal state. Once a ControllerRevision has been successfully created, it can not be updated. The API Server will fail validation of all requests that attempt to mutate the Data field. ControllerRevisions may, however, be deleted. Note that, due to its use by both the DaemonSet and StatefulSet controllers for update and rollback, this object is beta. However, it may be subject to name and representation changes in future releases, and clients should not depend on its stability. It is primarily for internal use by controllers.", "properties": { "apiVersion": { "type": "string", @@ -74442,7 +74461,7 @@ ] }, "kubernetes:apps/v1beta1:DeploymentPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDeployment enables declarative updates for Pods and ReplicaSets.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. The Deployment has begun to be updated by the Deployment controller. If the current\n generation of the Deployment is > 1, then this means that the current generation must\n be different from the generation reported by the last outputs.\n2. There exists a ReplicaSet whose revision is equal to the current revision of the\n Deployment.\n3. The Deployment's '.status.conditions' has a status of type 'Available' whose 'status'\n member is set to 'True'.\n4. If the Deployment has generation > 1, then '.status.conditions' has a status of type\n 'Progressing', whose 'status' member is set to 'True', and whose 'reason' is\n 'NewReplicaSetAvailable'. For generation <= 1, this status field does not exist,\n because it doesn't do a rollout (i.e., it simply creates the Deployment and\n corresponding ReplicaSet), and therefore there is no rollout to mark as 'Progressing'.\n\nIf the Deployment has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDeployment enables declarative updates for Pods and ReplicaSets.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. The Deployment has begun to be updated by the Deployment controller. If the current\n generation of the Deployment is > 1, then this means that the current generation must\n be different from the generation reported by the last outputs.\n2. There exists a ReplicaSet whose revision is equal to the current revision of the\n Deployment.\n3. The Deployment's '.status.conditions' has a status of type 'Available' whose 'status'\n member is set to 'True'.\n4. If the Deployment has generation > 1, then '.status.conditions' has a status of type\n 'Progressing', whose 'status' member is set to 'True', and whose 'reason' is\n 'NewReplicaSetAvailable'. For generation <= 1, this status field does not exist,\n because it doesn't do a rollout (i.e., it simply creates the Deployment and\n corresponding ReplicaSet), and therefore there is no rollout to mark as 'Progressing'.\n\nIf the Deployment has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", "properties": { "apiVersion": { "type": "string", @@ -74650,7 +74669,7 @@ ] }, "kubernetes:apps/v1beta1:StatefulSetPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nStatefulSet represents a set of pods with consistent identities. Identities are defined as:\n - Network: A single stable DNS and hostname.\n - Storage: As many VolumeClaims as requested.\nThe StatefulSet guarantees that a given network identity will always map to the same storage identity.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. The value of 'spec.replicas' matches '.status.replicas', '.status.currentReplicas',\n and '.status.readyReplicas'.\n2. The value of '.status.updateRevision' matches '.status.currentRevision'.\n\nIf the StatefulSet has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nStatefulSet represents a set of pods with consistent identities. Identities are defined as:\n - Network: A single stable DNS and hostname.\n - Storage: As many VolumeClaims as requested.\nThe StatefulSet guarantees that a given network identity will always map to the same storage identity.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. The value of 'spec.replicas' matches '.status.replicas', '.status.currentReplicas',\n and '.status.readyReplicas'.\n2. The value of '.status.updateRevision' matches '.status.currentRevision'.\n\nIf the StatefulSet has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", "properties": { "apiVersion": { "type": "string", @@ -74869,7 +74888,7 @@ ] }, "kubernetes:apps/v1beta2:ControllerRevisionPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nControllerRevision implements an immutable snapshot of state data. Clients are responsible for serializing and deserializing the objects that contain their internal state. Once a ControllerRevision has been successfully created, it can not be updated. The API Server will fail validation of all requests that attempt to mutate the Data field. ControllerRevisions may, however, be deleted. Note that, due to its use by both the DaemonSet and StatefulSet controllers for update and rollback, this object is beta. However, it may be subject to name and representation changes in future releases, and clients should not depend on its stability. It is primarily for internal use by controllers.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nControllerRevision implements an immutable snapshot of state data. Clients are responsible for serializing and deserializing the objects that contain their internal state. Once a ControllerRevision has been successfully created, it can not be updated. The API Server will fail validation of all requests that attempt to mutate the Data field. ControllerRevisions may, however, be deleted. Note that, due to its use by both the DaemonSet and StatefulSet controllers for update and rollback, this object is beta. However, it may be subject to name and representation changes in future releases, and clients should not depend on its stability. It is primarily for internal use by controllers.", "properties": { "apiVersion": { "type": "string", @@ -75086,7 +75105,7 @@ ] }, "kubernetes:apps/v1beta2:DaemonSetPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDaemonSet represents the configuration of a daemon set.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDaemonSet represents the configuration of a daemon set.", "properties": { "apiVersion": { "type": "string", @@ -75300,7 +75319,7 @@ ] }, "kubernetes:apps/v1beta2:DeploymentPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDeployment enables declarative updates for Pods and ReplicaSets.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. The Deployment has begun to be updated by the Deployment controller. If the current\n generation of the Deployment is > 1, then this means that the current generation must\n be different from the generation reported by the last outputs.\n2. There exists a ReplicaSet whose revision is equal to the current revision of the\n Deployment.\n3. The Deployment's '.status.conditions' has a status of type 'Available' whose 'status'\n member is set to 'True'.\n4. If the Deployment has generation > 1, then '.status.conditions' has a status of type\n 'Progressing', whose 'status' member is set to 'True', and whose 'reason' is\n 'NewReplicaSetAvailable'. For generation <= 1, this status field does not exist,\n because it doesn't do a rollout (i.e., it simply creates the Deployment and\n corresponding ReplicaSet), and therefore there is no rollout to mark as 'Progressing'.\n\nIf the Deployment has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDeployment enables declarative updates for Pods and ReplicaSets.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. The Deployment has begun to be updated by the Deployment controller. If the current\n generation of the Deployment is > 1, then this means that the current generation must\n be different from the generation reported by the last outputs.\n2. There exists a ReplicaSet whose revision is equal to the current revision of the\n Deployment.\n3. The Deployment's '.status.conditions' has a status of type 'Available' whose 'status'\n member is set to 'True'.\n4. If the Deployment has generation > 1, then '.status.conditions' has a status of type\n 'Progressing', whose 'status' member is set to 'True', and whose 'reason' is\n 'NewReplicaSetAvailable'. For generation <= 1, this status field does not exist,\n because it doesn't do a rollout (i.e., it simply creates the Deployment and\n corresponding ReplicaSet), and therefore there is no rollout to mark as 'Progressing'.\n\nIf the Deployment has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", "properties": { "apiVersion": { "type": "string", @@ -75514,7 +75533,7 @@ ] }, "kubernetes:apps/v1beta2:ReplicaSetPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nReplicaSet ensures that a specified number of pod replicas are running at any given time.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nReplicaSet ensures that a specified number of pod replicas are running at any given time.", "properties": { "apiVersion": { "type": "string", @@ -75719,7 +75738,7 @@ ] }, "kubernetes:apps/v1beta2:StatefulSetPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nStatefulSet represents a set of pods with consistent identities. Identities are defined as:\n - Network: A single stable DNS and hostname.\n - Storage: As many VolumeClaims as requested.\nThe StatefulSet guarantees that a given network identity will always map to the same storage identity.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. The value of 'spec.replicas' matches '.status.replicas', '.status.currentReplicas',\n and '.status.readyReplicas'.\n2. The value of '.status.updateRevision' matches '.status.currentRevision'.\n\nIf the StatefulSet has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nStatefulSet represents a set of pods with consistent identities. Identities are defined as:\n - Network: A single stable DNS and hostname.\n - Storage: As many VolumeClaims as requested.\nThe StatefulSet guarantees that a given network identity will always map to the same storage identity.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. The value of 'spec.replicas' matches '.status.replicas', '.status.currentReplicas',\n and '.status.readyReplicas'.\n2. The value of '.status.updateRevision' matches '.status.currentRevision'.\n\nIf the StatefulSet has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", "properties": { "apiVersion": { "type": "string", @@ -75910,7 +75929,7 @@ ] }, "kubernetes:auditregistration.k8s.io/v1alpha1:AuditSinkPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nAuditSink represents a cluster level audit sink", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nAuditSink represents a cluster level audit sink", "properties": { "apiVersion": { "type": "string", @@ -76107,7 +76126,7 @@ ] }, "kubernetes:autoscaling/v1:HorizontalPodAutoscalerPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nconfiguration of a horizontal pod autoscaler.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nconfiguration of a horizontal pod autoscaler.", "properties": { "apiVersion": { "type": "string", @@ -76322,7 +76341,7 @@ ] }, "kubernetes:autoscaling/v2:HorizontalPodAutoscalerPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nHorizontalPodAutoscaler is the configuration for a horizontal pod autoscaler, which automatically manages the replica count of any resource implementing the scale subresource based on the metrics specified.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nHorizontalPodAutoscaler is the configuration for a horizontal pod autoscaler, which automatically manages the replica count of any resource implementing the scale subresource based on the metrics specified.", "properties": { "apiVersion": { "type": "string", @@ -76537,7 +76556,7 @@ ] }, "kubernetes:autoscaling/v2beta1:HorizontalPodAutoscalerPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nHorizontalPodAutoscaler is the configuration for a horizontal pod autoscaler, which automatically manages the replica count of any resource implementing the scale subresource based on the metrics specified.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nHorizontalPodAutoscaler is the configuration for a horizontal pod autoscaler, which automatically manages the replica count of any resource implementing the scale subresource based on the metrics specified.", "properties": { "apiVersion": { "type": "string", @@ -76752,7 +76771,7 @@ ] }, "kubernetes:autoscaling/v2beta2:HorizontalPodAutoscalerPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nHorizontalPodAutoscaler is the configuration for a horizontal pod autoscaler, which automatically manages the replica count of any resource implementing the scale subresource based on the metrics specified.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nHorizontalPodAutoscaler is the configuration for a horizontal pod autoscaler, which automatically manages the replica count of any resource implementing the scale subresource based on the metrics specified.", "properties": { "apiVersion": { "type": "string", @@ -76964,7 +76983,7 @@ ] }, "kubernetes:batch/v1:CronJobPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCronJob represents the configuration of a single cron job.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCronJob represents the configuration of a single cron job.", "properties": { "apiVersion": { "type": "string", @@ -77165,7 +77184,7 @@ ] }, "kubernetes:batch/v1:JobPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nJob represents the configuration of a single job.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. The Job's '.status.startTime' is set, which indicates that the Job has started running.\n2. The Job's '.status.conditions' has a status of type 'Complete', and a 'status' set\n to 'True'.\n3. The Job's '.status.conditions' do not have a status of type 'Failed', with a\n\t'status' set to 'True'. If this condition is set, we should fail the Job immediately.\n\nIf the Job has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.\n\nBy default, if a resource failed to become ready in a previous update, \nPulumi will continue to wait for readiness on the next update. If you would prefer\nto schedule a replacement for an unready resource on the next update, you can add the\n\"pulumi.com/replaceUnready\": \"true\" annotation to the resource definition.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nJob represents the configuration of a single job.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. The Job's '.status.startTime' is set, which indicates that the Job has started running.\n2. The Job's '.status.conditions' has a status of type 'Complete', and a 'status' set\n to 'True'.\n3. The Job's '.status.conditions' do not have a status of type 'Failed', with a\n\t'status' set to 'True'. If this condition is set, we should fail the Job immediately.\n\nIf the Job has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.\n\nBy default, if a resource failed to become ready in a previous update, \nPulumi will continue to wait for readiness on the next update. If you would prefer\nto schedule a replacement for an unready resource on the next update, you can add the\n\"pulumi.com/replaceUnready\": \"true\" annotation to the resource definition.", "properties": { "apiVersion": { "type": "string", @@ -77366,7 +77385,7 @@ ] }, "kubernetes:batch/v1beta1:CronJobPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCronJob represents the configuration of a single cron job.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCronJob represents the configuration of a single cron job.", "properties": { "apiVersion": { "type": "string", @@ -77575,7 +77594,7 @@ ] }, "kubernetes:batch/v2alpha1:CronJobPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCronJob represents the configuration of a single cron job.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCronJob represents the configuration of a single cron job.", "properties": { "apiVersion": { "type": "string", @@ -77780,7 +77799,7 @@ ] }, "kubernetes:certificates.k8s.io/v1:CertificateSigningRequestPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCertificateSigningRequest objects provide a mechanism to obtain x509 certificates by submitting a certificate signing request, and having it asynchronously approved and issued.\n\nKubelets use this API to obtain:\n 1. client certificates to authenticate to kube-apiserver (with the \"kubernetes.io/kube-apiserver-client-kubelet\" signerName).\n 2. serving certificates for TLS endpoints kube-apiserver can connect to securely (with the \"kubernetes.io/kubelet-serving\" signerName).\n\nThis API can be used to request client certificates to authenticate to kube-apiserver (with the \"kubernetes.io/kube-apiserver-client\" signerName), or to obtain certificates from custom non-Kubernetes signers.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCertificateSigningRequest objects provide a mechanism to obtain x509 certificates by submitting a certificate signing request, and having it asynchronously approved and issued.\n\nKubelets use this API to obtain:\n 1. client certificates to authenticate to kube-apiserver (with the \"kubernetes.io/kube-apiserver-client-kubelet\" signerName).\n 2. serving certificates for TLS endpoints kube-apiserver can connect to securely (with the \"kubernetes.io/kubelet-serving\" signerName).\n\nThis API can be used to request client certificates to authenticate to kube-apiserver (with the \"kubernetes.io/kube-apiserver-client\" signerName), or to obtain certificates from custom non-Kubernetes signers.", "properties": { "apiVersion": { "type": "string", @@ -77974,7 +77993,7 @@ ] }, "kubernetes:certificates.k8s.io/v1alpha1:ClusterTrustBundlePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nClusterTrustBundle is a cluster-scoped container for X.509 trust anchors (root certificates).\n\nClusterTrustBundle objects are considered to be readable by any authenticated user in the cluster, because they can be mounted by pods using the `clusterTrustBundle` projection. All service accounts have read access to ClusterTrustBundles by default. Users who only have namespace-level access to a cluster can read ClusterTrustBundles by impersonating a serviceaccount that they have access to.\n\nIt can be optionally associated with a particular assigner, in which case it contains one valid set of trust anchors for that signer. Signers may have multiple associated ClusterTrustBundles; each is an independent set of trust anchors for that signer. Admission control is used to enforce that only users with permissions on the signer can create or modify the corresponding bundle.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nClusterTrustBundle is a cluster-scoped container for X.509 trust anchors (root certificates).\n\nClusterTrustBundle objects are considered to be readable by any authenticated user in the cluster, because they can be mounted by pods using the `clusterTrustBundle` projection. All service accounts have read access to ClusterTrustBundles by default. Users who only have namespace-level access to a cluster can read ClusterTrustBundles by impersonating a serviceaccount that they have access to.\n\nIt can be optionally associated with a particular assigner, in which case it contains one valid set of trust anchors for that signer. Signers may have multiple associated ClusterTrustBundles; each is an independent set of trust anchors for that signer. Admission control is used to enforce that only users with permissions on the signer can create or modify the corresponding bundle.", "properties": { "apiVersion": { "type": "string", @@ -78160,7 +78179,7 @@ ] }, "kubernetes:certificates.k8s.io/v1beta1:CertificateSigningRequestPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDescribes a certificate signing request", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDescribes a certificate signing request", "properties": { "apiVersion": { "type": "string", @@ -78356,7 +78375,7 @@ ] }, "kubernetes:coordination.k8s.io/v1:LeasePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nLease defines a lease concept.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nLease defines a lease concept.", "properties": { "apiVersion": { "type": "string", @@ -78549,7 +78568,7 @@ ] }, "kubernetes:coordination.k8s.io/v1beta1:LeasePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nLease defines a lease concept.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nLease defines a lease concept.", "properties": { "apiVersion": { "type": "string", @@ -78671,7 +78690,7 @@ ] }, "kubernetes:core/v1:BindingPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nBinding ties one object to another; for example, a pod is bound to a node by a scheduler. Deprecated in 1.7, please use the bindings subresource of pods instead.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nBinding ties one object to another; for example, a pod is bound to a node by a scheduler. Deprecated in 1.7, please use the bindings subresource of pods instead.", "properties": { "apiVersion": { "type": "string", @@ -78886,7 +78905,7 @@ ] }, "kubernetes:core/v1:ConfigMapPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nConfigMap holds configuration data for pods to consume.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nConfigMap holds configuration data for pods to consume.", "properties": { "apiVersion": { "type": "string", @@ -79105,7 +79124,7 @@ ] }, "kubernetes:core/v1:EndpointsPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nEndpoints is a collection of endpoints that implement the actual service. Example:\n\n\t Name: \"mysvc\",\n\t Subsets: [\n\t {\n\t Addresses: [{\"ip\": \"10.10.1.1\"}, {\"ip\": \"10.10.2.2\"}],\n\t Ports: [{\"name\": \"a\", \"port\": 8675}, {\"name\": \"b\", \"port\": 309}]\n\t },\n\t {\n\t Addresses: [{\"ip\": \"10.10.3.3\"}],\n\t Ports: [{\"name\": \"a\", \"port\": 93}, {\"name\": \"b\", \"port\": 76}]\n\t },\n\t]", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nEndpoints is a collection of endpoints that implement the actual service. Example:\n\n\t Name: \"mysvc\",\n\t Subsets: [\n\t {\n\t Addresses: [{\"ip\": \"10.10.1.1\"}, {\"ip\": \"10.10.2.2\"}],\n\t Ports: [{\"name\": \"a\", \"port\": 8675}, {\"name\": \"b\", \"port\": 309}]\n\t },\n\t {\n\t Addresses: [{\"ip\": \"10.10.3.3\"}],\n\t Ports: [{\"name\": \"a\", \"port\": 93}, {\"name\": \"b\", \"port\": 76}]\n\t },\n\t]", "properties": { "apiVersion": { "type": "string", @@ -79436,7 +79455,7 @@ ] }, "kubernetes:core/v1:EventPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nEvent is a report of an event somewhere in the cluster. Events have a limited retention time and triggers and messages may evolve with time. Event consumers should not rely on the timing of an event with a given Reason reflecting a consistent underlying trigger, or the continued existence of events with that Reason. Events should be treated as informative, best-effort, supplemental data.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nEvent is a report of an event somewhere in the cluster. Events have a limited retention time and triggers and messages may evolve with time. Event consumers should not rely on the timing of an event with a given Reason reflecting a consistent underlying trigger, or the continued existence of events with that Reason. Events should be treated as informative, best-effort, supplemental data.", "properties": { "action": { "type": "string", @@ -79744,7 +79763,7 @@ ] }, "kubernetes:core/v1:LimitRangePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nLimitRange sets resource usage limits for each kind of resource in a Namespace.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nLimitRange sets resource usage limits for each kind of resource in a Namespace.", "properties": { "apiVersion": { "type": "string", @@ -79932,7 +79951,7 @@ ] }, "kubernetes:core/v1:NamespacePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nNamespace provides a scope for Names. Use of multiple namespaces is optional.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nNamespace provides a scope for Names. Use of multiple namespaces is optional.", "properties": { "apiVersion": { "type": "string", @@ -80125,7 +80144,7 @@ ] }, "kubernetes:core/v1:NodePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nNode is a worker node in Kubernetes. Each node will have a unique identifier in the cache (i.e. in etcd).", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nNode is a worker node in Kubernetes. Each node will have a unique identifier in the cache (i.e. in etcd).", "properties": { "apiVersion": { "type": "string", @@ -80383,7 +80402,7 @@ ] }, "kubernetes:core/v1:PersistentVolumeClaimPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPersistentVolumeClaim is a user's request for and claim to a persistent volume", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPersistentVolumeClaim is a user's request for and claim to a persistent volume", "properties": { "apiVersion": { "type": "string", @@ -80511,7 +80530,7 @@ ] }, "kubernetes:core/v1:PersistentVolumePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPersistentVolume (PV) is a storage resource provisioned by an administrator. It is analogous to a node. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPersistentVolume (PV) is a storage resource provisioned by an administrator. It is analogous to a node. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes", "properties": { "apiVersion": { "type": "string", @@ -80704,7 +80723,7 @@ ] }, "kubernetes:core/v1:PodPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPod is a collection of containers that can run on a host. This resource is created by clients and scheduled onto hosts.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. The Pod is scheduled (\"PodScheduled\"\" '.status.condition' is true).\n2. The Pod is initialized (\"Initialized\" '.status.condition' is true).\n3. The Pod is ready (\"Ready\" '.status.condition' is true) and the '.status.phase' is\n set to \"Running\".\nOr (for Jobs): The Pod succeeded ('.status.phase' set to \"Succeeded\").\n\nIf the Pod has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPod is a collection of containers that can run on a host. This resource is created by clients and scheduled onto hosts.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. The Pod is scheduled (\"PodScheduled\"\" '.status.condition' is true).\n2. The Pod is initialized (\"Initialized\" '.status.condition' is true).\n3. The Pod is ready (\"Ready\" '.status.condition' is true) and the '.status.phase' is\n set to \"Running\".\nOr (for Jobs): The Pod succeeded ('.status.phase' set to \"Succeeded\").\n\nIf the Pod has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", "properties": { "apiVersion": { "type": "string", @@ -80892,7 +80911,7 @@ ] }, "kubernetes:core/v1:PodTemplatePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPodTemplate describes a template for creating copies of a predefined pod.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPodTemplate describes a template for creating copies of a predefined pod.", "properties": { "apiVersion": { "type": "string", @@ -81080,7 +81099,7 @@ ] }, "kubernetes:core/v1:ReplicationControllerPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nReplicationController represents the configuration of a replication controller.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nReplicationController represents the configuration of a replication controller.", "properties": { "apiVersion": { "type": "string", @@ -81273,7 +81292,7 @@ ] }, "kubernetes:core/v1:ResourceQuotaPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceQuota sets aggregate quota restrictions enforced per namespace", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceQuota sets aggregate quota restrictions enforced per namespace", "properties": { "apiVersion": { "type": "string", @@ -81507,7 +81526,7 @@ ] }, "kubernetes:core/v1:SecretPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nSecret holds secret data of a certain type. The total bytes of the values in the Data field must be less than MaxSecretSize bytes.\n\nNote: While Pulumi automatically encrypts the 'data' and 'stringData'\nfields, this encryption only applies to Pulumi's context, including the state file, \nthe Service, the CLI, etc. Kubernetes does not encrypt Secret resources by default,\nand the contents are visible to users with access to the Secret in Kubernetes using\ntools like 'kubectl'.\n\nFor more information on securing Kubernetes Secrets, see the following links:\nhttps://kubernetes.io/docs/concepts/configuration/secret/#security-properties\nhttps://kubernetes.io/docs/concepts/configuration/secret/#risks", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nSecret holds secret data of a certain type. The total bytes of the values in the Data field must be less than MaxSecretSize bytes.\n\nNote: While Pulumi automatically encrypts the 'data' and 'stringData'\nfields, this encryption only applies to Pulumi's context, including the state file, \nthe Service, the CLI, etc. Kubernetes does not encrypt Secret resources by default,\nand the contents are visible to users with access to the Secret in Kubernetes using\ntools like 'kubectl'.\n\nFor more information on securing Kubernetes Secrets, see the following links:\nhttps://kubernetes.io/docs/concepts/configuration/secret/#security-properties\nhttps://kubernetes.io/docs/concepts/configuration/secret/#risks", "properties": { "apiVersion": { "type": "string", @@ -81826,7 +81845,7 @@ ] }, "kubernetes:core/v1:ServiceAccountPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nServiceAccount binds together: * a name, understood by users, and perhaps by peripheral systems, for an identity * a principal that can be authenticated and authorized * a set of secrets", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nServiceAccount binds together: * a name, understood by users, and perhaps by peripheral systems, for an identity * a principal that can be authenticated and authorized * a set of secrets", "properties": { "apiVersion": { "type": "string", @@ -81979,7 +81998,7 @@ ] }, "kubernetes:core/v1:ServicePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nService is a named abstraction of software service (for example, mysql) consisting of local port (for example 3306) that the proxy listens on, and the selector that determines which pods will answer requests sent through the proxy.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. Service object exists.\n2. Related Endpoint objects are created. Each time we get an update, wait 10 seconds\n for any stragglers.\n3. The endpoints objects target some number of living objects (unless the Service is\n an \"empty headless\" Service [1] or a Service with '.spec.type: ExternalName').\n4. External IP address is allocated (if Service has '.spec.type: LoadBalancer').\n\nKnown limitations: \nServices targeting ReplicaSets (and, by extension, Deployments,\nStatefulSets, etc.) with '.spec.replicas' set to 0 are not handled, and will time\nout. To work around this limitation, set 'pulumi.com/skipAwait: \"true\"' on\n'.metadata.annotations' for the Service. Work to handle this case is in progress [2].\n\n[1] https://kubernetes.io/docs/concepts/services-networking/service/#headless-services\n[2] https://github.com/pulumi/pulumi-kubernetes/pull/703\n\nIf the Service has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nService is a named abstraction of software service (for example, mysql) consisting of local port (for example 3306) that the proxy listens on, and the selector that determines which pods will answer requests sent through the proxy.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. Service object exists.\n2. Related Endpoint objects are created. Each time we get an update, wait 10 seconds\n for any stragglers.\n3. The endpoints objects target some number of living objects (unless the Service is\n an \"empty headless\" Service [1] or a Service with '.spec.type: ExternalName').\n4. External IP address is allocated (if Service has '.spec.type: LoadBalancer').\n\nKnown limitations: \nServices targeting ReplicaSets (and, by extension, Deployments,\nStatefulSets, etc.) with '.spec.replicas' set to 0 are not handled, and will time\nout. To work around this limitation, set 'pulumi.com/skipAwait: \"true\"' on\n'.metadata.annotations' for the Service. Work to handle this case is in progress [2].\n\n[1] https://kubernetes.io/docs/concepts/services-networking/service/#headless-services\n[2] https://github.com/pulumi/pulumi-kubernetes/pull/703\n\nIf the Service has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", "properties": { "apiVersion": { "type": "string", @@ -82208,7 +82227,7 @@ ] }, "kubernetes:discovery.k8s.io/v1:EndpointSlicePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nEndpointSlice represents a subset of the endpoints that implement a service. For a given service there may be multiple EndpointSlice objects, selected by labels, which must be joined to produce the full set of endpoints.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nEndpointSlice represents a subset of the endpoints that implement a service. For a given service there may be multiple EndpointSlice objects, selected by labels, which must be joined to produce the full set of endpoints.", "properties": { "addressType": { "type": "string", @@ -82467,7 +82486,7 @@ ] }, "kubernetes:discovery.k8s.io/v1beta1:EndpointSlicePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nEndpointSlice represents a subset of the endpoints that implement a service. For a given service there may be multiple EndpointSlice objects, selected by labels, which must be joined to produce the full set of endpoints.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nEndpointSlice represents a subset of the endpoints that implement a service. For a given service there may be multiple EndpointSlice objects, selected by labels, which must be joined to produce the full set of endpoints.", "properties": { "addressType": { "type": "string", @@ -82826,7 +82845,7 @@ ] }, "kubernetes:events.k8s.io/v1:EventPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nEvent is a report of an event somewhere in the cluster. It generally denotes some state change in the system. Events have a limited retention time and triggers and messages may evolve with time. Event consumers should not rely on the timing of an event with a given Reason reflecting a consistent underlying trigger, or the continued existence of events with that Reason. Events should be treated as informative, best-effort, supplemental data.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nEvent is a report of an event somewhere in the cluster. It generally denotes some state change in the system. Events have a limited retention time and triggers and messages may evolve with time. Event consumers should not rely on the timing of an event with a given Reason reflecting a consistent underlying trigger, or the continued existence of events with that Reason. Events should be treated as informative, best-effort, supplemental data.", "properties": { "action": { "type": "string", @@ -83273,7 +83292,7 @@ ] }, "kubernetes:events.k8s.io/v1beta1:EventPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nEvent is a report of an event somewhere in the cluster. It generally denotes some state change in the system.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nEvent is a report of an event somewhere in the cluster. It generally denotes some state change in the system.", "properties": { "action": { "type": "string", @@ -83593,7 +83612,7 @@ ] }, "kubernetes:extensions/v1beta1:DaemonSetPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDaemonSet represents the configuration of a daemon set.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDaemonSet represents the configuration of a daemon set.", "properties": { "apiVersion": { "type": "string", @@ -83807,7 +83826,7 @@ ] }, "kubernetes:extensions/v1beta1:DeploymentPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDeployment enables declarative updates for Pods and ReplicaSets.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. The Deployment has begun to be updated by the Deployment controller. If the current\n generation of the Deployment is > 1, then this means that the current generation must\n be different from the generation reported by the last outputs.\n2. There exists a ReplicaSet whose revision is equal to the current revision of the\n Deployment.\n3. The Deployment's '.status.conditions' has a status of type 'Available' whose 'status'\n member is set to 'True'.\n4. If the Deployment has generation > 1, then '.status.conditions' has a status of type\n 'Progressing', whose 'status' member is set to 'True', and whose 'reason' is\n 'NewReplicaSetAvailable'. For generation <= 1, this status field does not exist,\n because it doesn't do a rollout (i.e., it simply creates the Deployment and\n corresponding ReplicaSet), and therefore there is no rollout to mark as 'Progressing'.\n\nIf the Deployment has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDeployment enables declarative updates for Pods and ReplicaSets.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. The Deployment has begun to be updated by the Deployment controller. If the current\n generation of the Deployment is > 1, then this means that the current generation must\n be different from the generation reported by the last outputs.\n2. There exists a ReplicaSet whose revision is equal to the current revision of the\n Deployment.\n3. The Deployment's '.status.conditions' has a status of type 'Available' whose 'status'\n member is set to 'True'.\n4. If the Deployment has generation > 1, then '.status.conditions' has a status of type\n 'Progressing', whose 'status' member is set to 'True', and whose 'reason' is\n 'NewReplicaSetAvailable'. For generation <= 1, this status field does not exist,\n because it doesn't do a rollout (i.e., it simply creates the Deployment and\n corresponding ReplicaSet), and therefore there is no rollout to mark as 'Progressing'.\n\nIf the Deployment has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", "properties": { "apiVersion": { "type": "string", @@ -84021,7 +84040,7 @@ ] }, "kubernetes:extensions/v1beta1:IngressPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nIngress 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. \n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. Ingress object exists.\n2. Endpoint objects exist with matching names for each Ingress path (except when Service\n type is ExternalName).\n3. Ingress entry exists for '.status.loadBalancer.ingress'.\n\nIf the Ingress has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nIngress 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. \n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. Ingress object exists.\n2. Endpoint objects exist with matching names for each Ingress path (except when Service\n type is ExternalName).\n3. Ingress entry exists for '.status.loadBalancer.ingress'.\n\nIf the Ingress has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", "properties": { "apiVersion": { "type": "string", @@ -84223,7 +84242,7 @@ ] }, "kubernetes:extensions/v1beta1:NetworkPolicyPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDEPRECATED 1.9 - This group version of NetworkPolicy is deprecated by networking/v1/NetworkPolicy. NetworkPolicy describes what network traffic is allowed for a set of Pods", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDEPRECATED 1.9 - This group version of NetworkPolicy is deprecated by networking/v1/NetworkPolicy. NetworkPolicy describes what network traffic is allowed for a set of Pods", "properties": { "apiVersion": { "type": "string", @@ -84416,7 +84435,7 @@ ] }, "kubernetes:extensions/v1beta1:PodSecurityPolicyPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPodSecurityPolicy governs the ability to make requests that affect the Security Context that will be applied to a pod and container. Deprecated: use PodSecurityPolicy from policy API Group instead.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPodSecurityPolicy governs the ability to make requests that affect the Security Context that will be applied to a pod and container. Deprecated: use PodSecurityPolicy from policy API Group instead.", "properties": { "apiVersion": { "type": "string", @@ -84618,7 +84637,7 @@ ] }, "kubernetes:extensions/v1beta1:ReplicaSetPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nReplicaSet ensures that a specified number of pod replicas are running at any given time.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nReplicaSet ensures that a specified number of pod replicas are running at any given time.", "properties": { "apiVersion": { "type": "string", @@ -84834,7 +84853,7 @@ ] }, "kubernetes:flowcontrol.apiserver.k8s.io/v1:FlowSchemaPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nFlowSchema 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\".", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nFlowSchema 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\".", "properties": { "apiVersion": { "type": "string", @@ -85055,7 +85074,7 @@ ] }, "kubernetes:flowcontrol.apiserver.k8s.io/v1:PriorityLevelConfigurationPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPriorityLevelConfiguration represents the configuration of a priority level.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPriorityLevelConfiguration represents the configuration of a priority level.", "properties": { "apiVersion": { "type": "string", @@ -85276,7 +85295,7 @@ ] }, "kubernetes:flowcontrol.apiserver.k8s.io/v1alpha1:FlowSchemaPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nFlowSchema 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\".", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nFlowSchema 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\".", "properties": { "apiVersion": { "type": "string", @@ -85497,7 +85516,7 @@ ] }, "kubernetes:flowcontrol.apiserver.k8s.io/v1alpha1:PriorityLevelConfigurationPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPriorityLevelConfiguration represents the configuration of a priority level.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPriorityLevelConfiguration represents the configuration of a priority level.", "properties": { "apiVersion": { "type": "string", @@ -85718,7 +85737,7 @@ ] }, "kubernetes:flowcontrol.apiserver.k8s.io/v1beta1:FlowSchemaPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nFlowSchema 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\".", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nFlowSchema 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\".", "properties": { "apiVersion": { "type": "string", @@ -85939,7 +85958,7 @@ ] }, "kubernetes:flowcontrol.apiserver.k8s.io/v1beta1:PriorityLevelConfigurationPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPriorityLevelConfiguration represents the configuration of a priority level.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPriorityLevelConfiguration represents the configuration of a priority level.", "properties": { "apiVersion": { "type": "string", @@ -86160,7 +86179,7 @@ ] }, "kubernetes:flowcontrol.apiserver.k8s.io/v1beta2:FlowSchemaPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nFlowSchema 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\".", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nFlowSchema 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\".", "properties": { "apiVersion": { "type": "string", @@ -86381,7 +86400,7 @@ ] }, "kubernetes:flowcontrol.apiserver.k8s.io/v1beta2:PriorityLevelConfigurationPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPriorityLevelConfiguration represents the configuration of a priority level.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPriorityLevelConfiguration represents the configuration of a priority level.", "properties": { "apiVersion": { "type": "string", @@ -86602,7 +86621,7 @@ ] }, "kubernetes:flowcontrol.apiserver.k8s.io/v1beta3:FlowSchemaPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nFlowSchema 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\".", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nFlowSchema 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\".", "properties": { "apiVersion": { "type": "string", @@ -86823,7 +86842,7 @@ ] }, "kubernetes:flowcontrol.apiserver.k8s.io/v1beta3:PriorityLevelConfigurationPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPriorityLevelConfiguration represents the configuration of a priority level.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPriorityLevelConfiguration represents the configuration of a priority level.", "properties": { "apiVersion": { "type": "string", @@ -87461,7 +87480,7 @@ } }, "kubernetes:meta/v1:StatusPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nStatus is a return value for calls that don't return other objects.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nStatus is a return value for calls that don't return other objects.", "properties": { "apiVersion": { "type": "string", @@ -87754,7 +87773,7 @@ ] }, "kubernetes:networking.k8s.io/v1:IngressClassPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nIngressClass 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.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nIngressClass 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.", "properties": { "apiVersion": { "type": "string", @@ -87882,7 +87901,7 @@ ] }, "kubernetes:networking.k8s.io/v1:IngressPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nIngress 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.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. Ingress object exists.\n2. Endpoint objects exist with matching names for each Ingress path (except when Service\n type is ExternalName).\n3. Ingress entry exists for '.status.loadBalancer.ingress'.\n\nIf the Ingress has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nIngress 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.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. Ingress object exists.\n2. Endpoint objects exist with matching names for each Ingress path (except when Service\n type is ExternalName).\n3. Ingress entry exists for '.status.loadBalancer.ingress'.\n\nIf the Ingress has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", "properties": { "apiVersion": { "type": "string", @@ -88088,7 +88107,7 @@ ] }, "kubernetes:networking.k8s.io/v1:NetworkPolicyPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nNetworkPolicy describes what network traffic is allowed for a set of Pods", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nNetworkPolicy describes what network traffic is allowed for a set of Pods", "properties": { "apiVersion": { "type": "string", @@ -88281,7 +88300,7 @@ ] }, "kubernetes:networking.k8s.io/v1alpha1:ClusterCIDRPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nClusterCIDR 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.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nClusterCIDR 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.", "properties": { "apiVersion": { "type": "string", @@ -88464,7 +88483,7 @@ ] }, "kubernetes:networking.k8s.io/v1alpha1:IPAddressPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nIPAddress represents a single IP of a single IP Family. The object is designed to be used by APIs that operate on IP addresses. The object is used by the Service core API for allocation of IP addresses. An IP address can be represented in different formats, to guarantee the uniqueness of the IP, the name of the object is the IP address in canonical format, four decimal digits separated by dots suppressing leading zeros for IPv4 and the representation defined by RFC 5952 for IPv6. Valid: 192.168.1.5 or 2001:db8::1 or 2001:db8:aaaa:bbbb:cccc:dddd:eeee:1 Invalid: 10.01.2.3 or 2001:db8:0:0:0::1", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nIPAddress represents a single IP of a single IP Family. The object is designed to be used by APIs that operate on IP addresses. The object is used by the Service core API for allocation of IP addresses. An IP address can be represented in different formats, to guarantee the uniqueness of the IP, the name of the object is the IP address in canonical format, four decimal digits separated by dots suppressing leading zeros for IPv4 and the representation defined by RFC 5952 for IPv6. Valid: 192.168.1.5 or 2001:db8::1 or 2001:db8:aaaa:bbbb:cccc:dddd:eeee:1 Invalid: 10.01.2.3 or 2001:db8:0:0:0::1", "properties": { "apiVersion": { "type": "string", @@ -88652,7 +88671,7 @@ ] }, "kubernetes:networking.k8s.io/v1alpha1:ServiceCIDRPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nServiceCIDR defines a range of IP addresses using CIDR format (e.g. 192.168.0.0/24 or 2001:db2::/64). This range is used to allocate ClusterIPs to Service objects.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nServiceCIDR defines a range of IP addresses using CIDR format (e.g. 192.168.0.0/24 or 2001:db2::/64). This range is used to allocate ClusterIPs to Service objects.", "properties": { "apiVersion": { "type": "string", @@ -88918,7 +88937,7 @@ ] }, "kubernetes:networking.k8s.io/v1beta1:IngressClassPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nIngressClass 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.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nIngressClass 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.", "properties": { "apiVersion": { "type": "string", @@ -89046,7 +89065,7 @@ ] }, "kubernetes:networking.k8s.io/v1beta1:IngressPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nIngress 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.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. Ingress object exists.\n2. Endpoint objects exist with matching names for each Ingress path (except when Service\n type is ExternalName).\n3. Ingress entry exists for '.status.loadBalancer.ingress'.\n\nIf the Ingress has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nIngress 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.\n\nThis resource waits until its status is ready before registering success\nfor create/update, and populating output properties from the current state of the resource.\nThe following conditions are used to determine whether the resource creation has\nsucceeded or failed:\n\n1. Ingress object exists.\n2. Endpoint objects exist with matching names for each Ingress path (except when Service\n type is ExternalName).\n3. Ingress entry exists for '.status.loadBalancer.ingress'.\n\nIf the Ingress has not reached a Ready state after 10 minutes, it will\ntime out and mark the resource update as Failed. You can override the default timeout value\nby setting the 'customTimeouts' option on the resource.", "properties": { "apiVersion": { "type": "string", @@ -89273,7 +89292,7 @@ ] }, "kubernetes:node.k8s.io/v1:RuntimeClassPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nRuntimeClass 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/", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nRuntimeClass 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/", "properties": { "apiVersion": { "type": "string", @@ -89493,7 +89512,7 @@ ] }, "kubernetes:node.k8s.io/v1alpha1:RuntimeClassPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nRuntimeClass 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", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nRuntimeClass 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", "properties": { "apiVersion": { "type": "string", @@ -89715,7 +89734,7 @@ ] }, "kubernetes:node.k8s.io/v1beta1:RuntimeClassPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nRuntimeClass 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", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nRuntimeClass 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", "properties": { "apiVersion": { "type": "string", @@ -89934,7 +89953,7 @@ ] }, "kubernetes:policy/v1:PodDisruptionBudgetPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPodDisruptionBudget is an object to define the max disruption that can be caused to a collection of pods", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPodDisruptionBudget is an object to define the max disruption that can be caused to a collection of pods", "properties": { "apiVersion": { "type": "string", @@ -90131,7 +90150,7 @@ ] }, "kubernetes:policy/v1beta1:PodDisruptionBudgetPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPodDisruptionBudget is an object to define the max disruption that can be caused to a collection of pods", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPodDisruptionBudget is an object to define the max disruption that can be caused to a collection of pods", "properties": { "apiVersion": { "type": "string", @@ -90327,7 +90346,7 @@ ] }, "kubernetes:policy/v1beta1:PodSecurityPolicyPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPodSecurityPolicy governs the ability to make requests that affect the Security Context that will be applied to a pod and container.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPodSecurityPolicy governs the ability to make requests that affect the Security Context that will be applied to a pod and container.", "properties": { "apiVersion": { "type": "string", @@ -90626,7 +90645,7 @@ ] }, "kubernetes:rbac.authorization.k8s.io/v1:ClusterRoleBindingPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nClusterRoleBinding references a ClusterRole, but not contain it. It can reference a ClusterRole in the global namespace, and adds who information via Subject.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nClusterRoleBinding references a ClusterRole, but not contain it. It can reference a ClusterRole in the global namespace, and adds who information via Subject.", "properties": { "apiVersion": { "type": "string", @@ -90772,7 +90791,7 @@ ] }, "kubernetes:rbac.authorization.k8s.io/v1:ClusterRolePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nClusterRole is a cluster level, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding or ClusterRoleBinding.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nClusterRole is a cluster level, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding or ClusterRoleBinding.", "properties": { "aggregationRule": { "$ref": "#/types/kubernetes:rbac.authorization.k8s.io/v1:AggregationRulePatch", @@ -91079,7 +91098,7 @@ ] }, "kubernetes:rbac.authorization.k8s.io/v1:RoleBindingPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nRoleBinding 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.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nRoleBinding 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.", "properties": { "apiVersion": { "type": "string", @@ -91225,7 +91244,7 @@ ] }, "kubernetes:rbac.authorization.k8s.io/v1:RolePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nRole is a namespaced, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nRole is a namespaced, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding.", "properties": { "apiVersion": { "type": "string", @@ -91533,7 +91552,7 @@ ] }, "kubernetes:rbac.authorization.k8s.io/v1alpha1:ClusterRoleBindingPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nClusterRoleBinding 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.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nClusterRoleBinding 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.", "properties": { "apiVersion": { "type": "string", @@ -91679,7 +91698,7 @@ ] }, "kubernetes:rbac.authorization.k8s.io/v1alpha1:ClusterRolePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nClusterRole 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.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nClusterRole 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.", "properties": { "aggregationRule": { "$ref": "#/types/kubernetes:rbac.authorization.k8s.io/v1alpha1:AggregationRulePatch", @@ -91986,7 +92005,7 @@ ] }, "kubernetes:rbac.authorization.k8s.io/v1alpha1:RoleBindingPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nRoleBinding 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.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nRoleBinding 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.", "properties": { "apiVersion": { "type": "string", @@ -92132,7 +92151,7 @@ ] }, "kubernetes:rbac.authorization.k8s.io/v1alpha1:RolePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nRole is a namespaced, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 Role, and will no longer be served in v1.20.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nRole is a namespaced, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 Role, and will no longer be served in v1.20.", "properties": { "apiVersion": { "type": "string", @@ -92440,7 +92459,7 @@ ] }, "kubernetes:rbac.authorization.k8s.io/v1beta1:ClusterRoleBindingPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nClusterRoleBinding 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.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nClusterRoleBinding 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.", "properties": { "apiVersion": { "type": "string", @@ -92586,7 +92605,7 @@ ] }, "kubernetes:rbac.authorization.k8s.io/v1beta1:ClusterRolePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nClusterRole 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.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nClusterRole 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.", "properties": { "aggregationRule": { "$ref": "#/types/kubernetes:rbac.authorization.k8s.io/v1beta1:AggregationRulePatch", @@ -92893,7 +92912,7 @@ ] }, "kubernetes:rbac.authorization.k8s.io/v1beta1:RoleBindingPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nRoleBinding 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.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nRoleBinding 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.", "properties": { "apiVersion": { "type": "string", @@ -93039,7 +93058,7 @@ ] }, "kubernetes:rbac.authorization.k8s.io/v1beta1:RolePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nRole is a namespaced, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 Role, and will no longer be served in v1.20.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nRole is a namespaced, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 Role, and will no longer be served in v1.20.", "properties": { "apiVersion": { "type": "string", @@ -93244,7 +93263,7 @@ ] }, "kubernetes:resource.k8s.io/v1alpha1:PodSchedulingPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPodScheduling objects hold information that is needed to schedule a Pod with ResourceClaims that use \"WaitForFirstConsumer\" allocation mode.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPodScheduling objects hold information that is needed to schedule a Pod with ResourceClaims that use \"WaitForFirstConsumer\" allocation mode.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.", "properties": { "apiVersion": { "type": "string", @@ -93445,7 +93464,7 @@ ] }, "kubernetes:resource.k8s.io/v1alpha1:ResourceClaimPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceClaim describes which resources are needed by a resource consumer. Its status tracks whether the resource has been allocated and what the resulting attributes are.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceClaim describes which resources are needed by a resource consumer. Its status tracks whether the resource has been allocated and what the resulting attributes are.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.", "properties": { "apiVersion": { "type": "string", @@ -93646,7 +93665,7 @@ ] }, "kubernetes:resource.k8s.io/v1alpha1:ResourceClaimTemplatePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceClaimTemplate is used to produce ResourceClaim objects.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceClaimTemplate is used to produce ResourceClaim objects.", "properties": { "apiVersion": { "type": "string", @@ -93862,7 +93881,7 @@ ] }, "kubernetes:resource.k8s.io/v1alpha1:ResourceClassPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceClass is used by administrators to influence how resources are allocated.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceClass is used by administrators to influence how resources are allocated.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.", "properties": { "apiVersion": { "type": "string", @@ -94076,7 +94095,7 @@ ] }, "kubernetes:resource.k8s.io/v1alpha2:PodSchedulingContextPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPodSchedulingContext objects hold information that is needed to schedule a Pod with ResourceClaims that use \"WaitForFirstConsumer\" allocation mode.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPodSchedulingContext objects hold information that is needed to schedule a Pod with ResourceClaims that use \"WaitForFirstConsumer\" allocation mode.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.", "properties": { "apiVersion": { "type": "string", @@ -94432,7 +94451,7 @@ ] }, "kubernetes:resource.k8s.io/v1alpha2:ResourceClaimParametersPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceClaimParameters defines resource requests for a ResourceClaim in an in-tree format understood by Kubernetes.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceClaimParameters defines resource requests for a ResourceClaim in an in-tree format understood by Kubernetes.", "properties": { "apiVersion": { "type": "string", @@ -94510,7 +94529,7 @@ } }, "kubernetes:resource.k8s.io/v1alpha2:ResourceClaimPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceClaim describes which resources are needed by a resource consumer. Its status tracks whether the resource has been allocated and what the resulting attributes are.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceClaim describes which resources are needed by a resource consumer. Its status tracks whether the resource has been allocated and what the resulting attributes are.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.", "properties": { "apiVersion": { "type": "string", @@ -94711,7 +94730,7 @@ ] }, "kubernetes:resource.k8s.io/v1alpha2:ResourceClaimTemplatePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceClaimTemplate is used to produce ResourceClaim objects.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceClaimTemplate is used to produce ResourceClaim objects.", "properties": { "apiVersion": { "type": "string", @@ -95098,7 +95117,7 @@ ] }, "kubernetes:resource.k8s.io/v1alpha2:ResourceClassParametersPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceClassParameters defines resource requests for a ResourceClass in an in-tree format understood by Kubernetes.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceClassParameters defines resource requests for a ResourceClass in an in-tree format understood by Kubernetes.", "properties": { "apiVersion": { "type": "string", @@ -95182,7 +95201,7 @@ } }, "kubernetes:resource.k8s.io/v1alpha2:ResourceClassPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceClass is used by administrators to influence how resources are allocated.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceClass is used by administrators to influence how resources are allocated.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.", "properties": { "apiVersion": { "type": "string", @@ -95420,7 +95439,7 @@ ] }, "kubernetes:resource.k8s.io/v1alpha2:ResourceSlicePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceSlice provides information about available resources on individual nodes.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nResourceSlice provides information about available resources on individual nodes.", "properties": { "apiVersion": { "type": "string", @@ -95662,7 +95681,7 @@ ] }, "kubernetes:scheduling.k8s.io/v1:PriorityClassPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPriorityClass defines mapping from a priority class name to the priority integer value. The value can be any valid integer.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPriorityClass defines mapping from a priority class name to the priority integer value. The value can be any valid integer.", "properties": { "apiVersion": { "type": "string", @@ -95921,7 +95940,7 @@ ] }, "kubernetes:scheduling.k8s.io/v1alpha1:PriorityClassPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDEPRECATED - This group version of PriorityClass is deprecated by scheduling.k8s.io/v1/PriorityClass. PriorityClass defines mapping from a priority class name to the priority integer value. The value can be any valid integer.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDEPRECATED - This group version of PriorityClass is deprecated by scheduling.k8s.io/v1/PriorityClass. PriorityClass defines mapping from a priority class name to the priority integer value. The value can be any valid integer.", "properties": { "apiVersion": { "type": "string", @@ -96180,7 +96199,7 @@ ] }, "kubernetes:scheduling.k8s.io/v1beta1:PriorityClassPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDEPRECATED - This group version of PriorityClass is deprecated by scheduling.k8s.io/v1/PriorityClass. PriorityClass defines mapping from a priority class name to the priority integer value. The value can be any valid integer.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDEPRECATED - This group version of PriorityClass is deprecated by scheduling.k8s.io/v1/PriorityClass. PriorityClass defines mapping from a priority class name to the priority integer value. The value can be any valid integer.", "properties": { "apiVersion": { "type": "string", @@ -96394,7 +96413,7 @@ ] }, "kubernetes:settings.k8s.io/v1alpha1:PodPresetPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPodPreset is a policy resource that defines additional runtime requirements for a Pod.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nPodPreset is a policy resource that defines additional runtime requirements for a Pod.", "properties": { "apiVersion": { "type": "string", @@ -96581,7 +96600,7 @@ ] }, "kubernetes:storage.k8s.io/v1:CSIDriverPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCSIDriver captures information about a Container Storage Interface (CSI) volume driver deployed on the cluster. Kubernetes attach detach controller uses this object to determine whether attach is required. Kubelet uses this object to determine whether pod information needs to be passed on mount. CSIDriver objects are non-namespaced.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCSIDriver captures information about a Container Storage Interface (CSI) volume driver deployed on the cluster. Kubernetes attach detach controller uses this object to determine whether attach is required. Kubelet uses this object to determine whether pod information needs to be passed on mount. CSIDriver objects are non-namespaced.", "properties": { "apiVersion": { "type": "string", @@ -96777,7 +96796,7 @@ ] }, "kubernetes:storage.k8s.io/v1:CSINodePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCSINode holds information about all CSI drivers installed on a node. CSI drivers do not need to create the CSINode object directly. As long as they use the node-driver-registrar sidecar container, the kubelet will automatically populate the CSINode object for the CSI driver as part of kubelet plugin registration. CSINode has the same name as a node. If the object is missing, it means either there are no CSI Drivers available on the node, or the Kubelet version is low enough that it doesn't create this object. CSINode has an OwnerReference that points to the corresponding node object.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCSINode holds information about all CSI drivers installed on a node. CSI drivers do not need to create the CSINode object directly. As long as they use the node-driver-registrar sidecar container, the kubelet will automatically populate the CSINode object for the CSI driver as part of kubelet plugin registration. CSINode has the same name as a node. If the object is missing, it means either there are no CSI Drivers available on the node, or the Kubelet version is low enough that it doesn't create this object. CSINode has an OwnerReference that points to the corresponding node object.", "properties": { "apiVersion": { "type": "string", @@ -97006,7 +97025,7 @@ ] }, "kubernetes:storage.k8s.io/v1:CSIStorageCapacityPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCSIStorageCapacity stores the result of one CSI GetCapacity call. For a given StorageClass, this describes the available capacity in a particular topology segment. This can be used when considering where to instantiate new PersistentVolumes.\n\nFor example this can express things like: - StorageClass \"standard\" has \"1234 GiB\" available in \"topology.kubernetes.io/zone=us-east1\" - StorageClass \"localssd\" has \"10 GiB\" available in \"kubernetes.io/hostname=knode-abc123\"\n\nThe following three cases all imply that no capacity is available for a certain combination: - no object exists with suitable topology and storage class name - such an object exists, but the capacity is unset - such an object exists, but the capacity is zero\n\nThe producer of these objects can decide which approach is more suitable.\n\nThey are consumed by the kube-scheduler when a CSI driver opts into capacity-aware scheduling with CSIDriverSpec.StorageCapacity. The scheduler compares the MaximumVolumeSize against the requested size of pending volumes to filter out unsuitable nodes. If MaximumVolumeSize is unset, it falls back to a comparison against the less precise Capacity. If that is also unset, the scheduler assumes that capacity is insufficient and tries some other node.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCSIStorageCapacity stores the result of one CSI GetCapacity call. For a given StorageClass, this describes the available capacity in a particular topology segment. This can be used when considering where to instantiate new PersistentVolumes.\n\nFor example this can express things like: - StorageClass \"standard\" has \"1234 GiB\" available in \"topology.kubernetes.io/zone=us-east1\" - StorageClass \"localssd\" has \"10 GiB\" available in \"kubernetes.io/hostname=knode-abc123\"\n\nThe following three cases all imply that no capacity is available for a certain combination: - no object exists with suitable topology and storage class name - such an object exists, but the capacity is unset - such an object exists, but the capacity is zero\n\nThe producer of these objects can decide which approach is more suitable.\n\nThey are consumed by the kube-scheduler when a CSI driver opts into capacity-aware scheduling with CSIDriverSpec.StorageCapacity. The scheduler compares the MaximumVolumeSize against the requested size of pending volumes to filter out unsuitable nodes. If MaximumVolumeSize is unset, it falls back to a comparison against the less precise Capacity. If that is also unset, the scheduler assumes that capacity is insufficient and tries some other node.", "properties": { "apiVersion": { "type": "string", @@ -97310,7 +97329,7 @@ ] }, "kubernetes:storage.k8s.io/v1:StorageClassPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nStorageClass describes the parameters for a class of storage for which PersistentVolumes can be dynamically provisioned.\n\nStorageClasses are non-namespaced; the name of the storage class according to etcd is in ObjectMeta.Name.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nStorageClass describes the parameters for a class of storage for which PersistentVolumes can be dynamically provisioned.\n\nStorageClasses are non-namespaced; the name of the storage class according to etcd is in ObjectMeta.Name.", "properties": { "allowVolumeExpansion": { "type": "boolean", @@ -97586,7 +97605,7 @@ ] }, "kubernetes:storage.k8s.io/v1:VolumeAttachmentPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nVolumeAttachment captures the intent to attach or detach the specified volume to/from the specified node.\n\nVolumeAttachment objects are non-namespaced.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nVolumeAttachment captures the intent to attach or detach the specified volume to/from the specified node.\n\nVolumeAttachment objects are non-namespaced.", "properties": { "apiVersion": { "type": "string", @@ -97798,7 +97817,7 @@ ] }, "kubernetes:storage.k8s.io/v1alpha1:VolumeAttachmentPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nVolumeAttachment captures the intent to attach or detach the specified volume to/from the specified node.\n\nVolumeAttachment objects are non-namespaced.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nVolumeAttachment captures the intent to attach or detach the specified volume to/from the specified node.\n\nVolumeAttachment objects are non-namespaced.", "properties": { "apiVersion": { "type": "string", @@ -98013,7 +98032,7 @@ ] }, "kubernetes:storage.k8s.io/v1alpha1:VolumeAttributesClassPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nVolumeAttributesClass represents a specification of mutable volume attributes defined by the CSI driver. The class can be specified during dynamic provisioning of PersistentVolumeClaims, and changed in the PersistentVolumeClaim spec after provisioning.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nVolumeAttributesClass represents a specification of mutable volume attributes defined by the CSI driver. The class can be specified during dynamic provisioning of PersistentVolumeClaims, and changed in the PersistentVolumeClaim spec after provisioning.", "properties": { "apiVersion": { "type": "string", @@ -98219,7 +98238,7 @@ ] }, "kubernetes:storage.k8s.io/v1beta1:CSIDriverPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCSIDriver captures information about a Container Storage Interface (CSI) volume driver deployed on the cluster. CSI drivers do not need to create the CSIDriver object directly. Instead they may use the cluster-driver-registrar sidecar container. When deployed with a CSI driver it automatically creates a CSIDriver object representing the driver. Kubernetes attach detach controller uses this object to determine whether attach is required. Kubelet uses this object to determine whether pod information needs to be passed on mount. CSIDriver objects are non-namespaced.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCSIDriver captures information about a Container Storage Interface (CSI) volume driver deployed on the cluster. CSI drivers do not need to create the CSIDriver object directly. Instead they may use the cluster-driver-registrar sidecar container. When deployed with a CSI driver it automatically creates a CSIDriver object representing the driver. Kubernetes attach detach controller uses this object to determine whether attach is required. Kubelet uses this object to determine whether pod information needs to be passed on mount. CSIDriver objects are non-namespaced.", "properties": { "apiVersion": { "type": "string", @@ -98416,7 +98435,7 @@ ] }, "kubernetes:storage.k8s.io/v1beta1:CSINodePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCSINode holds information about all CSI drivers installed on a node. CSI drivers do not need to create the CSINode object directly. As long as they use the node-driver-registrar sidecar container, the kubelet will automatically populate the CSINode object for the CSI driver as part of kubelet plugin registration. CSINode has the same name as a node. If the object is missing, it means either there are no CSI Drivers available on the node, or the Kubelet version is low enough that it doesn't create this object. CSINode has an OwnerReference that points to the corresponding node object.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCSINode holds information about all CSI drivers installed on a node. CSI drivers do not need to create the CSINode object directly. As long as they use the node-driver-registrar sidecar container, the kubelet will automatically populate the CSINode object for the CSI driver as part of kubelet plugin registration. CSINode has the same name as a node. If the object is missing, it means either there are no CSI Drivers available on the node, or the Kubelet version is low enough that it doesn't create this object. CSINode has an OwnerReference that points to the corresponding node object.", "properties": { "apiVersion": { "type": "string", @@ -98646,7 +98665,7 @@ ] }, "kubernetes:storage.k8s.io/v1beta1:CSIStorageCapacityPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCSIStorageCapacity stores the result of one CSI GetCapacity call. For a given StorageClass, this describes the available capacity in a particular topology segment. This can be used when considering where to instantiate new PersistentVolumes.\n\nFor example this can express things like: - StorageClass \"standard\" has \"1234 GiB\" available in \"topology.kubernetes.io/zone=us-east1\" - StorageClass \"localssd\" has \"10 GiB\" available in \"kubernetes.io/hostname=knode-abc123\"\n\nThe following three cases all imply that no capacity is available for a certain combination: - no object exists with suitable topology and storage class name - such an object exists, but the capacity is unset - such an object exists, but the capacity is zero\n\nThe producer of these objects can decide which approach is more suitable.\n\nThey are consumed by the kube-scheduler when a CSI driver opts into capacity-aware scheduling with CSIDriverSpec.StorageCapacity. The scheduler compares the MaximumVolumeSize against the requested size of pending volumes to filter out unsuitable nodes. If MaximumVolumeSize is unset, it falls back to a comparison against the less precise Capacity. If that is also unset, the scheduler assumes that capacity is insufficient and tries some other node.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nCSIStorageCapacity stores the result of one CSI GetCapacity call. For a given StorageClass, this describes the available capacity in a particular topology segment. This can be used when considering where to instantiate new PersistentVolumes.\n\nFor example this can express things like: - StorageClass \"standard\" has \"1234 GiB\" available in \"topology.kubernetes.io/zone=us-east1\" - StorageClass \"localssd\" has \"10 GiB\" available in \"kubernetes.io/hostname=knode-abc123\"\n\nThe following three cases all imply that no capacity is available for a certain combination: - no object exists with suitable topology and storage class name - such an object exists, but the capacity is unset - such an object exists, but the capacity is zero\n\nThe producer of these objects can decide which approach is more suitable.\n\nThey are consumed by the kube-scheduler when a CSI driver opts into capacity-aware scheduling with CSIDriverSpec.StorageCapacity. The scheduler compares the MaximumVolumeSize against the requested size of pending volumes to filter out unsuitable nodes. If MaximumVolumeSize is unset, it falls back to a comparison against the less precise Capacity. If that is also unset, the scheduler assumes that capacity is insufficient and tries some other node.", "properties": { "apiVersion": { "type": "string", @@ -98950,7 +98969,7 @@ ] }, "kubernetes:storage.k8s.io/v1beta1:StorageClassPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nStorageClass describes the parameters for a class of storage for which PersistentVolumes can be dynamically provisioned.\n\nStorageClasses are non-namespaced; the name of the storage class according to etcd is in ObjectMeta.Name.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nStorageClass describes the parameters for a class of storage for which PersistentVolumes can be dynamically provisioned.\n\nStorageClasses are non-namespaced; the name of the storage class according to etcd is in ObjectMeta.Name.", "properties": { "allowVolumeExpansion": { "type": "boolean", @@ -99226,7 +99245,7 @@ ] }, "kubernetes:storage.k8s.io/v1beta1:VolumeAttachmentPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nVolumeAttachment captures the intent to attach or detach the specified volume to/from the specified node.\n\nVolumeAttachment objects are non-namespaced.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nVolumeAttachment captures the intent to attach or detach the specified volume to/from the specified node.\n\nVolumeAttachment objects are non-namespaced.", "properties": { "apiVersion": { "type": "string", @@ -99427,7 +99446,7 @@ ] }, "kubernetes:storagemigration.k8s.io/v1alpha1:StorageVersionMigrationPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nStorageVersionMigration represents a migration of stored data to the latest storage version.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nStorageVersionMigration represents a migration of stored data to the latest storage version.", "properties": { "apiVersion": { "type": "string", diff --git a/provider/pkg/await/await.go b/provider/pkg/await/await.go index 407f30cc00..c14bbf9c5f 100644 --- a/provider/pkg/await/await.go +++ b/provider/pkg/await/await.go @@ -70,6 +70,7 @@ type ProviderConfig struct { FieldManager string ClusterVersion *cluster.ServerVersion ServerSideApply bool + EnableUpsert bool ClientSet *clients.DynamicClientSet DedupLogger *logging.DedupLogger @@ -192,7 +193,7 @@ func Creation(c CreateConfig) (*unstructured.Unstructured, error) { } } - if c.ServerSideApply { + if c.ServerSideApply && c.EnableUpsert { force := patchForce(c.Inputs, nil, c.Preview) options := metav1.PatchOptions{ FieldManager: c.FieldManager, diff --git a/provider/pkg/gen/schema.go b/provider/pkg/gen/schema.go index 436f732a55..ca559d750a 100644 --- a/provider/pkg/gen/schema.go +++ b/provider/pkg/gen/schema.go @@ -90,6 +90,16 @@ func PulumiSchema(swagger map[string]any) pschema.PackageSpec { Description: "BETA FEATURE - If present and set to true, allow ConfigMaps to be mutated.\nThis feature is in developer preview, and is disabled by default.\n\nThis config can be specified in the following ways using this precedence:\n1. This `enableConfigMapMutable` parameter.\n2. The `PULUMI_K8S_ENABLE_CONFIGMAP_MUTABLE` environment variable.", TypeSpec: pschema.TypeSpec{Type: "boolean"}, }, + "enableUpsert": { + Description: "If present and set to false, the provider will surface errors if a create operation would overwrite existing resources in the cluster.", + TypeSpec: pschema.TypeSpec{Type: "boolean"}, + Default: true, + DefaultInfo: &pschema.DefaultSpec{ + Environment: []string{ + "PULUMI_K8S_ENABLE_UPSERT", + }, + }, + }, "renderYamlToDirectory": { Description: "BETA FEATURE - If present, render resource manifests to this directory. In this mode, resources will not\nbe created on a Kubernetes cluster, but the rendered manifests will be kept in sync with changes\nto the Pulumi program. This feature is in developer preview, and is disabled by default.\n\nNote that some computed Outputs such as status fields will not be populated\nsince the resources are not created on a Kubernetes cluster. These Output values will remain undefined,\nand may result in an error if they are referenced by other resources. Also note that any secret values\nused in these resources will be rendered in plaintext to the resulting YAML.", TypeSpec: pschema.TypeSpec{Type: "string"}, @@ -177,6 +187,15 @@ func PulumiSchema(swagger map[string]any) pschema.PackageSpec { Description: "BETA FEATURE - If present and set to true, allow ConfigMaps to be mutated.\nThis feature is in developer preview, and is disabled by default.\n\nThis config can be specified in the following ways using this precedence:\n1. This `enableConfigMapMutable` parameter.\n2. The `PULUMI_K8S_ENABLE_CONFIGMAP_MUTABLE` environment variable.", TypeSpec: pschema.TypeSpec{Type: "boolean"}, }, + "enableUpsert": { + Description: "If present and set to false, the provider will surface errors if a create operation would overwrite existing resources in the cluster.", + TypeSpec: pschema.TypeSpec{Type: "boolean"}, + DefaultInfo: &pschema.DefaultSpec{ + Environment: []string{ + "PULUMI_K8S_ENABLE_UPSERT", + }, + }, + }, "renderYamlToDirectory": { Description: "BETA FEATURE - If present, render resource manifests to this directory. In this mode, resources will not\nbe created on a Kubernetes cluster, but the rendered manifests will be kept in sync with changes\nto the Pulumi program. This feature is in developer preview, and is disabled by default.\n\nNote that some computed Outputs such as status fields will not be populated\nsince the resources are not created on a Kubernetes cluster. These Output values will remain undefined,\nand may result in an error if they are referenced by other resources. Also note that any secret values\nused in these resources will be rendered in plaintext to the resulting YAML.", TypeSpec: pschema.TypeSpec{Type: "string"}, @@ -425,8 +444,8 @@ func PulumiSchema(swagger map[string]any) pschema.PackageSpec { } patchDescription := `Patch resources are used to modify existing Kubernetes resources by using -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. +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/how-to-guides/managing-resources-with-server-side-apply/) for additional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.` diff --git a/provider/pkg/provider/provider.go b/provider/pkg/provider/provider.go index b8eabe8b9c..9c9b56b46f 100644 --- a/provider/pkg/provider/provider.go +++ b/provider/pkg/provider/provider.go @@ -130,6 +130,7 @@ type kubeProvider struct { skipUpdateUnreachable bool enableConfigMapMutable bool enableSecrets bool + enableUpsert bool suppressDeprecationWarnings bool suppressHelmHookWarnings bool serverSideApplyMode bool @@ -543,6 +544,17 @@ func (k *kubeProvider) Configure(_ context.Context, req *pulumirpc.ConfigureRequ k.enableConfigMapMutable = true } + enableUpsert := func() bool { + if enabled, exists := vars["kubernetes:config:enableUpsert"]; exists { + return enabled == trueStr + } + if enabled, exists := os.LookupEnv("PULUMI_K8S_ENABLE_UPSERT"); exists { + return enabled == trueStr + } + return true + } + k.enableUpsert = enableUpsert() + suppressDeprecationWarnings := func() bool { // If the provider flag is set, use that value to determine behavior. This will override the ENV var. if enabled, exists := vars["kubernetes:config:suppressDeprecationWarnings"]; exists { @@ -1849,6 +1861,7 @@ func (k *kubeProvider) Create( DedupLogger: logging.NewLogger(k.canceler.context, k.host, urn), Resources: resources, ServerSideApply: k.serverSideApplyMode, + EnableUpsert: k.enableUpsert, }, Inputs: newInputs, Timeout: req.Timeout, @@ -2096,6 +2109,8 @@ func (k *kubeProvider) Read(ctx context.Context, req *pulumirpc.ReadRequest) (*p ClientSet: k.clientSet, DedupLogger: logging.NewLogger(k.canceler.context, k.host, urn), Resources: resources, + ServerSideApply: k.serverSideApplyMode, + EnableUpsert: k.enableUpsert, }, Inputs: oldInputs, ReadFromCluster: readFromCluster, @@ -2344,6 +2359,7 @@ func (k *kubeProvider) Update( DedupLogger: logging.NewLogger(k.canceler.context, k.host, urn), Resources: resources, ServerSideApply: k.serverSideApplyMode, + EnableUpsert: k.enableUpsert, }, OldInputs: oldLivePruned, OldOutputs: oldLive, @@ -2502,6 +2518,7 @@ func (k *kubeProvider) Delete(ctx context.Context, req *pulumirpc.DeleteRequest) DedupLogger: logging.NewLogger(k.canceler.context, k.host, urn), Resources: resources, ServerSideApply: k.serverSideApplyMode, + EnableUpsert: k.enableUpsert, }, Inputs: oldInputs, Outputs: current, diff --git a/tests/provider/create/without-upsert/Pulumi.yaml b/tests/provider/create/without-upsert/Pulumi.yaml new file mode 100644 index 0000000000..7454aa7c16 --- /dev/null +++ b/tests/provider/create/without-upsert/Pulumi.yaml @@ -0,0 +1,30 @@ +name: create-without-upsert +runtime: yaml +description: | + Providers can opt-in to Create behavior that fails fast + when it would overwrite a resource that already exists in + the cluster. + +resources: + ns: + type: kubernetes:core/v1:Namespace + + provider: + type: pulumi:providers:kubernetes + properties: + namespace: ${ns.metadata.name} + enableUpsert: false + + pod1: + type: kubernetes:core/v1:Pod + properties: + metadata: + name: nginx + spec: + containers: + - image: nginx:1.14.2 + name: nginx + ports: + - containerPort: 80 + options: + provider: ${provider} diff --git a/tests/provider/create/without-upsert/step2/Pulumi.yaml b/tests/provider/create/without-upsert/step2/Pulumi.yaml new file mode 100644 index 0000000000..64e294ac8a --- /dev/null +++ b/tests/provider/create/without-upsert/step2/Pulumi.yaml @@ -0,0 +1,46 @@ +name: create-without-upsert +runtime: yaml +description: | + Providers can opt-in to Create behavior that fails fast + when it would overwrite a resource that already exists in + the cluster. + +resources: + ns: + type: kubernetes:core/v1:Namespace + + provider: + type: pulumi:providers:kubernetes + properties: + namespace: ${ns.metadata.name} + enableUpsert: false + + pod1: + type: kubernetes:core/v1:Pod + properties: + metadata: + name: nginx + spec: + containers: + - image: nginx:1.14.2 + name: nginx + ports: + - containerPort: 80 + options: + provider: ${provider} + + # Attempt to create a new pod that would overwrite the + # cluster's existing pod. + pod2: + type: kubernetes:core/v1:Pod + properties: + metadata: + name: nginx + spec: + containers: + - image: nginx:1.14.2 + name: nginx + ports: + - containerPort: 80 + options: + provider: ${provider} diff --git a/tests/provider/create/without-upsert/step3/Pulumi.yaml b/tests/provider/create/without-upsert/step3/Pulumi.yaml new file mode 100644 index 0000000000..84aa219963 --- /dev/null +++ b/tests/provider/create/without-upsert/step3/Pulumi.yaml @@ -0,0 +1,45 @@ +name: create-without-upsert +runtime: yaml +description: | + Providers can opt-in to Create behavior that fails fast + when it would overwrite a resource that already exists in + the cluster. + +resources: + ns: + type: kubernetes:core/v1:Namespace + + provider: + type: pulumi:providers:kubernetes + properties: + namespace: ${ns.metadata.name} + # Try again with upsert re-enabled. + enableUpsert: true + + pod1: + type: kubernetes:core/v1:Pod + properties: + metadata: + name: nginx + spec: + containers: + - image: nginx:1.14.2 + name: nginx + ports: + - containerPort: 80 + options: + provider: ${provider} + + pod2: + type: kubernetes:core/v1:Pod + properties: + metadata: + name: nginx + spec: + containers: + - image: nginx:1.14.2 + name: nginx + ports: + - containerPort: 80 + options: + provider: ${provider} diff --git a/tests/provider/create_test.go b/tests/provider/create_test.go new file mode 100644 index 0000000000..135ba2191c --- /dev/null +++ b/tests/provider/create_test.go @@ -0,0 +1,30 @@ +package provider + +import ( + "context" + "testing" + + "github.com/pulumi/providertest/pulumitest" + "github.com/stretchr/testify/assert" +) + +func TestCreateWithoutUpsert(t *testing.T) { + t.Parallel() + ctx := context.Background() + test := pulumitest.NewPulumiTest(t, "create/without-upsert") + t.Cleanup(func() { + test.Destroy() + }) + + test.Up() + + // Create a new pod resource referencing one that already exists -- should fail. + test.UpdateSource("create/without-upsert/step2") + _, err := test.CurrentStack().Up(ctx) + + assert.ErrorContains(t, err, "already exists") + + // Try again with upsert re-enabled -- should succeed. + test.UpdateSource("create/without-upsert/step3") + test.Up() +} From aadda8c422291d5130ee6c59999104071da80949 Mon Sep 17 00:00:00 2001 From: Bryce Lampe Date: Wed, 8 May 2024 14:55:33 -0700 Subject: [PATCH 2/4] changelog --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 6eedd13b52..d2ee48a6a3 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,7 +2,7 @@ - Fix Release behavior to deep merge `valueYamlFiles` to match Helm. (https://github.com/pulumi/pulumi-kubernetes/pull/2963) - Add field manager's name to server-side apply conflict errors. (https://github.com/pulumi/pulumi-kubernetes/pull/2983) -- Add `enableUpsert` provider configuration to control apply behavior on resource creation. +- Add `enableUpsert` provider configuration to control apply behavior on resource creation. (https://github.com/pulumi/pulumi-kubernetes/pull/3000) ## 4.11.0 (April 17, 2024) From a31a0ce5684b1311964ca7bea70cb14920ea1624 Mon Sep 17 00:00:00 2001 From: Bryce Lampe Date: Wed, 8 May 2024 15:05:29 -0700 Subject: [PATCH 3/4] Fix tests --- provider/pkg/await/await_test.go | 2 ++ 1 file changed, 2 insertions(+) diff --git a/provider/pkg/await/await_test.go b/provider/pkg/await/await_test.go index 764a22b8d9..b139cb36cd 100644 --- a/provider/pkg/await/await_test.go +++ b/provider/pkg/await/await_test.go @@ -325,6 +325,7 @@ func Test_Creation(t *testing.T) { DedupLogger: logging.NewLogger(context.Background(), host, urn), Resources: resources, ServerSideApply: tt.args.serverSideApply, + EnableUpsert: tt.args.serverSideApply, awaiters: map[string]awaitSpec{}, }, Inputs: tt.args.inputs, @@ -365,6 +366,7 @@ func TestAwaitSSAConflict(t *testing.T) { FieldManager: "test", ClientSet: client, ServerSideApply: true, + EnableUpsert: true, } config := CreateConfig{ ProviderConfig: pconfig, From 0006ded9ba2d08e0b044ee7dcc7b089b02b0504c Mon Sep 17 00:00:00 2001 From: Bryce Lampe Date: Wed, 8 May 2024 15:09:30 -0700 Subject: [PATCH 4/4] Regenerate SDK --- sdk/dotnet/Config/Config.cs | 10 +++++ sdk/dotnet/Provider.cs | 7 ++++ sdk/go/kubernetes/config/config.go | 13 +++++++ sdk/go/kubernetes/provider.go | 9 +++++ .../java/com/pulumi/kubernetes/Config.java | 7 ++++ .../com/pulumi/kubernetes/ProviderArgs.java | 38 +++++++++++++++++++ sdk/nodejs/provider.ts | 5 +++ sdk/python/pulumi_kubernetes/provider.py | 24 ++++++++++++ 8 files changed, 113 insertions(+) diff --git a/sdk/dotnet/Config/Config.cs b/sdk/dotnet/Config/Config.cs index 69ddc8683b..543d7a1675 100644 --- a/sdk/dotnet/Config/Config.cs +++ b/sdk/dotnet/Config/Config.cs @@ -98,6 +98,16 @@ public static bool? EnableServerSideApply set => _enableServerSideApply.Set(value); } + private static readonly __Value _enableUpsert = new __Value(() => __config.GetBoolean("enableUpsert") ?? Utilities.GetEnvBoolean("PULUMI_K8S_ENABLE_UPSERT") ?? true); + /// + /// If present and set to false, the provider will surface errors if a create operation would overwrite existing resources in the cluster. + /// + public static bool? EnableUpsert + { + get => _enableUpsert.Get(); + set => _enableUpsert.Set(value); + } + private static readonly __Value _kubeconfig = new __Value(() => __config.Get("kubeconfig")); /// /// The contents of a kubeconfig file or the path to a kubeconfig file. If this is set, this config will be used instead of $KUBECONFIG. diff --git a/sdk/dotnet/Provider.cs b/sdk/dotnet/Provider.cs index 7a5d7a4b23..feb5bad7d9 100644 --- a/sdk/dotnet/Provider.cs +++ b/sdk/dotnet/Provider.cs @@ -82,6 +82,12 @@ public sealed class ProviderArgs : global::Pulumi.ResourceArgs [Input("enableServerSideApply", json: true)] public Input? EnableServerSideApply { get; set; } + /// + /// If present and set to false, the provider will surface errors if a create operation would overwrite existing resources in the cluster. + /// + [Input("enableUpsert", json: true)] + public Input? EnableUpsert { get; set; } + /// /// Options to configure the Helm Release resource. /// @@ -147,6 +153,7 @@ public ProviderArgs() DeleteUnreachable = Utilities.GetEnvBoolean("PULUMI_K8S_DELETE_UNREACHABLE"); EnableConfigMapMutable = Utilities.GetEnvBoolean("PULUMI_K8S_ENABLE_CONFIGMAP_MUTABLE"); EnableServerSideApply = Utilities.GetEnvBoolean("PULUMI_K8S_ENABLE_SERVER_SIDE_APPLY"); + EnableUpsert = Utilities.GetEnvBoolean("PULUMI_K8S_ENABLE_UPSERT"); KubeConfig = Utilities.GetEnv("KUBECONFIG"); SkipUpdateUnreachable = Utilities.GetEnvBoolean("PULUMI_K8S_SKIP_UPDATE_UNREACHABLE"); SuppressDeprecationWarnings = Utilities.GetEnvBoolean("PULUMI_K8S_SUPPRESS_DEPRECATION_WARNINGS"); diff --git a/sdk/go/kubernetes/config/config.go b/sdk/go/kubernetes/config/config.go index 14bb8b9d58..0dc69d9f37 100644 --- a/sdk/go/kubernetes/config/config.go +++ b/sdk/go/kubernetes/config/config.go @@ -49,6 +49,19 @@ func GetEnableServerSideApply(ctx *pulumi.Context) bool { return config.GetBool(ctx, "kubernetes:enableServerSideApply") } +// If present and set to false, the provider will surface errors if a create operation would overwrite existing resources in the cluster. +func GetEnableUpsert(ctx *pulumi.Context) bool { + v, err := config.TryBool(ctx, "kubernetes:enableUpsert") + if err == nil { + return v + } + var value bool + if d := utilities.GetEnvOrDefault(true, utilities.ParseEnvBool, "PULUMI_K8S_ENABLE_UPSERT"); d != nil { + value = d.(bool) + } + return value +} + // The contents of a kubeconfig file or the path to a kubeconfig file. If this is set, this config will be used instead of $KUBECONFIG. func GetKubeconfig(ctx *pulumi.Context) string { return config.Get(ctx, "kubernetes:kubeconfig") diff --git a/sdk/go/kubernetes/provider.go b/sdk/go/kubernetes/provider.go index 06749043c9..5d343e7f0c 100644 --- a/sdk/go/kubernetes/provider.go +++ b/sdk/go/kubernetes/provider.go @@ -38,6 +38,11 @@ func NewProvider(ctx *pulumi.Context, args.EnableServerSideApply = pulumi.BoolPtr(d.(bool)) } } + if args.EnableUpsert == nil { + if d := utilities.GetEnvOrDefault(nil, utilities.ParseEnvBool, "PULUMI_K8S_ENABLE_UPSERT"); d != nil { + args.EnableUpsert = pulumi.BoolPtr(d.(bool)) + } + } if args.HelmReleaseSettings != nil { args.HelmReleaseSettings = args.HelmReleaseSettings.ToHelmReleaseSettingsPtrOutput().ApplyT(func(v *HelmReleaseSettings) *HelmReleaseSettings { return v.Defaults() }).(HelmReleaseSettingsPtrOutput) } @@ -90,6 +95,8 @@ type providerArgs struct { // If present and set to false, disable Server-Side Apply mode. // See https://github.com/pulumi/pulumi-kubernetes/issues/2011 for additional details. EnableServerSideApply *bool `pulumi:"enableServerSideApply"` + // If present and set to false, the provider will surface errors if a create operation would overwrite existing resources in the cluster. + EnableUpsert *bool `pulumi:"enableUpsert"` // Options to configure the Helm Release resource. HelmReleaseSettings *HelmReleaseSettings `pulumi:"helmReleaseSettings"` // Options for tuning the Kubernetes client used by a Provider. @@ -138,6 +145,8 @@ type ProviderArgs struct { // If present and set to false, disable Server-Side Apply mode. // See https://github.com/pulumi/pulumi-kubernetes/issues/2011 for additional details. EnableServerSideApply pulumi.BoolPtrInput + // If present and set to false, the provider will surface errors if a create operation would overwrite existing resources in the cluster. + EnableUpsert pulumi.BoolPtrInput // Options to configure the Helm Release resource. HelmReleaseSettings HelmReleaseSettingsPtrInput // Options for tuning the Kubernetes client used by a Provider. diff --git a/sdk/java/src/main/java/com/pulumi/kubernetes/Config.java b/sdk/java/src/main/java/com/pulumi/kubernetes/Config.java index 0f5cfcf907..4cfbedd673 100644 --- a/sdk/java/src/main/java/com/pulumi/kubernetes/Config.java +++ b/sdk/java/src/main/java/com/pulumi/kubernetes/Config.java @@ -59,6 +59,13 @@ public Optional enableReplaceCRD() { public Optional enableServerSideApply() { return Codegen.booleanProp("enableServerSideApply").config(config).get(); } +/** + * If present and set to false, the provider will surface errors if a create operation would overwrite existing resources in the cluster. + * + */ + public Optional enableUpsert() { + return Codegen.booleanProp("enableUpsert").config(config).env("PULUMI_K8S_ENABLE_UPSERT").def(true).get(); + } /** * The contents of a kubeconfig file or the path to a kubeconfig file. If this is set, this config will be used instead of $KUBECONFIG. * diff --git a/sdk/java/src/main/java/com/pulumi/kubernetes/ProviderArgs.java b/sdk/java/src/main/java/com/pulumi/kubernetes/ProviderArgs.java index a587b70e73..803ddc517f 100644 --- a/sdk/java/src/main/java/com/pulumi/kubernetes/ProviderArgs.java +++ b/sdk/java/src/main/java/com/pulumi/kubernetes/ProviderArgs.java @@ -106,6 +106,21 @@ public Optional> enableServerSideApply() { return Optional.ofNullable(this.enableServerSideApply); } + /** + * If present and set to false, the provider will surface errors if a create operation would overwrite existing resources in the cluster. + * + */ + @Import(name="enableUpsert", json=true) + private @Nullable Output enableUpsert; + + /** + * @return If present and set to false, the provider will surface errors if a create operation would overwrite existing resources in the cluster. + * + */ + public Optional> enableUpsert() { + return Optional.ofNullable(this.enableUpsert); + } + /** * Options to configure the Helm Release resource. * @@ -258,6 +273,7 @@ private ProviderArgs(ProviderArgs $) { this.deleteUnreachable = $.deleteUnreachable; this.enableConfigMapMutable = $.enableConfigMapMutable; this.enableServerSideApply = $.enableServerSideApply; + this.enableUpsert = $.enableUpsert; this.helmReleaseSettings = $.helmReleaseSettings; this.kubeClientSettings = $.kubeClientSettings; this.kubeconfig = $.kubeconfig; @@ -403,6 +419,27 @@ public Builder enableServerSideApply(Boolean enableServerSideApply) { return enableServerSideApply(Output.of(enableServerSideApply)); } + /** + * @param enableUpsert If present and set to false, the provider will surface errors if a create operation would overwrite existing resources in the cluster. + * + * @return builder + * + */ + public Builder enableUpsert(@Nullable Output enableUpsert) { + $.enableUpsert = enableUpsert; + return this; + } + + /** + * @param enableUpsert If present and set to false, the provider will surface errors if a create operation would overwrite existing resources in the cluster. + * + * @return builder + * + */ + public Builder enableUpsert(Boolean enableUpsert) { + return enableUpsert(Output.of(enableUpsert)); + } + /** * @param helmReleaseSettings Options to configure the Helm Release resource. * @@ -599,6 +636,7 @@ public ProviderArgs build() { $.deleteUnreachable = Codegen.booleanProp("deleteUnreachable").output().arg($.deleteUnreachable).env("PULUMI_K8S_DELETE_UNREACHABLE").getNullable(); $.enableConfigMapMutable = Codegen.booleanProp("enableConfigMapMutable").output().arg($.enableConfigMapMutable).env("PULUMI_K8S_ENABLE_CONFIGMAP_MUTABLE").getNullable(); $.enableServerSideApply = Codegen.booleanProp("enableServerSideApply").output().arg($.enableServerSideApply).env("PULUMI_K8S_ENABLE_SERVER_SIDE_APPLY").getNullable(); + $.enableUpsert = Codegen.booleanProp("enableUpsert").output().arg($.enableUpsert).env("PULUMI_K8S_ENABLE_UPSERT").getNullable(); $.kubeconfig = Codegen.stringProp("kubeconfig").output().arg($.kubeconfig).env("KUBECONFIG").getNullable(); $.skipUpdateUnreachable = Codegen.booleanProp("skipUpdateUnreachable").output().arg($.skipUpdateUnreachable).env("PULUMI_K8S_SKIP_UPDATE_UNREACHABLE").getNullable(); $.suppressDeprecationWarnings = Codegen.booleanProp("suppressDeprecationWarnings").output().arg($.suppressDeprecationWarnings).env("PULUMI_K8S_SUPPRESS_DEPRECATION_WARNINGS").getNullable(); diff --git a/sdk/nodejs/provider.ts b/sdk/nodejs/provider.ts index ddc19fd673..61c54a663e 100644 --- a/sdk/nodejs/provider.ts +++ b/sdk/nodejs/provider.ts @@ -42,6 +42,7 @@ export class Provider extends pulumi.ProviderResource { resourceInputs["deleteUnreachable"] = pulumi.output((args ? args.deleteUnreachable : undefined) ?? utilities.getEnvBoolean("PULUMI_K8S_DELETE_UNREACHABLE")).apply(JSON.stringify); resourceInputs["enableConfigMapMutable"] = pulumi.output((args ? args.enableConfigMapMutable : undefined) ?? utilities.getEnvBoolean("PULUMI_K8S_ENABLE_CONFIGMAP_MUTABLE")).apply(JSON.stringify); resourceInputs["enableServerSideApply"] = pulumi.output((args ? args.enableServerSideApply : undefined) ?? utilities.getEnvBoolean("PULUMI_K8S_ENABLE_SERVER_SIDE_APPLY")).apply(JSON.stringify); + resourceInputs["enableUpsert"] = pulumi.output((args ? args.enableUpsert : undefined) ?? utilities.getEnvBoolean("PULUMI_K8S_ENABLE_UPSERT")).apply(JSON.stringify); resourceInputs["helmReleaseSettings"] = pulumi.output(args ? (args.helmReleaseSettings ? pulumi.output(args.helmReleaseSettings).apply(inputs.helmReleaseSettingsProvideDefaults) : undefined) : undefined).apply(JSON.stringify); resourceInputs["kubeClientSettings"] = pulumi.output(args ? (args.kubeClientSettings ? pulumi.output(args.kubeClientSettings).apply(inputs.kubeClientSettingsProvideDefaults) : undefined) : undefined).apply(JSON.stringify); resourceInputs["kubeconfig"] = (args ? args.kubeconfig : undefined) ?? utilities.getEnv("KUBECONFIG"); @@ -86,6 +87,10 @@ export interface ProviderArgs { * See https://github.com/pulumi/pulumi-kubernetes/issues/2011 for additional details. */ enableServerSideApply?: pulumi.Input; + /** + * If present and set to false, the provider will surface errors if a create operation would overwrite existing resources in the cluster. + */ + enableUpsert?: pulumi.Input; /** * Options to configure the Helm Release resource. */ diff --git a/sdk/python/pulumi_kubernetes/provider.py b/sdk/python/pulumi_kubernetes/provider.py index 5292427b69..c4a397316d 100644 --- a/sdk/python/pulumi_kubernetes/provider.py +++ b/sdk/python/pulumi_kubernetes/provider.py @@ -20,6 +20,7 @@ def __init__(__self__, *, delete_unreachable: Optional[pulumi.Input[bool]] = None, enable_config_map_mutable: Optional[pulumi.Input[bool]] = None, enable_server_side_apply: Optional[pulumi.Input[bool]] = None, + enable_upsert: Optional[pulumi.Input[bool]] = None, helm_release_settings: Optional[pulumi.Input['HelmReleaseSettingsArgs']] = None, kube_client_settings: Optional[pulumi.Input['KubeClientSettingsArgs']] = None, kubeconfig: Optional[pulumi.Input[str]] = None, @@ -41,6 +42,7 @@ def __init__(__self__, *, 2. The `PULUMI_K8S_ENABLE_CONFIGMAP_MUTABLE` environment variable. :param pulumi.Input[bool] enable_server_side_apply: If present and set to false, disable Server-Side Apply mode. See https://github.com/pulumi/pulumi-kubernetes/issues/2011 for additional details. + :param pulumi.Input[bool] enable_upsert: If present and set to false, the provider will surface errors if a create operation would overwrite existing resources in the cluster. :param pulumi.Input['HelmReleaseSettingsArgs'] helm_release_settings: Options to configure the Helm Release resource. :param pulumi.Input['KubeClientSettingsArgs'] kube_client_settings: Options for tuning the Kubernetes client used by a Provider. :param pulumi.Input[str] kubeconfig: The contents of a kubeconfig file or the path to a kubeconfig file. @@ -78,6 +80,10 @@ def __init__(__self__, *, enable_server_side_apply = _utilities.get_env_bool('PULUMI_K8S_ENABLE_SERVER_SIDE_APPLY') if enable_server_side_apply is not None: pulumi.set(__self__, "enable_server_side_apply", enable_server_side_apply) + if enable_upsert is None: + enable_upsert = _utilities.get_env_bool('PULUMI_K8S_ENABLE_UPSERT') + if enable_upsert is not None: + pulumi.set(__self__, "enable_upsert", enable_upsert) if helm_release_settings is not None: pulumi.set(__self__, "helm_release_settings", helm_release_settings) if kube_client_settings is not None: @@ -169,6 +175,18 @@ def enable_server_side_apply(self) -> Optional[pulumi.Input[bool]]: def enable_server_side_apply(self, value: Optional[pulumi.Input[bool]]): pulumi.set(self, "enable_server_side_apply", value) + @property + @pulumi.getter(name="enableUpsert") + def enable_upsert(self) -> Optional[pulumi.Input[bool]]: + """ + If present and set to false, the provider will surface errors if a create operation would overwrite existing resources in the cluster. + """ + return pulumi.get(self, "enable_upsert") + + @enable_upsert.setter + def enable_upsert(self, value: Optional[pulumi.Input[bool]]): + pulumi.set(self, "enable_upsert", value) + @property @pulumi.getter(name="helmReleaseSettings") def helm_release_settings(self) -> Optional[pulumi.Input['HelmReleaseSettingsArgs']]: @@ -288,6 +306,7 @@ def __init__(__self__, delete_unreachable: Optional[pulumi.Input[bool]] = None, enable_config_map_mutable: Optional[pulumi.Input[bool]] = None, enable_server_side_apply: Optional[pulumi.Input[bool]] = None, + enable_upsert: Optional[pulumi.Input[bool]] = None, helm_release_settings: Optional[pulumi.Input[pulumi.InputType['HelmReleaseSettingsArgs']]] = None, kube_client_settings: Optional[pulumi.Input[pulumi.InputType['KubeClientSettingsArgs']]] = None, kubeconfig: Optional[pulumi.Input[str]] = None, @@ -313,6 +332,7 @@ def __init__(__self__, 2. The `PULUMI_K8S_ENABLE_CONFIGMAP_MUTABLE` environment variable. :param pulumi.Input[bool] enable_server_side_apply: If present and set to false, disable Server-Side Apply mode. See https://github.com/pulumi/pulumi-kubernetes/issues/2011 for additional details. + :param pulumi.Input[bool] enable_upsert: If present and set to false, the provider will surface errors if a create operation would overwrite existing resources in the cluster. :param pulumi.Input[pulumi.InputType['HelmReleaseSettingsArgs']] helm_release_settings: Options to configure the Helm Release resource. :param pulumi.Input[pulumi.InputType['KubeClientSettingsArgs']] kube_client_settings: Options for tuning the Kubernetes client used by a Provider. :param pulumi.Input[str] kubeconfig: The contents of a kubeconfig file or the path to a kubeconfig file. @@ -363,6 +383,7 @@ def _internal_init(__self__, delete_unreachable: Optional[pulumi.Input[bool]] = None, enable_config_map_mutable: Optional[pulumi.Input[bool]] = None, enable_server_side_apply: Optional[pulumi.Input[bool]] = None, + enable_upsert: Optional[pulumi.Input[bool]] = None, helm_release_settings: Optional[pulumi.Input[pulumi.InputType['HelmReleaseSettingsArgs']]] = None, kube_client_settings: Optional[pulumi.Input[pulumi.InputType['KubeClientSettingsArgs']]] = None, kubeconfig: Optional[pulumi.Input[str]] = None, @@ -391,6 +412,9 @@ def _internal_init(__self__, if enable_server_side_apply is None: enable_server_side_apply = _utilities.get_env_bool('PULUMI_K8S_ENABLE_SERVER_SIDE_APPLY') __props__.__dict__["enable_server_side_apply"] = pulumi.Output.from_input(enable_server_side_apply).apply(pulumi.runtime.to_json) if enable_server_side_apply is not None else None + if enable_upsert is None: + enable_upsert = _utilities.get_env_bool('PULUMI_K8S_ENABLE_UPSERT') + __props__.__dict__["enable_upsert"] = pulumi.Output.from_input(enable_upsert).apply(pulumi.runtime.to_json) if enable_upsert is not None else None __props__.__dict__["helm_release_settings"] = pulumi.Output.from_input(helm_release_settings).apply(pulumi.runtime.to_json) if helm_release_settings is not None else None __props__.__dict__["kube_client_settings"] = pulumi.Output.from_input(kube_client_settings).apply(pulumi.runtime.to_json) if kube_client_settings is not None else None if kubeconfig is None: