From 4ae1374f79d3a7f38b2926ae5803ae57df2fb6dd Mon Sep 17 00:00:00 2001 From: Anton Tayanovskyy Date: Tue, 1 Oct 2024 18:28:05 -0400 Subject: [PATCH] Do not specify pulumi sdk (#3239) ### Proposed changes Re: https://github.com/pulumi/ci-mgmt/issues/1091 Since the original dependency required higher SDK versions than 3.x.x., the remediation also upgrades SDK generators to latest. ### Related issues (optional) --- .../pulumi-resource-kubernetes/schema.json | 284 +++++++++--------- provider/go.mod | 4 +- provider/go.sum | 8 +- provider/pkg/gen/schema.go | 8 +- sdk/nodejs/package.json | 2 +- sdk/python/pulumi_kubernetes/_utilities.py | 2 +- sdk/python/pyproject.toml | 2 +- tests/go.mod | 5 +- tests/go.sum | 10 +- 9 files changed, 159 insertions(+), 166 deletions(-) diff --git a/provider/cmd/pulumi-resource-kubernetes/schema.json b/provider/cmd/pulumi-resource-kubernetes/schema.json index 252d8df447..fba434d885 100644 --- a/provider/cmd/pulumi-resource-kubernetes/schema.json +++ b/provider/cmd/pulumi-resource-kubernetes/schema.json @@ -324,7 +324,6 @@ "nodejs": { "compatibility": "kubernetes20", "dependencies": { - "@pulumi/pulumi": "^3.25.0", "@types/node-fetch": "^2.1.4", "@types/tmp": "^0.0.33", "glob": "^10.3.10", @@ -490,7 +489,6 @@ }, "readme": "The Kubernetes provider package offers support for all Kubernetes resources and their properties.\nResources are exposed as types from modules based on Kubernetes API groups such as 'apps', 'core',\n'rbac', and 'storage', among many others. Additionally, support for deploying Helm charts ('helm')\nand YAML files ('yaml') is available in this package. Using this package allows you to\nprogrammatically declare instances of any Kubernetes resources and any supported resource version\nusing infrastructure as code, which Pulumi then uses to drive the Kubernetes API.\n\nIf this is your first time using this package, these two resources may be helpful:\n\n* [Kubernetes Getting Started Guide](https://www.pulumi.com/docs/quickstart/kubernetes/): Get up and running quickly.\n* [Kubernetes Pulumi Setup Documentation](https://www.pulumi.com/docs/quickstart/kubernetes/configure/): How to configure Pulumi\n for use with your Kubernetes cluster.\n", "requires": { - "pulumi": ">=3.109.0,<4.0.0", "requests": ">=2.21,<3.0" }, "respectSchemaVersion": true, @@ -73631,7 +73629,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", @@ -73906,7 +73904,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", @@ -74037,7 +74035,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", @@ -74244,7 +74242,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", @@ -74519,7 +74517,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", @@ -74650,7 +74648,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", @@ -74857,7 +74855,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", @@ -75132,7 +75130,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", @@ -75263,7 +75261,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", @@ -75470,7 +75468,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", @@ -75677,7 +75675,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", @@ -75879,7 +75877,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", @@ -76205,7 +76203,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", @@ -76419,7 +76417,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", @@ -76639,7 +76637,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", @@ -76854,7 +76852,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", @@ -77066,7 +77064,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", @@ -77278,7 +77276,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", @@ -77487,7 +77485,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", @@ -77707,7 +77705,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", @@ -77927,7 +77925,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", @@ -78135,7 +78133,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", @@ -78354,7 +78352,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", @@ -78571,7 +78569,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", @@ -78785,7 +78783,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", @@ -78999,7 +78997,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", @@ -79204,7 +79202,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", @@ -79395,7 +79393,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", @@ -79592,7 +79590,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", @@ -79807,7 +79805,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", @@ -80022,7 +80020,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", @@ -80237,7 +80235,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", @@ -80449,7 +80447,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", @@ -80650,7 +80648,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", @@ -80851,7 +80849,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", @@ -81060,7 +81058,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", @@ -81265,7 +81263,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", @@ -81459,7 +81457,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", @@ -81645,7 +81643,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", @@ -81841,7 +81839,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", @@ -82029,7 +82027,7 @@ ] }, "kubernetes:coordination.k8s.io/v1alpha1:LeaseCandidatePatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nLeaseCandidate defines a candidate for a Lease object. Candidates are created such that coordinated leader election will pick the best leader from the list of candidates.", + "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than\none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource.\nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nLeaseCandidate defines a candidate for a Lease object. Candidates are created such that coordinated leader election will pick the best leader from the list of candidates.", "properties": { "apiVersion": { "type": "string", @@ -82217,7 +82215,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", @@ -82339,7 +82337,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", @@ -82554,7 +82552,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", @@ -82773,7 +82771,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", @@ -83104,7 +83102,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", @@ -83412,7 +83410,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", @@ -83600,7 +83598,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", @@ -83793,7 +83791,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", @@ -84051,7 +84049,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", @@ -84179,7 +84177,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", @@ -84372,7 +84370,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", @@ -84560,7 +84558,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", @@ -84748,7 +84746,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", @@ -84941,7 +84939,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", @@ -85175,7 +85173,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", @@ -85494,7 +85492,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", @@ -85647,7 +85645,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. There are no \"not ready\" endpoints -- unless the Service is an \"empty\n headless\" Service [1], a Service with '.spec.type: ExternalName', or a Service\n without a selector.\n4. External IP address is allocated (if Service has '.spec.type: LoadBalancer').\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. There are no \"not ready\" endpoints -- unless the Service is an \"empty\n headless\" Service [1], a Service with '.spec.type: ExternalName', or a Service\n without a selector.\n4. External IP address is allocated (if Service has '.spec.type: LoadBalancer').\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", @@ -85876,7 +85874,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", @@ -86135,7 +86133,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", @@ -86494,7 +86492,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", @@ -86941,7 +86939,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", @@ -87261,7 +87259,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", @@ -87475,7 +87473,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", @@ -87689,7 +87687,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", @@ -87891,7 +87889,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", @@ -88084,7 +88082,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", @@ -88286,7 +88284,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", @@ -88502,7 +88500,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", @@ -88723,7 +88721,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", @@ -88944,7 +88942,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", @@ -89165,7 +89163,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", @@ -89386,7 +89384,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", @@ -89607,7 +89605,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", @@ -89828,7 +89826,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", @@ -90049,7 +90047,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", @@ -90270,7 +90268,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", @@ -90491,7 +90489,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", @@ -91258,7 +91256,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", @@ -91551,7 +91549,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", @@ -91679,7 +91677,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", @@ -91885,7 +91883,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", @@ -92078,7 +92076,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", @@ -92266,7 +92264,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", @@ -92464,7 +92462,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", @@ -92662,7 +92660,7 @@ ] }, "kubernetes:networking.k8s.io/v1beta1: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", @@ -92928,7 +92926,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", @@ -93056,7 +93054,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", @@ -93262,7 +93260,7 @@ ] }, "kubernetes:networking.k8s.io/v1beta1: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", @@ -93486,7 +93484,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", @@ -93706,7 +93704,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", @@ -93928,7 +93926,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", @@ -94147,7 +94145,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", @@ -94344,7 +94342,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", @@ -94540,7 +94538,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", @@ -94839,7 +94837,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", @@ -94985,7 +94983,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", @@ -95292,7 +95290,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", @@ -95438,7 +95436,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", @@ -95746,7 +95744,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", @@ -95892,7 +95890,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", @@ -96199,7 +96197,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", @@ -96345,7 +96343,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", @@ -96653,7 +96651,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", @@ -96799,7 +96797,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", @@ -97106,7 +97104,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", @@ -97252,7 +97250,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", @@ -97457,7 +97455,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", @@ -97661,7 +97659,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", @@ -97868,7 +97866,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", @@ -98087,7 +98085,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", @@ -98306,7 +98304,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", @@ -98670,7 +98668,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", @@ -98748,7 +98746,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", @@ -98955,7 +98953,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", @@ -99345,7 +99343,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", @@ -99429,7 +99427,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", @@ -99672,7 +99670,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", @@ -99881,7 +99879,7 @@ ] }, "kubernetes:resource.k8s.io/v1alpha3:DeviceClassPatch": { - "description": "Patch resources are used to modify existing Kubernetes resources by using\nServer-Side Apply updates. The name of the resource must be specified, but all other properties are optional. More than \none patch may be applied to the same resource, and a random FieldManager name will be used for each Patch resource. \nConflicts will result in an error by default, but can be forced using the \"pulumi.com/patchForce\" annotation. See the\n[Server-Side Apply Docs](https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/) for\nadditional information about using Server-Side Apply to manage Kubernetes resources with Pulumi.\nDeviceClass is a vendor- or admin-provided resource that contains device configuration and selectors. It can be referenced in the device requests of a claim to apply these presets. Cluster scoped.\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.\nDeviceClass is a vendor- or admin-provided resource that contains device configuration and selectors. It can be referenced in the device requests of a claim to apply these presets. Cluster scoped.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.", "properties": { "apiVersion": { "type": "string", @@ -100077,7 +100075,7 @@ ] }, "kubernetes:resource.k8s.io/v1alpha3: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 DRAControlPlaneController 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 DRAControlPlaneController feature gate.", "properties": { "apiVersion": { "type": "string", @@ -100286,7 +100284,7 @@ ] }, "kubernetes:resource.k8s.io/v1alpha3: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 a request for access to resources in the cluster, for use by workloads. For example, if a workload needs an accelerator device with specific properties, this is how that request is expressed. The status stanza tracks whether this claim has been satisfied and what specific resources have been 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.\nResourceClaim describes a request for access to resources in the cluster, for use by workloads. For example, if a workload needs an accelerator device with specific properties, this is how that request is expressed. The status stanza tracks whether this claim has been satisfied and what specific resources have been allocated.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.", "properties": { "apiVersion": { "type": "string", @@ -100493,7 +100491,7 @@ ] }, "kubernetes:resource.k8s.io/v1alpha3: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.\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.\nResourceClaimTemplate is used to produce ResourceClaim objects.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.", "properties": { "apiVersion": { "type": "string", @@ -100623,7 +100621,7 @@ ] }, "kubernetes:resource.k8s.io/v1alpha3: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 represents one or more resources in a pool of similar resources, managed by a common driver. A pool may span more than one ResourceSlice, and exactly how many ResourceSlices comprise a pool is determined by the driver.\n\nAt the moment, the only supported resources are devices with attributes and capacities. Each device in a given pool, regardless of how many ResourceSlices, must have a unique name. The ResourceSlice in which a device gets published may change over time. The unique identifier for a device is the tuple , , .\n\nWhenever a driver needs to update a pool, it increments the pool.Spec.Pool.Generation number and updates all ResourceSlices with that new number and new resource definitions. A consumer must only use ResourceSlices with the highest generation number and ignore all others.\n\nWhen allocating all resources in a pool matching certain criteria or when looking for the best solution among several different alternatives, a consumer should check the number of ResourceSlices in a pool (included in each ResourceSlice) to determine whether its view of a pool is complete and if not, should wait until the driver has completed updating the pool.\n\nFor resources that are not local to a node, the node name is not set. Instead, the driver may use a node selector to specify where the devices are available.\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.\nResourceSlice represents one or more resources in a pool of similar resources, managed by a common driver. A pool may span more than one ResourceSlice, and exactly how many ResourceSlices comprise a pool is determined by the driver.\n\nAt the moment, the only supported resources are devices with attributes and capacities. Each device in a given pool, regardless of how many ResourceSlices, must have a unique name. The ResourceSlice in which a device gets published may change over time. The unique identifier for a device is the tuple , , .\n\nWhenever a driver needs to update a pool, it increments the pool.Spec.Pool.Generation number and updates all ResourceSlices with that new number and new resource definitions. A consumer must only use ResourceSlices with the highest generation number and ignore all others.\n\nWhen allocating all resources in a pool matching certain criteria or when looking for the best solution among several different alternatives, a consumer should check the number of ResourceSlices in a pool (included in each ResourceSlice) to determine whether its view of a pool is complete and if not, should wait until the driver has completed updating the pool.\n\nFor resources that are not local to a node, the node name is not set. Instead, the driver may use a node selector to specify where the devices are available.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.", "properties": { "apiVersion": { "type": "string", @@ -100852,7 +100850,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", @@ -101111,7 +101109,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", @@ -101370,7 +101368,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", @@ -101584,7 +101582,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", @@ -101771,7 +101769,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", @@ -101967,7 +101965,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", @@ -102196,7 +102194,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", @@ -102500,7 +102498,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", @@ -102776,7 +102774,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", @@ -102988,7 +102986,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", @@ -103208,7 +103206,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", @@ -103419,7 +103417,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", @@ -103616,7 +103614,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", @@ -103846,7 +103844,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", @@ -104150,7 +104148,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", @@ -104426,7 +104424,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", @@ -104646,7 +104644,7 @@ ] }, "kubernetes:storage.k8s.io/v1beta1: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", @@ -104854,7 +104852,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/go.mod b/provider/go.mod index 83724feb1c..1201beaf63 100644 --- a/provider/go.mod +++ b/provider/go.mod @@ -21,8 +21,8 @@ require ( github.com/pulumi/cloud-ready-checks v1.1.1-0.20240731201114-3a703c6bee71 github.com/pulumi/pulumi-kubernetes/sdk/v4 v4.0.0 github.com/pulumi/pulumi-kubernetes/tests/v4 v4.0.0-20240302002028-652829a1ed71 - github.com/pulumi/pulumi/pkg/v3 v3.134.1 - github.com/pulumi/pulumi/sdk/v3 v3.134.1 + github.com/pulumi/pulumi/pkg/v3 v3.135.0 + github.com/pulumi/pulumi/sdk/v3 v3.135.0 github.com/stretchr/testify v1.9.0 golang.org/x/crypto v0.26.0 golang.org/x/exp v0.0.0-20240719175910-8a7402abbf56 diff --git a/provider/go.sum b/provider/go.sum index bda71f0550..977239d7b3 100644 --- a/provider/go.sum +++ b/provider/go.sum @@ -708,10 +708,10 @@ github.com/pulumi/esc v0.10.0 h1:jzBKzkLVW0mePeanDRfqSQoCJ5yrkux0jIwAkUxpRKE= github.com/pulumi/esc v0.10.0/go.mod h1:2Bfa+FWj/xl8CKqRTWbWgDX0SOD4opdQgvYSURTGK2c= github.com/pulumi/inflector v0.1.1 h1:dvlxlWtXwOJTUUtcYDvwnl6Mpg33prhK+7mzeF+SobA= github.com/pulumi/inflector v0.1.1/go.mod h1:HUFCjcPTz96YtTuUlwG3i3EZG4WlniBvR9bd+iJxCUY= -github.com/pulumi/pulumi/pkg/v3 v3.134.1 h1:iGKvaSHEoPCGBqDoIGQUXUm3qkrawfd513lL0I9vnNQ= -github.com/pulumi/pulumi/pkg/v3 v3.134.1/go.mod h1:1iCee1QIwXYvkIQJ/HnBjsPsmYJ/arBPWX6hAao/Pro= -github.com/pulumi/pulumi/sdk/v3 v3.134.1 h1:v1zd0d+B9gpUhsdJ483YUMHwHXqDvXvZ+mh/A4HhPWg= -github.com/pulumi/pulumi/sdk/v3 v3.134.1/go.mod h1:J5kQEX8v87aeUhk6NdQXnjCo1DbiOnOiL3Sf2DuDda8= +github.com/pulumi/pulumi/pkg/v3 v3.135.0 h1:f4pBtLUf9+fa0+vVmLB4Mkdlh1KboXEt7h3pkF1seVs= +github.com/pulumi/pulumi/pkg/v3 v3.135.0/go.mod h1:6RkK4xeCtl54+PljZFwLASs6TADOE+IMofX0wj1SocY= +github.com/pulumi/pulumi/sdk/v3 v3.135.0 h1:oBP7QsmZv6uUf3eJ9j6av0nrZpipV9IguNu6rVpHlFU= +github.com/pulumi/pulumi/sdk/v3 v3.135.0/go.mod h1:J5kQEX8v87aeUhk6NdQXnjCo1DbiOnOiL3Sf2DuDda8= github.com/rivo/uniseg v0.1.0/go.mod h1:J6wj4VEh+S6ZtnVlnTBMWIodfgj8LQOQFoIToxlJtxc= github.com/rivo/uniseg v0.2.0/go.mod h1:J6wj4VEh+S6ZtnVlnTBMWIodfgj8LQOQFoIToxlJtxc= github.com/rivo/uniseg v0.4.4 h1:8TfxU8dW6PdqD27gjM8MVNuicgxIjxpm4K7x4jp8sis= diff --git a/provider/pkg/gen/schema.go b/provider/pkg/gen/schema.go index 676df8ec60..4b25488d20 100644 --- a/provider/pkg/gen/schema.go +++ b/provider/pkg/gen/schema.go @@ -540,8 +540,8 @@ func PulumiSchema(swagger map[string]any, opts ...schemaGeneratorOption) pschema } 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.` @@ -580,8 +580,8 @@ additional information about using Server-Side Apply to manage Kubernetes resour const kubernetes20 = "kubernetes20" pkgReferences := map[string]string{ - "Glob": "1.1.5", "Pulumi": "3.*", + "Glob": "1.1.5", } if gen.pulumiKubernetesDependency != "" { pkgReferences["Pulumi.Kubernetes"] = gen.pulumiKubernetesDependency @@ -617,7 +617,6 @@ additional information about using Server-Side Apply to manage Kubernetes resour }) nodeDeps := map[string]string{ - "@pulumi/pulumi": "^3.25.0", "shell-quote": "^1.6.1", "tmp": "^0.0.33", "@types/tmp": "^0.0.33", @@ -656,7 +655,6 @@ Use the navigation below to see detailed documentation for each of the supported }) requires := map[string]string{ - "pulumi": ">=3.109.0,<4.0.0", "requests": ">=2.21,<3.0", } if gen.pulumiKubernetesDependency != "" { diff --git a/sdk/nodejs/package.json b/sdk/nodejs/package.json index 32ebd608ca..67c44d4711 100644 --- a/sdk/nodejs/package.json +++ b/sdk/nodejs/package.json @@ -14,7 +14,7 @@ "build": "tsc" }, "dependencies": { - "@pulumi/pulumi": "^3.25.0", + "@pulumi/pulumi": "^3.134.1", "@types/node-fetch": "^2.1.4", "@types/tmp": "^0.0.33", "glob": "^10.3.10", diff --git a/sdk/python/pulumi_kubernetes/_utilities.py b/sdk/python/pulumi_kubernetes/_utilities.py index a77ccec075..ea7f927fed 100644 --- a/sdk/python/pulumi_kubernetes/_utilities.py +++ b/sdk/python/pulumi_kubernetes/_utilities.py @@ -264,7 +264,7 @@ def call_plain( output = pulumi.runtime.call(tok, props, res, typ) # Ingoring deps silently. They are typically non-empty, r.f() calls include r as a dependency. - result, known, secret, _ = _sync_await(asyncio.ensure_future(_await_output(output))) + result, known, secret, _ = _sync_await(asyncio.create_task(_await_output(output))) problem = None if not known: diff --git a/sdk/python/pyproject.toml b/sdk/python/pyproject.toml index 7c822f1f23..3e9ffbc5c0 100644 --- a/sdk/python/pyproject.toml +++ b/sdk/python/pyproject.toml @@ -1,7 +1,7 @@ [project] name = "pulumi_kubernetes" description = "A Pulumi package for creating and managing Kubernetes resources." - dependencies = ["parver>=0.2.1", "pulumi>=3.109.0,<4.0.0", "requests>=2.21,<3.0", "semver>=2.8.1", "typing-extensions>=4.11; python_version < \"3.11\""] + dependencies = ["parver>=0.2.1", "pulumi>=3.134.1,<4.0.0", "requests>=2.21,<3.0", "semver>=2.8.1", "typing-extensions>=4.11; python_version < \"3.11\""] keywords = ["pulumi", "kubernetes", "category/cloud", "kind/native"] readme = "README.md" requires-python = ">=3.8" diff --git a/tests/go.mod b/tests/go.mod index 3c85affe3a..09fc6529d7 100644 --- a/tests/go.mod +++ b/tests/go.mod @@ -15,8 +15,8 @@ require ( github.com/pulumi/providertest v0.0.12 github.com/pulumi/pulumi-kubernetes/provider/v4 v4.0.0 github.com/pulumi/pulumi-kubernetes/sdk/v4 v4.0.0 - github.com/pulumi/pulumi/pkg/v3 v3.134.1 - github.com/pulumi/pulumi/sdk/v3 v3.134.1 + github.com/pulumi/pulumi/pkg/v3 v3.135.0 + github.com/pulumi/pulumi/sdk/v3 v3.135.0 github.com/pulumiverse/pulumi-time/sdk v0.0.0-20231010123146-089d7304da13 github.com/stretchr/testify v1.9.0 golang.org/x/exp v0.0.0-20240719175910-8a7402abbf56 @@ -53,7 +53,6 @@ require ( github.com/ProtonMail/go-crypto v1.0.0 // indirect github.com/aead/chacha20 v0.0.0-20180709150244-8b13a72661da // indirect github.com/agext/levenshtein v1.2.3 // indirect - github.com/ahmetb/go-linq v3.0.0+incompatible // indirect github.com/antlr4-go/antlr/v4 v4.13.0 // indirect github.com/apparentlymart/go-textseg/v13 v13.0.0 // indirect github.com/asaskevich/govalidator v0.0.0-20230301143203-a9d515a09cc2 // indirect diff --git a/tests/go.sum b/tests/go.sum index f8316c0693..868510975e 100644 --- a/tests/go.sum +++ b/tests/go.sum @@ -66,8 +66,6 @@ github.com/aead/chacha20 v0.0.0-20180709150244-8b13a72661da h1:KjTM2ks9d14ZYCvmH github.com/aead/chacha20 v0.0.0-20180709150244-8b13a72661da/go.mod h1:eHEWzANqSiWQsof+nXEI9bUVUyV6F53Fp89EuCh2EAA= github.com/agext/levenshtein v1.2.3 h1:YB2fHEn0UJagG8T1rrWknE3ZQzWM06O8AMAatNn7lmo= github.com/agext/levenshtein v1.2.3/go.mod h1:JEDfjyjHDjOF/1e4FlBE/PkbqA9OfWu2ki2W0IB5558= -github.com/ahmetb/go-linq v3.0.0+incompatible h1:qQkjjOXKrKOTy83X8OpRmnKflXKQIL/mC/gMVVDMhOA= -github.com/ahmetb/go-linq v3.0.0+incompatible/go.mod h1:PFffvbdbtw+QTB0WKRP0cNht7vnCfnGlEpak/DVg5cY= github.com/alecthomas/template v0.0.0-20160405071501-a0175ee3bccc/go.mod h1:LOuyumcjzFXgccqObfd/Ljyb9UuFJ6TxHnclSeseNhc= github.com/alecthomas/units v0.0.0-20151022065526-2efee857e7cf/go.mod h1:ybxpYRFXyAe+OPACYpWeL0wqObRcbAqCMya13uyzqw0= github.com/anmitsu/go-shlex v0.0.0-20200514113438-38f4b401e2be h1:9AeTilPcZAjCFIImctFaOjnTIavg87rW78vTPkQqLI8= @@ -631,10 +629,10 @@ github.com/pulumi/esc v0.10.0 h1:jzBKzkLVW0mePeanDRfqSQoCJ5yrkux0jIwAkUxpRKE= github.com/pulumi/esc v0.10.0/go.mod h1:2Bfa+FWj/xl8CKqRTWbWgDX0SOD4opdQgvYSURTGK2c= github.com/pulumi/providertest v0.0.12 h1:UjcFQHHs4AGJyJqxhvC2q8yVQ7Li+UyCyP95HZcK03U= github.com/pulumi/providertest v0.0.12/go.mod h1:REAoaN+hGOtdWJGirfWYqcSjCejlbGfzyVTUuemJTuE= -github.com/pulumi/pulumi/pkg/v3 v3.134.1 h1:iGKvaSHEoPCGBqDoIGQUXUm3qkrawfd513lL0I9vnNQ= -github.com/pulumi/pulumi/pkg/v3 v3.134.1/go.mod h1:1iCee1QIwXYvkIQJ/HnBjsPsmYJ/arBPWX6hAao/Pro= -github.com/pulumi/pulumi/sdk/v3 v3.134.1 h1:v1zd0d+B9gpUhsdJ483YUMHwHXqDvXvZ+mh/A4HhPWg= -github.com/pulumi/pulumi/sdk/v3 v3.134.1/go.mod h1:J5kQEX8v87aeUhk6NdQXnjCo1DbiOnOiL3Sf2DuDda8= +github.com/pulumi/pulumi/pkg/v3 v3.135.0 h1:f4pBtLUf9+fa0+vVmLB4Mkdlh1KboXEt7h3pkF1seVs= +github.com/pulumi/pulumi/pkg/v3 v3.135.0/go.mod h1:6RkK4xeCtl54+PljZFwLASs6TADOE+IMofX0wj1SocY= +github.com/pulumi/pulumi/sdk/v3 v3.135.0 h1:oBP7QsmZv6uUf3eJ9j6av0nrZpipV9IguNu6rVpHlFU= +github.com/pulumi/pulumi/sdk/v3 v3.135.0/go.mod h1:J5kQEX8v87aeUhk6NdQXnjCo1DbiOnOiL3Sf2DuDda8= github.com/pulumiverse/pulumi-time/sdk v0.0.0-20231010123146-089d7304da13 h1:4U7DFIlSggj/4iLbis2Bckayed+OhaYKE7bncZwQCYI= github.com/pulumiverse/pulumi-time/sdk v0.0.0-20231010123146-089d7304da13/go.mod h1:NUa1zA74DF002WrM6iF111A6UjX9knPpXufVRvBwNyg= github.com/rivo/uniseg v0.1.0/go.mod h1:J6wj4VEh+S6ZtnVlnTBMWIodfgj8LQOQFoIToxlJtxc=