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

Sync upstream release 1.15 for v1.15.5 #143

Merged
merged 15 commits into from
Sep 17, 2024

Conversation

turkenh
Copy link
Member

@turkenh turkenh commented Sep 17, 2024

Description of your changes

Brings latest changes for v1.15.5

I have:

  • Read and followed Crossplane's contribution process.
  • Run earthly +reviewable to ensure this PR is ready for review.
  • Added or updated unit tests.
  • Added or updated e2e tests.
  • Linked a PR or a docs tracking issue to document this change.
  • Added backport release-x.y labels to auto-backport this PR.

Need help with this checklist? See the cheat sheet.

crossplane-renovate bot and others added 15 commits July 26, 2024 08:10
…hub.com-docker-docker-vulnerability

fix(deps): update module github.com/docker/docker to v25.0.6+incompatible [security] (release-1.15)
…hub.com-rs-cors-vulnerability

chore(deps): update module github.com/rs/cors to v1.11.0 [security] (release-1.15)
Using Update instead of CreateOrUpdate avoids a race by failing with a conflict if the underlying
Secret changed between the call to Get and the call to Update.

Signed-off-by: Jonathan Oddy <[email protected]>
(cherry picked from commit 9eca638)
Signed-off-by: Hasan Turken <[email protected]>
[Backport release-1.15] Fix race condition creating certs in init.
Signed-off-by: Lucas Käldström <[email protected]>
(cherry picked from commit 81074a1)
[Backport release-1.15] Add secrets.crossplane.io grant rules to RBAC manager roles, even though the feature is alpha.
Previously if a composed resource appeared in an XR's spec.resourceRefs
but didn't have a controller reference the XR would refuse to garbage
collect it. The XR would then remove the composed resource from its
resource refs, effectively orphaning it.

Now if the composed resource has _no_ controller, the XR will delete it.
Most likely it was owned by the XR, then had its controller ref stripped
(e.g. due to being backed up and restored using a tool like Velero).

If the composed resource is controlled by another resource, we'll now
return an error rather than silently orphaning it.

Signed-off-by: Nic Cope <[email protected]>
Delete packages in lock having same name and distinct identifier.

Signed-off-by: Jose Francisco Dillet Alfonso <[email protected]>
(cherry picked from commit 519e707)
Signed-off-by: Jose Francisco Dillet Alfonso <[email protected]>
(cherry picked from commit 991ac5f)
[release-1.15] Delete resources that don't have a controller but appear in resourceRefs
[Backport release-1.15] Fix "Missing node in tree error" after updating a package source
@turkenh turkenh merged commit ffde8ac into upbound:release-1.15 Sep 17, 2024
11 of 15 checks passed
@turkenh turkenh deleted the sync-upstream-release-1.15 branch September 17, 2024 06:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants