Releases: pulumi/pulumi-kubernetes
Releases · pulumi/pulumi-kubernetes
v4.17.0
v4.16.0
Added
-
clusterIdentifier
configuration can now be used to manually control the replacement behavior of a provider resource. (#3068) -
Pod errors now include the pod's last termination state, as well as the pod's termination message if available. (#3091)
The pod's termination message can be helpful in
CrashLoopBackOff
situations but will only be reported if it was correctly configured.By default, the pod's termination message is read from
/dev/termination-log
. This location can be configured withterminationMessagePath
.Use
terminationMessagePolicy: FallbackToLogsOnError
to use the pod's logs as its termination message. -
Documentation is now generated for all languages supported by overlay types. (#3107)
Fixed
- Updated logic to accurately detect if a resource is a Patch variant. (#3102)
- Added Java as a supported language for
CustomResource
overlays. (#3120) - Status messages reported during updates are now more accurately scoped to the affected resource. (#3128)
PersistentVolumeClaims
with a bind mode ofWaitForFirstConsumer
will no longer hang indefinitely. (#3130)- [java] Fixed an issue where child resources could not be registered by Chart v4. (#3119)
v4.15.0
v4.14.0
v4.13.1
v4.12.0
Added
- Added a new Helm Chart v4 resource. (#2947)
- Added support for deletion propagation policies (e.g. Orphan). (#3011)
- Server-side apply conflict errors now include the original field manager's name. (#2983)
Changed
- Pulumi will now wait for DaemonSets to become ready. (#2953)
- The Release resource's merge behavior for
valueYamlFiles
now more closely matches Helm's behavior. (#2963)
Fixed
v4.12.0-alpha.1
Merge branch 'master' of github.com:pulumi/pulumi-kubernetes into bla…
v4.11.0
Upgrade Kubernetes schema and client libraries to v1.30 (#2932) ### Proposed changes Update Kubernetes schema and client libraries to v1.30. Go is also updated to v1.22 as an upstream library requires this. ### Related issues (optional) Closes: #2914
v4.10.0
Ensure deplyoment await logic uses the latest deployment object (#2943) ### Proposed changes This PR ensures that we compare deployment revisions based on the old live object, and the most current deployment object. This PR does the following: - Add a repro test that fails before the change is applied - Only watch for deployment events until the deployment object has been reconciled by the deployment controller - Update existing unit tests to account for blocking unbuffered channels, and faked objects that did not have `.status.observedGeneration` ### Related issues (optional) Fixes: #2941
v4.9.1
Prepare for v4.9.1 release