-
Notifications
You must be signed in to change notification settings - Fork 273
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[release-0.19] Backporting dependency bumps to fix vulnerabilities (#…
…8118) * Bump controller-runtime to v0.16.5 (#7788) `controller-runtime` v0.16.5 - Fake client breaking changes: - Start using `WithStatusSubresource` when we care about status being treated differently through `Update` calls. This is basically all controllers. - Add a finalizer when creating an object directly with a deletion timestamp. This make sense since any controller interested in the delete flow should be already adding finalizers. - Signature of `Watches` for creating a controller has been simplified and doesn't need the `source.Kind` wrapper. - Manager options signature has changed. Now metrics and webhook fields are nested in its own second level struct. - Validation webhooks now return a `(admission.Warnings, error)` instead of just `error`. We are not using this functionality for now, but we had to update all our webhooks and test to follow the new signature. - `handler.MapFunc` has changed, now they take a context as well. We don't use the context but need to conform to the new signature. `cluster-api` v1.6.2 - When setting up cluster tracker, the variable `DefaultIndexes` is removed, now we use `[]Index{NodeProviderIDIndex}` CAPC We are still waiting for capc to be updated to capi v1.5, which would enable us to move to controller-runtime v0.15. It's taking quite long and we got to the point where this is preventing us from updating moduled (like helm) that we need to update ASAP. I opted for "vendoring" just the api structs we need from capc. In order to contain changes and allow for an easy "revert" to use the original module (whenever we can), I created a dummy module so I can just use a `replace` in our go.mod and point to our vendored folder. I put this in `internal/thirdparty/capc`. You don't need to review that code, I just copied it. Assertions in gomock I had to change some of the assertions in the cluster manager tests. Now they are less strict since they use type instead of content assertion. TBH, they were wrong from the beginning since they expected current and new spec to be the same, so if so, this makes the test slightly better. I checked and I believe all this is already dead code because of the workflow refactors we did in v0.19.0. It's just that the code hasn't been deleted yet. I'll push to get all this crap removed. CAPV They just change the package where they have the api structs from `api/[version]` to `apis/[version]`. * Bump helm to v3.14.2 (#7797) bump helm and controller runtime * Bump x/net (#7945) bump net/x to fix vulnerability * go mod tidy * Bump Go version to 1.21 (#7805) * Bump helm froo 3.14.2 to 3.14.4 (#8119) * go mod tidy * fix linting errors --------- Co-authored-by: Guillermo Gaston <gaslor@amazon.com> Co-authored-by: Xu Deng <xudeng@amazon.com> Co-authored-by: Abhay Krishna <arnchlm@amazon.com>
- Loading branch information
1 parent
dca4806
commit f34868b
Showing
101 changed files
with
5,893 additions
and
3,093 deletions.
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.