-
Notifications
You must be signed in to change notification settings - Fork 15
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.16 for v1.16.2 #142
Merged
turkenh
merged 15 commits into
upbound:release-1.16
from
turkenh:sync-upstream-release-1.16
Sep 17, 2024
Merged
Sync upstream release 1.16 for v1.16.2 #142
turkenh
merged 15 commits into
upbound:release-1.16
from
turkenh:sync-upstream-release-1.16
Sep 17, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Philippe Scorsolini <[email protected]> (cherry picked from commit 685ed5a)
[Backport release-1.16] fix(trace): set default qps and burst back
…hub.com-docker-docker-vulnerability fix(deps): update module github.com/docker/docker to v25.0.6+incompatible [security] (release-1.16)
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.16] Fix race condition creating certs in init.
Signed-off-by: Lucas Käldström <[email protected]> (cherry picked from commit 81074a1)
[Backport release-1.16] 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)
[Backport release-1.16] Fix "Missing node in tree error" after updating a package source
[release-1.16] Delete resources that don't have a controller but appear in resourceRefs
Release v1.16.2
jeanduplessis
approved these changes
Sep 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of your changes
Brings latest changes for v1.16.2
I have:
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.Addedbackport release-x.y
labels to auto-backport this PR.Need help with this checklist? See the cheat sheet.