Skip to content

chore(deps): update local-start-crossplane-bootstrap - #119

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/local-start-crossplane-bootstrap
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/local-start-crossplane-bootstrap

Conversation

@renovate

@renovate renovate Bot commented Sep 12, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
crossplane-contrib/provider-helm minor v1.1.0v1.4.0
crossplane-contrib/provider-kubernetes minor v1.2.0v1.3.1

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

crossplane-contrib/provider-helm (crossplane-contrib/provider-helm)

v1.4.0

Compare Source

Release v1.4.0

[!IMPORTANT]
This release upgrades the embedded Helm SDK from v3 to v4 (helm.sh/helm/v4 v4.2.3). The Release API surface is unchanged, but Helm v4 changes some runtime behavior — most notably server-side apply becoming the default apply method for newly installed releases and wait now being backed by kstatus. Review the behavioral changes below before upgrading.

Summary

This release upgrades the provider to Helm SDK v4, adds a new ssaForceConflicts field to the Release API, adds Nebius authentication support, fixes a long-standing bug that caused continuous no-op release upgrades, and includes security and dependency updates.

Highlights
  • Helm SDK v4: Upgraded helm.sh/helm from v3.21.1 to v4.2.3
  • New API field: spec.forProvider.ssaForceConflicts on Release for forcing server-side apply conflict resolution
  • New authentication: NebiusServiceAccountCredentials identity type on ProviderConfig
  • Bug fix: Fixed the provider continuously upgrading a Release even when there were no changes
  • Operability: Added health/readiness probes and made metrics, health-probe, and webhook ports configurable
  • Security update: oras.land/oras-go/v2 bumped to v2.6.2 (addresses CVE-2026-50163 / GHSA-f36w-mj3v-6jqv and GHSA-fxhp-mv3v-67qp)

Helm SDK v4

