Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update @pulumi/kubernetes to 4.18.1 #5403

Merged
merged 1 commit into from
Sep 16, 2024

Conversation

lumiere-bot[bot]
Copy link
Contributor

@lumiere-bot lumiere-bot bot commented Sep 12, 2024

This PR contains the following updates:

Package Type Update Change
@pulumi/kubernetes (source) dependencies minor 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 to
    Secrets as updates instead of replacements (similar to the
    enableConfigMapMutable option).

    The default replacement behavior can be preserved for a particular Secret
    by setting its immutable field to true.
    https://github.com/pulumi/pulumi-kubernetes/issues/22912291)

    Note: These options (enableSecretMutable and enableConfigMapMutable)
    may become the default behavior in a future v5 release of the provider.
    Programs that depend on the replacement of Secrets and ConfigMaps (e.g.
    to trigger updates for downstream dependencies like Deployments) are
    recommended 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 to
    await 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 allow
    for custom readiness checks. This override Pulumi's own await logic for the
    resource (however the pulumi.com/skipAwait annotation still takes
    precedence).

    The value of this annotation can take 3 forms:

    1. A string prefixed with jsonpath= followed by a
      JSONPath
      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":

      `pulumi.com/waitFor: "jsonpath={.status.phase}=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 configured
      with a CA bundle:

      `pulumi.com/waitFor: "jsonpath={.webhooks[*].clientConfig.caBundle}"`
      
    2. A string prefixed with condition= followed by the type of the
      condition and an optional status. This matches the behavior of
      kubectl wait --for=condition=... and will wait until the resource has a
      matching condition. The expected status defaults to "True" if not
      specified.

      `pulumi.com/waitFor: "condition=Synced"`
      
      `pulumi.com/waitFor: "condition=Reconciling=False"`
      
    3. A string containing a JSON array of multiple jsonpath= and
      condition= expressions.

      `pulumi.com/waitFor: '["jsonpath={.foo}", "condition=Bar"]'` 
      
  • 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

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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@lumiere-bot lumiere-bot bot requested a review from coolguy1771 as a code owner September 12, 2024 00:33
@lumiere-bot lumiere-bot bot added type/minor area/pulumi Changes made in the "pulumi" directory labels Sep 12, 2024
@lumiere-bot lumiere-bot bot force-pushed the renovate/kyak-pulumi-kubernetes-4.x-lockfile branch from dc2a727 to 4da466d Compare September 13, 2024 23:10
@lumiere-bot lumiere-bot bot changed the title fix(deps): update @pulumi/kubernetes to 4.18.0 fix(deps): update @pulumi/kubernetes to 4.18.1 Sep 13, 2024
@lumiere-bot lumiere-bot bot force-pushed the renovate/kyak-pulumi-kubernetes-4.x-lockfile branch from 4da466d to bdd15b1 Compare September 16, 2024 09:13
@lumiere-bot lumiere-bot bot merged commit 23cf2e7 into main Sep 16, 2024
3 checks passed
@lumiere-bot lumiere-bot bot deleted the renovate/kyak-pulumi-kubernetes-4.x-lockfile branch September 16, 2024 12:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/pulumi Changes made in the "pulumi" directory type/minor
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants