-
Notifications
You must be signed in to change notification settings - Fork 537
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.5.0 #4510
Bump CAPI to v1.5.0 #4510
Conversation
/test pull-cluster-api-provider-aws-e2e |
485a62d
to
6a92789
Compare
@@ -113,7 +112,6 @@ var ( | |||
) | |||
|
|||
func main() { | |||
rand.NewSource(time.Now().UnixNano()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this changing? I never noticed this line before, what was this used for?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, I myself have not noticed this. I dont think this line has any affect, that's why it was removed by @furkatgofurov7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep. The only place we are using Random is in subnets.go to shuffle the AZs. But rand.Shuffel
is already using a default seed. So it will provide pseudo random results every time its running. Removing this should be safe.
@@ -2,7 +2,7 @@ module sigs.k8s.io/cluster-api-provider-aws/v2 | |||
|
|||
go 1.20 | |||
|
|||
replace sigs.k8s.io/cluster-api => sigs.k8s.io/cluster-api v1.4.4 | |||
replace sigs.k8s.io/cluster-api => sigs.k8s.io/cluster-api v1.5.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm confused by this - what's the effect of replacing a package with the same thing that's required?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will pick the exact version of cluster api specified, otherwise it picks up the dirty version of whatever latest CAPI main branch has.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @richardcase to correct me if I am wrong.
416e708
to
1913959
Compare
/test pull-cluster-api-provider-aws-e2e-eks |
All tests are passing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
with minor comments
- pkg: k8s.io/apimachinery/pkg/api/errors | ||
alias: apierrors |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still used for imports, so why not lint it anymore?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was a duplicate import in the file, so removed, otherwise we will get below error
ERRO [linters_context] invalid configuration, multiple aliases for the same package: pkg=k8s.io/apimachinery/pkg/api/errors aliases=[apierrors,apierrors]
ERRO [linters_context] invalid configuration, multiple packages with the same alias: alias=apierrors packages=[k8s.io/apimachinery/pkg/api/errors,k8s.io/apimachinery/pkg/api/errors]
@@ -248,7 +248,7 @@ func TestGetAPIServerClassicELBSpecControlPlaneLoadBalancer(t *testing.T) { | |||
expect: func(t *testing.T, g *WithT, res *infrav1.LoadBalancer) { | |||
t.Helper() | |||
expectedTarget := fmt.Sprintf("%v:%d", infrav1.ELBProtocolTCP, infrav1.DefaultAPIServerPort) | |||
g.Expect(expectedTarget, res.HealthCheck.Target) | |||
g.Expect(expectedTarget).NotTo(Equal(res.HealthCheck.Target)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why it this now negated? Is the default target different?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great find, thanks @AndiDog yes the default target is changed when we were moving to v1beta2 APIs. This change reside in code base for long, not sure how unit tests didn't catch it. Thanks a lot for this finding.
cc @richardcase
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Skarlso 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 |
859c7ad
to
0173b10
Compare
Have added only the unit test change, so not re-running the E2E tests again. |
Oh dang, and that resulted in an API drift? Can we punt that? |
Uhmm this is weird, I just changed the unit tests, maybe some changes came with rebase thats causing the issue. |
Signed-off-by: Furkat Gofurov <furkat.gofurov@suse.com>
Signed-off-by: Furkat Gofurov <furkat.gofurov@suse.com>
The tests where failing after upgrading controller-runtime due to changes in the fake client. Signed-off-by: Richard Case <richard.case@outlook.com>
Signed-off-by: Furkat Gofurov <furkat.gofurov@suse.com>
Signed-off-by: Furkat Gofurov <furkat.gofurov@suse.com>
0173b10
to
43b06c8
Compare
@Skarlso its fine now. |
/lgtm |
/cherry-pick release-2.2 |
@Ankitasw: #4510 failed to apply on top of branch "release-2.2":
In response to this:
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/test-infra repository. |
What type of PR is this?
/kind support
What this PR does / why we need it:
Bumps CAPI to v1.5.0 based on https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/book/src/developer/providers/migrations/v1.4-to-v1.5.md
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #4375
Fixes #4390
Special notes for your reviewer:
Checklist:
Release note: