-
Notifications
You must be signed in to change notification settings - Fork 570
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
🌱 Bump CAPI to v1.8.4 #5061
🌱 Bump CAPI to v1.8.4 #5061
Conversation
Skipping CI for Draft Pull Request. |
/cc @nrb |
/test pull-cluster-api-provider-aws-e2e |
/hold |
Looks like we'll need to bump tests to use Go 1.22. |
/retest |
Per CAPI community meeting discussion, we should stop setting the |
@damdo: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Signed-off-by: Nolan Brubaker <[email protected]>
Signed-off-by: Nolan Brubaker <[email protected]>
Signed-off-by: Nolan Brubaker <[email protected]>
Signed-off-by: Nolan Brubaker <[email protected]>
We carry a very small patch for the conversion-gen tool so that we can support having types of the same name in both the standard and experimental APIs. During the v1.30 timeframe, the Kubernetes code generation tools were refactored to more modern Go module standards, while also cleaning up the code. This commit carries the v1.30 (specifically, commit 304c1999892b41b6a3ff5dae260253f39cf53660) changes for the main.go and conversion.go files, alongside our patch. This commit also includes the updated conversion code output by our vendored/forked conversion_gen tool. Signed-off-by: Nolan Brubaker <[email protected]>
The e2e tests are not passing on this. This is probably due to the AMI changes. Let's merge and follow-up on the e2e tests. We have #5161 created and added to the v2.7.0 milestone as a "release blocker". Based on this: /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: richardcase The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* capi v1.8.0-beta.0 * use source.Kind generics * update e2e testing versions * set terminationMessagePolicy to FallbackToLogsOnError for manager * bump go version to 1.22 * Update metrics options for new types Signed-off-by: Nolan Brubaker <[email protected]> * Update to CAPI 1.8.3 Signed-off-by: Nolan Brubaker <[email protected]> * Fix test linting Signed-off-by: Nolan Brubaker <[email protected]> * Use latest versions of setup-envtest Signed-off-by: Nolan Brubaker <[email protected]> * Update generation tools for Kube 1.30 We carry a very small patch for the conversion-gen tool so that we can support having types of the same name in both the standard and experimental APIs. During the v1.30 timeframe, the Kubernetes code generation tools were refactored to more modern Go module standards, while also cleaning up the code. This commit carries the v1.30 (specifically, commit 304c1999892b41b6a3ff5dae260253f39cf53660) changes for the main.go and conversion.go files, alongside our patch. This commit also includes the updated conversion code output by our vendored/forked conversion_gen tool. Signed-off-by: Nolan Brubaker <[email protected]> * Update to CAPI 1.8.4 --------- Signed-off-by: Nolan Brubaker <[email protected]> Co-authored-by: Nolan Brubaker <[email protected]>
@nrb: I'm not sure why, but See for instance https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/config/crd/patches/webhook_in_awsclustercontrolleridentities.yaml#L15 |
What type of PR is this?
/kind support
What this PR does / why we need it:
CAPI v1.8.0-beta.0 is out now, so this PRs bumps the CAPI version used by CAPA with the new released one.
Bumps CAPI to v1.8.x based on https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/book/src/developer/providers/migrations/v1.7-to-v1.8.md
Special notes for your reviewer:
TODO:
[ ] The support for INIT env variables was dropped in the clusterctl upgrade tests. If you were using INIT_WITH_BINARY, INIT_WITH_PROVIDERS_CONTRACT or INIT_WITH_KUBERNETES_VERSION consider using the corresponding fields in ClusterctlUpgradeSpecInput. If you prefer to use environment variables, read them e.g. via os.Getenv and then set the spec fields accordingly.we do this already![ ] remote.NewClusterCacheTracker now has options to configure QPS & Burst. It's highly recommended to implement corresponding flags the same way as core Cluster API (see PR: ✨ Add QPS & burst options & flags for ClusterCacheTracker cluster-api#10880)we don't use this.Release note: