fix(deps): update @pulumi/kubernetes to 4.18.1 #5403
Merged
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.
This PR contains the following updates:
4.17.1
->4.18.1
Release Notes
pulumi/pulumi-kubernetes (@pulumi/kubernetes)
v4.18.1
Compare Source
Added
Changed
v4.18.0
Compare Source
Added
The new
enableSecretMutable
provider configuration option treats changes toSecrets
as updates instead of replacements (similar to theenableConfigMapMutable
option).The default replacement behavior can be preserved for a particular
Secret
by setting its
immutable
field totrue
.https://github.com/pulumi/pulumi-kubernetes/issues/22912291)
Note: These options (
enableSecretMutable
andenableConfigMapMutable
)may become the default behavior in a future v5 release of the provider.
Programs that depend on the replacement of
Secrets
andConfigMaps
(e.g.to trigger updates for downstream dependencies like
Deployments
) arerecommended to explicitly specify
immutable: true
.A warning is now emitted if an object has finalizers which might be blocking
deletiohttps://github.com/pulumi/pulumi-kubernetes/issues/14181418)
EXPERIMENTAL: Generic await logic is now available as an opt-in feature.
Running a program with
PULUMI_K8S_AWAIT_ALL=true
will now cause Pulumi toawait readiness for all resources, including custom resources.
Generic readiness is determined according to some well-known conventions (like
the "Ready" condition) as determined by cli-utils.
Pulumi's current behavior, without this feature enabled, is to assume some
resources are immediately available, which can cause downstream resources to
fail.
Existing readiness logic is unaffected by this setting.
https://github.com/pulumi/pulumi-kubernetes/issues/29962996)
EXPERIMENTAL: The
pulumi.com/waitFor
annotation was introduced to allowfor custom readiness checks. This override Pulumi's own await logic for the
resource (however the
pulumi.com/skipAwait
annotation still takesprecedence).
The value of this annotation can take 3 forms:
A string prefixed with
jsonpath=
followed by aJSONPath
expression and an optional value.
The JSONPath expression accepts the same syntax as
kubectl get -o jsonpath={...}
.If a value is provided, the resource is considered ready when the
JSONPath expression evaluates to the same value. For example this
resource expects its "phase" field to have a value of "Running":
If a value is not provided, the resource will be considered ready when
any value exists at the given path, similar to
kubectl wait --for jsonpath=...
. This resource will wait until it has a webhook configuredwith a CA bundle:
A string prefixed with
condition=
followed by the type of thecondition and an optional status. This matches the behavior of
kubectl wait --for=condition=...
and will wait until the resource has amatching condition. The expected status defaults to "True" if not
specified.
A string containing a JSON array of multiple
jsonpath=
andcondition=
expressions.Pulumi will now emit logs for any Kubernetes "Warning" Events associated with
resources being created, updated or deletehttps://github.com/pulumi/pulumi-kubernetes/pull/3135ull/3135/files)
Fixed
The
immutable
field is now respected forConfigMaps
when the provider is configured withenableConfigMapMutable
.https://github.com/pulumi/pulumi-kubernetes/issues/31813181)
Fixed a panic that could occur during deletion. (https://github.com/pulumi/pulumi-kubernetes/issues/3157)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.