The provider now embeds Helm v4 (#​333, fixes #​314 and #​214). The Release API group and version are unchanged; existing manifests keep working. Notable behavioral changes inherited from Helm v4:

  • Server-side apply by default: Newly installed releases are applied with Kubernetes server-side apply. Releases previously installed with client-side apply continue to use client-side apply, matching Helm's own upgrade behavior.
  • kstatus-based waiting: spec.forProvider.wait: true now uses Helm v4's status-watcher strategy, which waits for the kstatus readiness of all objects deployed by the chart; wait: false maps to the hook-only strategy. This mirrors the Helm CLI's mapping of the legacy --wait flag and makes release readiness an aggregation of the readiness of the deployed objects (#​214).
  • Content-based chart caching: Charts are now cached by content digest (helm/helm#31165), preventing stale-cache issues when a chart version is republished.
  • Helm diagnostics preserved: Helm v4 replaced its callback-based logging with slog; the provider bridges Helm's internal logs (including wait/kstatus diagnostics) into the provider logger, so they remain visible when running with --debug.

New Features

  • Added the spec.forProvider.ssaForceConflicts field to Release (both cluster-scoped and namespaced APIs). When set to true, the provider forces server-side apply to overwrite field conflicts ("become sole manager") when installing, upgrading, or rolling back the release. See the Kubernetes server-side apply conflicts documentation for details. (#​333)
  • Added support for Nebius authentication: ProviderConfig now accepts the NebiusServiceAccountCredentials identity type for authenticating to Nebius-managed Kubernetes clusters. See the example ProviderConfig. (#​361)

Bug Fixes

  • Fixed the provider continuously upgrading a Release even though there were no changes: release configuration is now compared semantically with numeric type normalization instead of byte-by-byte, which was sensitive to map ordering. Thanks @​doxsch! (#​327, fixes #​318)
  • Added health and readiness probes and aligned port configuration with Crossplane core: the metrics address, health-probe address, and webhook port are now configurable via --metrics-bind-address (default :8080), --health-probe-bind-addr (default :8081), and --webhook-port (default 9443). Thanks @​ctenberge-oneid! (#​285, fixes #​274)
  • Fixed the Helm client debug log dropping variadic arguments, which produced unformatted log messages during reconciliation debugging. (#​370)
  • Standardized the webhook configuration across Crossplane providers. (#​374)

Security & Dependency Updates

Full Changelog: crossplane-contrib/provider-helm@v1.3.0...v1.4.0

v1.3.0

Compare Source

Summary

This release includes important bug fixes, dependency updates, and new features.

Highlights
  • Helm SDK Update: Upgraded to Helm v3.21.0, fixing a critical regression where charts with JSON schema files referencing remote HTTPS $refs would fail with 'invalid file url' errors
  • OCI Digest Support: Added support for installing OCI charts with SHA256 digests for improved security and reproducibility
  • TakeOwnership Support: Added spec.forProvider.takeOwnership API that allows provider-helm to ignore Helm annotation checks and take ownership of existing Helm releases.
  • Drift Detection: Improved drift detection by preserving last deployed digest for OCI charts
  • Go 1.26 Support: Updated Go toolchain to 1.26.4 with corresponding golangci-lint upgrade to v2.12.2
Bug Fixes
  • Fixed JSON schema validation for charts using external Kubernetes schema references (e.g., zitadel/zitadel-charts)
  • Fixed digest pull cache filenames for OCI charts
  • Fixed late-init check for digest-based chart installations
Dependencies
  • Helm SDK: v3.18.5 → v3.21.1
  • Go: 1.24.x → 1.26.4
  • golangci-lint: v2.1.2 → v2.12.2

v1.2.0

Compare Source

Summary

This release includes new features and security fixes.

Highlights
crossplane-contrib/provider-kubernetes (crossplane-contrib/provider-kubernetes)

v1.3.1

Compare Source

What's Changed

[!IMPORTANT]
Fixes ObservedObjectCollection failing to create Objects due to incorrectly serialized deletionPropagationPolicy - #​556

Full Changelog: crossplane-contrib/provider-kubernetes@v1.3.0...v1.3.1

v1.3.0

Compare Source

v1.3.0

New Features

  • Health and readiness probes (#​301): The provider now exposes HTTP health (/healthz) and readiness (/readyz) endpoints. Probe configuration is aligned with standard Crossplane provider conventions.

  • Configurable webhook port and metrics bind address (#​301): Webhook port and metrics bind address are now configurable via flags, making it easier to deploy the provider in restricted network environments.

  • Nebius in-process service account identity auth (#​499): A new NebiusServiceAccountCredentials identity type authenticates to Nebius Managed Kubernetes clusters by minting IAM tokens in-process from a service account's credentials, without requiring an exec credential plugin. Token sources are cached per-credentials to avoid leaks across reconciles.

  • Configurable DeletionPropagationPolicy for Object (#​437): The Object spec now accepts a deletionPropagationPolicy field. Defaults to Background. Set to Foreground to ensure dependent resources are fully cleaned up before the owner is removed.

  • Remove managed fields from observed objects (#​483): Managed fields are now stripped from objects returned by the provider, reducing noise in status and stored state.

  • Strip managed fields in informer caches (#​425): The controller-runtime cache is now configured to strip managed fields from informer objects and uses PartialObjectMetadata where appropriate, reducing memory usage when watching resources.

Bug Fixes

  • Redact Secret data from debug logs (#​533): Secret values are no longer logged at debug level, preventing accidental credential exposure in log aggregators.

  • Do not block Object deletion on failed connection details (#​531): A failure to publish connection details no longer prevents an Object from being deleted, avoiding stuck finalizers.

  • Honor proxy-url from kubeconfig cluster config (#​530): The provider now correctly picks up the proxy-url field from the kubeconfig cluster entry when building the Kubernetes client.

  • Fix OpenAPI v3 ServerRelativeURL root prefix stripping (#​507): SSA apply no longer fails when the OpenAPI discovery server returns a URL with an unexpected root path prefix.

  • Fix ProviderConfig readiness for wrapped providers (#​423): An Object that creates a k8s.m ProviderConfig now correctly transitions to Ready once the inner provider config is healthy.

Dependency & Security Updates

  • Crossplane runtime bumped to v2.3.3 (#​512)
  • Security patches: google.golang.org/grpc → v1.82.1, golang.org/x/net → v0.55.0, go.opentelemetry.io/otel → v1.41.0, github.com/google/cel-go → v0.29.0
  • Go toolchain updated to v1.26.5

Contributors

Thank you to everyone who contributed to this release:

What's Changed

New Contributors

Full Changelog: crossplane-contrib/provider-kubernetes@v1.2.1...v1.3.0

v1.2.1

Compare Source

Summary

This release includes security fixes addressing multiple CVE vulnerabilities.

Highlights

Configuration

📅 Schedule: (UTC)

  • 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR was generated by Mend Renovate. View the repository job log.

@coderabbitai

coderabbitai Bot commented Sep 12, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 05e44432-6aaf-4bf9-98ed-ad6fbacb375f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants