Update Helm release crossplane to v1.18.2 (main)

Sylva Renovate botrequested to merge
renovate/main-crossplane-1.x into main

This MR contains the following updates:

Package Update Change
crossplane (source) minor 1.17.1 -> 1.18.2

Release Notes

crossplane/crossplane (crossplane)

v1.18.2

Compare Source

This is a patch release scoped to fixing issues reported by users of Crossplane v1.17 and fixing security related issues in Crossplane's dependencies.

Users of v1.18.x reported that they were no longer able to downgrade a Crossplane installation from v1.18.x to a previous v1.17.x version. This was fixed in https://github.com/crossplane/crossplane/pull/6157 and we expect downgrades from v1.18.2 to be working once again.

The way Usage objects are managed within a Composition has been updated in https://github.com/crossplane/crossplane/pull/6155 to prevent orphaned Usage objects from remaining in the control plane when a Composition that creates a Usage is updated. The change is described below:

  • When the Usage itself deleted, the usage controller will wait for using resource before removing the finalizer, only if the Usage is part of a composite (i.e has crossplane.io/composite label).
  • When a resource removed from a composition (i.e. decomposed), the composition controllers (both PT and function) will remove the composed resource labels before deleting the resource.
  • This behavior is visually summarized in https://github.com/crossplane/crossplane/issues/5880#issuecomment-2363433313

What's Changed

Full Changelog: https://github.com/crossplane/crossplane/compare/v1.18.1...v1.18.2

v1.18.1

Compare Source

What's Changed

Full Changelog: https://github.com/crossplane/crossplane/compare/v1.18.0...v1.18.1

v1.18.0

Compare Source

🚨 Breaking Changes

  • While the EnvironmentConfig API was matured to Beta in this release, it's important to note that native support for EnvironmentConfig within a Composition was removed in https://github.com/crossplane/crossplane/pull/5938.
    • Users that enabled Alpha Composition Environments (--enable-environment-configs) and leveraged the native functionality (spec.environment.patches, spec.environment.environmentConfigs and *Environment patches), will have to migrate to Composition Functions to continue doing so.
    • We have built automated migration tooling to help with this migration/transition.
    • Further information, including migration instructions, can be found in the Crossplane docs.

❗ Notable Changes

A forthcoming change to Crossplane's default xpkg.upbound.io package registry may require you to authenticate to pull packages. In this release we've introduced a new ImageConfig API that makes it easier to configure registry credentials.

In order to minimize disruption to the community, we're making an exception to Crossplane's feature maturity process. We've introduced the new ImageConfig API as a beta feature that is enabled by default. We've also back ported the new ImageConfig API to the latest v1.16 and v1.17 patch releases.

🎉 Highlights

Release MVP

We'd like to thank @​cychiang for their multiple contributions within this release. Of particular note, they implemented #​5976 which enabled passing credentials to functions from the render command. We are also looking forward to including their contribution from #​5963 in the next milestone. Thanks @​cychiang!! 🙇‍♂️

📖 Full Changelog

New Contributors

Full Changelog: https://github.com/crossplane/crossplane/compare/v1.17.0...v1.18.0

v1.17.4

Compare Source

This is a patch release scoped to fixing security related issues in Crossplane's dependencies, as well as improving E2E test reliability.

What's Changed

Full Changelog: https://github.com/crossplane/crossplane/compare/v1.17.3...v1.17.4

v1.17.3

Compare Source

Notable Changes

A forthcoming change to Crossplane's default http://xpkg.upbound.io/ package registry may require you to authenticate to pull packages. In this release we've introduced a new ImageConfig API that makes it easier to configure registry credentials.

In order to minimize disruption to the community, we're making an exception to Crossplane's feature maturity process. We introduced the new ImageConfig API in Crossplane v1.18 as a beta feature that is enabled by default. We've also back ported the new ImageConfig API to this patch release, to make it available without needing to upgrade to v1.18.

What's Changed

Full Changelog: https://github.com/crossplane/crossplane/compare/v1.17.2...v1.17.3

v1.17.2

Compare Source

This is a patch release scoped to fixing issues reported by users of Crossplane v1.17. First, this patch release addresses the below published security advisory that affects the versions of golang that Crossplane depends on.

Thank you @​aditya-mayo for reporting this vulnerability! 🙇‍♂️

This release also addresses an issue (https://github.com/crossplane/crossplane/issues/5971) where users of v1.17 were not able to build or install Functions using v1 package metadata. Now that Functions have matured to v1, this will become much more pervasive throughout the Crossplane Functions ecosystem.

What's Changed

Full Changelog: https://github.com/crossplane/crossplane/compare/v1.17.1...v1.17.2

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 MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

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

This MR has been generated by Renovate Bot Sylva instance.

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon Meaning Available values
☁️ Infra Provider capd, capo, capm3
🚀 Bootstrap Provider kubeadm (alias kadm), rke2
🐧 Node OS ubuntu, suse
🛠️ Deployment Options light-deploy, oci, ha, misc
🎬 Pipeline Scenarios rolling-update, mgmt-rolling-update, k8s-upgrade, sylva-upgrade-from-x.x.x, simple-update, preview, nightly

  • 🎬 preview ☁️ capd 🚀 kadm 🐧 ubuntu 🛠️ oci

  • 🎬 preview ☁️ capo 🚀 rke2 🐧 suse

  • 🎬 preview ☁️ capm3 🚀 rke2 🐧 ubuntu

  • ☁️ capd 🚀 kadm 🛠️ light-deploy 🐧 ubuntu

  • ☁️ capd 🚀 rke2 🛠️ oci,light-deploy 🐧 suse

  • ☁️ capo 🚀 rke2 🛠️ oci 🐧 suse

  • ☁️ capo 🚀 kadm 🛠️ oci 🐧 ubuntu

  • ☁️ capo 🚀 rke2 🎬 rolling-update 🛠️ ha 🐧 ubuntu

  • ☁️ capo 🚀 kadm 🎬 k8s-upgrade 🐧 ubuntu

  • ☁️ capo 🚀 rke2 🎬 mgmt-rolling-update 🛠️ ha,misc 🐧 suse

  • ☁️ capo 🚀 rke2 🎬 sylva-upgrade-from-1.3.x 🛠️ ha,misc 🐧 ubuntu

  • ☁️ capm3 🚀 rke2 🐧 suse

  • ☁️ capm3 🚀 kadm 🛠️ oci 🐧 ubuntu

  • ☁️ capm3 🚀 kadm 🎬 mgmt-rolling-update 🛠️ ha,misc 🐧 ubuntu

  • ☁️ capm3 🚀 rke2 🎬 k8s-upgrade 🛠️ ha 🐧 suse

  • ☁️ capm3 🚀 kadm 🎬 rolling-update 🛠️ ha 🐧 ubuntu

  • ☁️ capm3 🚀 rke2 🎬 sylva-upgrade-from-1.3.x 🛠️ misc,ha 🐧 suse

  • ☁️ capm3 🚀 kadm 🎬 rolling-update 🛠️ ha 🐧 suse

Global config for deployment pipelines

  • autorun pipelines
  • allow failure on pipelines

Notes:

  • Enabling autorun will make deployment pipelines to be run automatically without human interaction
  • Disabling allow failure will make deployment pipelines mandatory for pipeline success.
  • if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.

⚙️ If no checkbox is checked, a default pipeline will be enabled (capm3, or capo if capo label is set)

Merge request reports