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

chore(deps): update dependency crossplane/crossplane to v1.18.2 #9147

Merged
merged 1 commit into from
Dec 18, 2024

Conversation

uniget-bot
Copy link

This PR contains the following updates:

Package Update Change
crossplane/crossplane patch 1.18.1 -> 1.18.2

Warning

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


Release Notes

crossplane/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: crossplane/crossplane@v1.18.1...v1.18.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 has been generated by Renovate Bot.

Copy link

@nicholasdille-bot nicholasdille-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approved because label type/renovate is present.

Copy link

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/crossplane:1.18.2

📦 Image Reference ghcr.io/uniget-org/tools/crossplane:1.18.2
digestsha256:7b485b335594e7ed5e5f98aafd9121f52f7fdbd2c317667fc855e27f8e789b64
vulnerabilitiescritical: 0 high: 0 medium: 1 low: 0
platformlinux/amd64
size19 MB
packages153
critical: 0 high: 0 medium: 1 low: 0 k8s.io/apiserver 0.31.2 (golang)

pkg:golang/k8s.io/[email protected]

medium 4.3: CVE--2020--8552 OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities

Affected range<1.15.10
Fixed version1.15.10, 1.16.7, 1.17.3
CVSS Score4.3
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Description

The Kubernetes API server component has been found to be vulnerable to a denial of service attack via successful API requests.

Copy link

Copy link

PR is clean and can be merged. See https://github.com/uniget-org/tools/actions/runs/12389300957.

@github-actions github-actions bot merged commit ddd5506 into main Dec 18, 2024
10 checks passed
@github-actions github-actions bot deleted the renovate/crossplane-crossplane-1.18.x branch December 18, 2024 08:40
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.

3 participants