chore(deps): bump github.com/pulumi/pulumi-kubernetes/sdk/v4 from 4.28.0 to 4.31.0

[dependabot]

Bumps github.com/pulumi/pulumi-kubernetes/sdk/v4 from 4.28.0 to 4.31.0.

Release notes

Sourced from github.com/pulumi/pulumi-kubernetes/sdk/v4's releases.

v4.31.0

No release notes provided.

v4.30.0

4.30.0 (April 24, 2026)

Fixed

• #4295Fix kustomize.v2.Directory resource output type in the schema to properly support array outputs. Previously, the resources field was incorrectly typed as a string in the schema. This fix updates the type to an array of Any, aligning the schema with the provider's Go implementation (pulumi.ArrayOutput). This resolves a regression that caused the Kustomize v2 resource to fail in the Python SDK.
• #2997 Stop stripping null values when unmarshaling, fixing Helm chart default deletion and valueYamlFiles null handling. Deprecate allowNullValues (no longer needed).

Changed

• Upgrade Kubernetes schema and libraries to v1.35.4.
• Upgrade Kubernetes schema and libraries to v1.36.0.

v4.29.0

Fixed

pulumi/pulumi-kubernetes#2926 Use client-side create for new resources instead of server-side apply.

Users may observe stricter errors on some Create operations. Please read carefully.

When a resource already exists in the cluster, the API server now returns an AlreadyExists error instead of silently updating the existing object. This prevents data loss from create-then-delete scenarios (e.g. renaming a Pulumi resource or replacing an explicitly-named resource). A new provider config option upsertExistingObjects (default false) restores the previous upsert behavior for users who intentionally adopt existing cluster resources. To manage fields on existing objects without owning their lifecycle, use Patch resources (e.g. NamespacePatch).

Added

pulumi/pulumi-kubernetes#2280 Add enablePatchForce provider config option to force SSA patch conflicts on a per-stack basis.

Changed

Upgrade Kubernetes schema and libraries to v1.35.3.

Changelog

Sourced from github.com/pulumi/pulumi-kubernetes/sdk/v4's changelog.

4.31.0 (May 14, 2026)

Added

• #2744 Advertise a helm mapping for terraform conversion so pulumi import --from terraform and pulumi convert --from terraform recognize helm_release and emit kubernetes:helm.sh/v3:Release.
• #4332 Implement the List provider RPC and advertise listInputs (namespace, name, labelSelector, fieldSelector) on every non-nested resource. namespace is omitted from listInputs on cluster-scoped kinds. See https://github.com/pulumi/pulumi-kubernetes/blob/master/docs/list-rpc-semantics.md for design notes.

Fixed

• #4261 Fix CRD parameterization: implement Parameterize(Value) so subsequent runs can reconstruct the CRD schema from saved state, and flatten array-of-objects in OpenAPI specs so nested fields like spec.listeners generate typed args.

Changed

• Upgrade Kubernetes schema and libraries to v1.36.1.

4.30.0 (April 24, 2026)

Fixed

• #4295Fix kustomize.v2.Directory resource output type in the schema to properly support array outputs. Previously, the resources field was incorrectly typed as a string in the schema. This fix updates the type to an array of Any, aligning the schema with the provider's Go implementation (pulumi.ArrayOutput). This resolves a regression that caused the Kustomize v2 resource to fail in the Python SDK.
• #2997 Stop stripping null values when unmarshaling, fixing Helm chart default deletion and valueYamlFiles null handling. Deprecate allowNullValues (no longer needed).

Changed

• Upgrade Kubernetes schema and libraries to v1.35.4.
• Upgrade Kubernetes schema and libraries to v1.36.0.

4.29.0 (April 15, 2026)

Fixed

• #2926 Use client-side create for new resources instead of server-side apply.

  Users may observe stricter errors on some Create operations. Please read carefully.

  When a resource already exists in the cluster, the API server now returns an AlreadyExists error instead of silently updating the existing object. This prevents data loss from create-then-delete scenarios (e.g. renaming a Pulumi resource or replacing an explicitly-named resource). A new provider config option upsertExistingObjects (default false) restores the previous upsert behavior for users who intentionally adopt existing cluster resources. To manage fields on existing objects without owning their lifecycle, use Patch resources (e.g. NamespacePatch).

Added

• #2280 Add enablePatchForce provider config option to force SSA patch conflicts on a per-stack basis.

Changed

• Upgrade Kubernetes schema and libraries to v1.35.3.

Commits

• 066f47e Prepare for v4.31.0 release (#4347)
• de93bd5 Update first-party Pulumi dependencies (#4338)
• e288f59 Automated upgrade: bump pulumi/pulumi to 3.239.0 (#4340)
• cd5fa5a Automated upgrade: bump Kubernetes to v1.36.1 (#4341)
• db5e7cd Add design notes for List RPC (#4343)
• 6e88dd5 Update GitHub Actions workflows. (#4337)
• 47d1850 Update first-party Pulumi dependencies (#4336)
• fd6ba38 Implement List for Kubernetes resources (#4333)
• 3ebc7ca Update GitHub Actions workflows. (#4334)
• 540b41b Update first-party Pulumi dependencies (#4267)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)