Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
4.24.0 (November 5, 2025)
Added
plainHttpoption to thev4.Chartresource. (helm.Chart Insecure HTTP (--plain-http) #3250)Changed
The
pulumi.com/waitForannotation now uses anRFC9535-compliant JSONPath
parser. This makes it possible to wait for more complex scenarios.
For example:
To wait for a Pod's
status.phaseto be "Running" or "Succeeded":pulumi.com/waitFor: "jsonpath={.status[?@ == 'Running' || @ == 'Succeeded' ]}"To wait for for an object to have a "Failed" or "Complete" condition with
a "True" value:
pulumi.com/waitFor: "jsonpath={.conditions[?(@.type=='Failed'||@.type=='Complete')].status}=True(Tools like jsonpath.com are very helpful for
ensuring your JSONPath expression works as expected.)
Importantly, please note that
kubectl wait --for=jsonpath=...supports onlya subset of RFC9535. This means some complex
waitForannotations will notbe reproducible with
kubectl.Existing expressions should continue to work normally with one notable
exception: a selector like
.items[]now requires an explicit wildcard, i.e..items[*].As a reminder, the
pulumi.com/waitForannotation is experimental andsubject to change. Similarly, RFC9535 is still only proposed and may also
change in the future.
enableConfigMapMutableandenableSecretMutableare now stable.(Remove the 'BETA FEATURE' status in front of
enableConfigMapMutableandenableSecretMutableprovider properties #3886)Fixed
Helm resources all now use the correct
registry/config.jsonfile forcredentials. For backward-compatibility
registry.jsonis preferred ifit exists. (Helm OCI support uses outdated Helm Registry Config path #3606)
Fixed an issue where deletions could take longer than necessary. (Await logic for deletion is sometimes slow #3317)
Significantly reduced memory usage. (Significant increase in memory usage from v4.18.0 onwards #3713)
Fixed incorrect deprecation warnings for VolumeAttributesClass. (VolumeAttributesClass produces spurious deprecation warnings #3772)
SecretPatch inputs are now automatically marked as secret.