Skip to content

chore(deps): update dependency crossplane/crossplane to v1.20.0#332

Closed
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/crossplane-crossplane-1.x
Closed

chore(deps): update dependency crossplane/crossplane to v1.20.0#332
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/crossplane-crossplane-1.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 21, 2025 •
edited
Loading

This PR contains the following updates:

Package Update Change
crossplane/crossplane minor v1.19.1 -> v1.20.0

Release Notes

crossplane/crossplane (crossplane/crossplane)

v1.20.0

Compare Source

The v1.20.0 release is a regular quarterly Crossplane release that is focused on maturing a number of key areas of functionality across the project, as Crossplane continues to become more capable, more reliable, and more performant for your production workloads. There are lots of exciting feature investments in this release that we are excited to share with the community, as well as important notes to consider when installing or upgrading to v1.20.0.

🚨 Warnings and breaking changes

Default registry is now xpkg.crossplane.io

The default registry that Crossplane installs packages from has changed to xpkg.crossplane.io from xpkg.upbound.io. This is a neutral community registry where community extension projects in https://github.com/crossplane-contrib must publish their release artifacts to.

  • For example, when installing a package, if the spec.package field is set to:
    • crossplane-contrib/provider-aws:v0.39.0, it will now be pulled from xpkg.crossplane.io.
    • index.docker.io/crossplane-contrib/provider-aws:v0.39.0, it will be pulled from index.docker.io (because an explicit registry is specified)
  • ⚠️ To preserve the previous behavior when upgrading to v1.20.0, set --set args='{"--registry=xpkg.upbound.io"}' during the Helm upgrade. More details can be found in the Crossplane documentation.

Realtime compositions are enabled by default

The realtime compositions feature has been matured to Beta and is now enabled/on by default. This feature in the composition engine actively watches for changes so it can respond immediately to run the composition pipeline in response to any changes.

This means that Crossplane no longer reconciles XRs on a regular poll interval. The --poll-interval flag now has no effect on XRs. Instead, Crossplane watches all resources and only reconciles XRs when something changes.

  • Crossplane also reconciles an XR when a composition function response's TTL expires.
  • In the case that a provider has a bug and cannot converge on stable values for a resource, which causes frequent reconciliation attempts, then realtime compositions can worsen this situation and cause even more reconciles and cloud provider API calls. A good example of a bug like this can be seen in https://github.com/crossplane/crossplane/issues/6461.
  • ⚠️ To preserve the previous behavior when upgrading to v1.20.0, set --set args='{"--enable-realtime-composition=false"}' during the Helm upgrade.

Flag name changes

A few flags for the core Crossplane binary have been renamed in this release:

Old flag name New flag name Notes
--webhook-enabled --enable-webhooks The old --webhook-enabled flag has been deprecated, but still functions in this release. If it is used, you will see a warning about its deprecation and removal in a future release.
--cache-dir --xpkg-cache-dir The old --cache-dir flag has been deprecated, but still functions in this release. If it is used, you will see a warning about its deprecation and removal in a future release.
--automatic-dependency-downgrade-enabled --enable-dependency-version-downgrades As this is an alpha feature, the old flag name has been removed entirely.

🎉 Highlights

  • Realtime compositions: Crossplane will compose resources faster than ever before now with realtime compositions matured to Beta and enabled by default. Crossplane automatically sets up watches so it will be aware of any relevant changes and execute the composition pipeline immediately in response. No more waiting minute(s) for changes related to your compositions to be reflected in your control plane!
  • Mirror packages to private repositories: Mirroring Crossplane packages to your private repos is now much easier than in previous releases. The ImageConfig API now allows package paths to be rewritten via prefix replacement. This allows packages and their dependencies to be mirrored to a different registry but installed using their original paths.
  • Change logs in providers: The change logs feature has been rolled out to some community providers, for example provider-kubernetes and provider-helm. This allows the providers to log every change they are making and the reason for doing so. Take a look at the change logs guide in the Crossplane docs to learn more.
  • Function response caching: A new Alpha feature, enabled with --enable-function-response-cache, allows the caching of responses in the function pipeline to the Crossplane pod filesystem. Using cached responses can reduce the amount of requests Crossplane sends to functions.
  • Crossplane CLI shell completions: Shell completions are now included for the crossplane CLI, enabling you to autocomplete crossplane commands with arguments and values. Try out crossplane beta trace and instead of typing or pasting the resource name, just let <tab> auto complete find it for you! Learn how to get started with shell completions in the CLI reference.

🏅 Release MVP

For the first time ever in Crossplane release history, we are recognizing two community members for their awesome contributions to the v1.20.0 release and naming them both release MVPs! Congratulations and thank you to our release MVPs @​chlunde and @​twobiers! 🎉

  • @​chlunde was a significant help during testing and validation of the v1.20.0 RC build. Carl took the time to install the RC on his lab test cluster (possibly one of the oldest known living Crossplane control planes 👴) and reported all of the potential issues along with helpful descriptions and reproduction steps. This type of participation by the community to validate the release candidates is so incredibly helpful to make each release high quality. Thank you @​chlunde!
  • @​twobiers took the initiative to contribute an awesome feature to the Crossplane CLI with shell completions, as noted in the release highlights section above. We're especially grateful that @​twobiers had the patience to work with the maintainer team through a long review cycle. The wait was worth it, as we are already loving the ease of use that comes when typing crossplane <tab> and having commands, resources, etc. auto completed for you. What a great feature to improve Crossplane user quality of life. Thank you @​twobiers!

What's Changed

New Contributors

Full Changelog: crossplane/crossplane@v1.19.0...v1.20.0

v1.19.2

Compare Source

What's Changed

Full Changelog: crossplane/crossplane@v1.19.1...v1.19.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 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 was generated by Mend Renovate. View the repository job log.

@renovate
chore(deps): update dependency crossplane/crossplane to v1.20.0
e8db098 
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate Bot added kind/renovate Categorizes issue or PR as related to Renovate lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/medium This issue or PR may be useful, and needs some attention size/xs Size XS status/review_needed The issue or PR needs to be reviewed labels May 21, 2025
@renovate renovate Bot added kind/renovate Categorizes issue or PR as related to Renovate priority/medium This issue or PR may be useful, and needs some attention lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. labels May 21, 2025
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 21, 2025

Important

Review skipped

Bot user detected.

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

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@stale
Copy link
Copy Markdown

stale Bot commented Jul 20, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 20, 2025
@stale stale Bot closed this Jul 27, 2025
@renovate renovate Bot deleted the renovate/crossplane-crossplane-1.x branch July 27, 2025 17:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@nlamirault nlamirault

Labels

kind/renovate Categorizes issue or PR as related to Renovate lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/medium This issue or PR may be useful, and needs some attention size/xs Size XS status/review_needed The issue or PR needs to be reviewed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@nlamirault