Repository navigation
Releases
v4.34.3
4.34.3 (November 2, 2026)
Fixed
-
#4615 Fix
yaml.ConfigGroup,yaml.ConfigFile, andkustomize.Directorybeing ignored by policy packs in Node.js. -
#4672 Address eMudhra security incident by upgrading Go to 1.26.10
Added
- #4616
helm.v4.Chartnow accepts akubeVersioninput, equivalent tohelm template --kube-version, to override the Kubernetes version used forCapabilities.KubeVersion. If the value is not specified, ``Capabilities.KubeVersionwill revert to the previous behavior of taking the connected cluster's version, or Helm's default ofv1.20.0` if no cluster is reachable.
Changed
- #4642 Upgrade Kubernetes schema and libraries to v1.37.1.
v4.34.2
What's Changed
Fixed
#4603 Fix a lookup condition where one parameterization package name clobbered the other
Added
#4611 Allow hyphens in CRD generation, as supported by the Pulumi engine.
Full Changelog: v4.34.1...v4.34.2
v4.34.1
Fixed
- #4588 Fix a crash on CRD schema generation with
nullable: truefields.
v4.34.0
What's Changed
- Generate extension-parameterized SDKs from Kubernetes CRDs by @guineveresaenger in #4437
- Fix waitFor JSONPath filters using !=, >= and <= by @matanbaruch in #4524
- Alias base-provider tokens on extension-served resources by @guineveresaenger in #4559
- Upgrade to Kubernetes v1.37 by @guineveresaenger in #4570
New Contributors
- @matanbaruch made their first contribution in #4524
Full Changelog: v4.33.0...v4.34.0
v4.33.0
4.33.0 (July 7, 2026)
Added
- #3595 Add
takeOwnershiptokubernetes.helm.sh/v3:Release. When set, Helm skips the resource-conflict check and adopts existing resources into the release (equivalent tohelm upgrade/helm install --take-ownership). - #3284 Add
includeHookstokubernetes.helm.sh/v4:Chart. When set together with the provider'srenderYamlToDirectory, Helm hook resources (annotatedhelm.sh/hook) are included in the rendered output instead of being dropped, so that another tool (e.g. Argo CD) can apply them.
Changed
- Upgrade Kubernetes schema and libraries to v1.36.2.
- #4454 Document that
skipAwaitdefaults tofalseonyaml/v2.ConfigFile,yaml/v2.ConfigGroup, andkustomize/v2.Directory.
v4.32.0
Fixed
#3176 ensure Helm-installed CRDs can be resolved during preview
#4396 Fix panic when creating a kubernetes.io/service-account-token Secret with a non-existent ServiceAccount.
#4394 Don't fail YAML render when a custom resource's namespace scope can't be determined offline. The resource is rendered without a namespace and a warning is logged, rather than erroring.
Changed
Align the documented minimum supported Kubernetes version and local SDK install instructions with current provider behavior.
v4.31.1
v4.31.0
Added
- #2744 Advertise a
helmmapping forterraformconversion sopulumi import --from terraformandpulumi convert --from terraformrecognizehelm_releaseand emitkubernetes:helm.sh/v3:Release. - #4332 Implement the
Listprovider RPC and advertiselistInputs(namespace,name,labelSelector,fieldSelector) on every non-nested resource.namespaceis omitted fromlistInputson cluster-scoped kinds. Seedocs/list-rpc-semantics.mdfor 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 likespec.listenersgenerate typed args.
Changed
- Upgrade Kubernetes schema and libraries to v1.36.1.
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 astringin the schema. This fix updates the type to an array ofAny, 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
valueYamlFilesnull handling. DeprecateallowNullValues(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
#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.