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

Bump Kubernetes to v1.24.0 and fix AWSMachinePool minsize #3468

Merged
merged 4 commits into from
Jul 29, 2022

Conversation

sedefsavas
Copy link
Contributor

@sedefsavas sedefsavas commented May 12, 2022

What this PR does / why we need it:
Bumping cluster-api version to v1.1.5 and Kubernetes version we use in e2e tests to v1.24.0.

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 #3242
Fixes #3600

Special notes for your reviewer:

Checklist:

  • squashed commits
  • includes documentation
  • adds unit tests
  • adds or updates e2e tests

@k8s-ci-robot k8s-ci-robot added needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 12, 2022
@k8s-ci-robot
Copy link
Contributor

@sedefsavas: This issue is currently awaiting triage.

If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels May 12, 2022
go.mod Outdated
golang.org/x/text v0.3.7
gopkg.in/yaml.v2 v2.4.0
k8s.io/api v0.23.5
k8s.io/api v0.24.0
Copy link
Member

@sbueringer sbueringer May 12, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think those k8s.io/* versions all have to stay the same (or at least stay on v0.23.x)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! finally reverted those properly.

@sedefsavas sedefsavas force-pushed the 1.24 branch 5 times, most recently from c75e375 to 32f46ea Compare May 13, 2022 09:18
@sedefsavas
Copy link
Contributor Author

/test ?

@k8s-ci-robot
Copy link
Contributor

@sedefsavas: The following commands are available to trigger required jobs:

  • /test pull-cluster-api-provider-aws-build
  • /test pull-cluster-api-provider-aws-test
  • /test pull-cluster-api-provider-aws-verify

The following commands are available to trigger optional jobs:

  • /test pull-cluster-api-provider-aws-apidiff-main
  • /test pull-cluster-api-provider-aws-e2e
  • /test pull-cluster-api-provider-aws-e2e-blocking
  • /test pull-cluster-api-provider-aws-e2e-conformance
  • /test pull-cluster-api-provider-aws-e2e-conformance-with-ci-artifacts
  • /test pull-cluster-api-provider-aws-e2e-eks

Use /test all to run the following jobs that were automatically triggered:

  • pull-cluster-api-provider-aws-apidiff-main
  • pull-cluster-api-provider-aws-build
  • pull-cluster-api-provider-aws-test
  • pull-cluster-api-provider-aws-verify

In response to this:

/test ?

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.

@sedefsavas
Copy link
Contributor Author

/test pull-cluster-api-provider-aws-e2e

@sedefsavas
Copy link
Contributor Author

/test pull-cluster-api-provider-aws-e2e-blocking

KUBERNETES_VERSION: "v1.23.3"
KUBERNETES_VERSION_UPGRADE_TO: "v1.23.3"
KUBERNETES_VERSION_UPGRADE_FROM: "v1.22.4"
KUBERNETES_VERSION_MANAGEMENT: "v1.24.0"
Copy link
Member

@sbueringer sbueringer May 13, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we have to keep this version on v1.23.3 for now.

The problem is that only kind v0.13 is compatible with kindest/node:v1.24.0+ and we didn't bump the kind version yet.

I think this should be okay for now given that we mostly want to verify that CAPI is able to manage v1.24 clusters vs kind being able to create v1.24 bootstrap clusters.

xref: the CI failure during kind create cluster: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api-provider-aws/3468/pull-cluster-api-provider-aws-e2e/1525045134981337088

(cc @fabriziopandini)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK, done.

Copy link
Member

@sbueringer sbueringer Jun 7, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the latest v1.1.x release we should now be able to use v1.24 as mgmt cluster. with kind

@sedefsavas
Copy link
Contributor Author

/test pull-cluster-api-provider-aws-e2e-blocking

@sedefsavas
Copy link
Contributor Author

/test pull-cluster-api-provider-aws-e2e

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 6, 2022
@Ankitasw
Copy link
Member

@sedefsavas any leads on this PR?

@k8s-ci-robot k8s-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jun 27, 2022
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 27, 2022
@k8s-ci-robot k8s-ci-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed do-not-merge/contains-merge-commits labels Jul 27, 2022
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 27, 2022
@sedefsavas
Copy link
Contributor Author

/test pull-cluster-api-provider-aws-e2e
/test pull-cluster-api-provider-aws-e2e-eks
/test pull-cluster-api-provider-aws-e2e-conformance
/test pull-cluster-api-provider-aws-e2e-conformance-with-ci-artifacts

@sedefsavas
Copy link
Contributor Author

Reason of the machinepool failure was e2e-config was using an old nightly image as the latest of 1.1.x capi version.
After all the e2e tests pass, this is good to go.

@mweibel
Copy link
Contributor

mweibel commented Jul 28, 2022

ah that makes sense! I did wonder whether this needs updating but wasn't sure.
Also explains why it worked locally - I had CAPI running locally of course.

Thanks for fixing!

@sedefsavas
Copy link
Contributor Author

/test pull-cluster-api-provider-aws-e2e

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Jul 28, 2022

@sedefsavas: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-cluster-api-provider-aws-e2e-blocking 2d885d5b23d3323e8079cd146b16ae0017041a7c link false /test pull-cluster-api-provider-aws-e2e-blocking

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/test-infra repository. I understand the commands that are listed here.

@sedefsavas
Copy link
Contributor Author

/test pull-cluster-api-provider-aws-e2e

@sedefsavas
Copy link
Contributor Author

/assign @richardcase

EKS tests passed in the previous run.

@sedefsavas
Copy link
Contributor Author

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 28, 2022
@richardcase
Copy link
Member

This all looks ok to me

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 29, 2022
@sedefsavas
Copy link
Contributor Author

/approve

Ups there is a pull-cluster-api-provider-aws-build-release-1-5 job running, there must be a bug in the release-1.5 jobs.

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sedefsavas

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 29, 2022
@k8s-ci-robot k8s-ci-robot merged commit d6dcb17 into kubernetes-sigs:main Jul 29, 2022
@k8s-ci-robot k8s-ci-robot added this to the v1.x milestone Jul 29, 2022
@k8s-infra-cherrypick-robot

@sedefsavas: #3468 failed to apply on top of branch "release-1.5":

Applying: Bump CAPI to v1.1.5 and e2e test Kubernetes versions to v1.24.0
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
M	pkg/cloud/scope/machine_test.go
M	test/e2e/data/e2e_eks_conf.yaml
Falling back to patching base and 3-way merge...
Auto-merging test/e2e/data/e2e_eks_conf.yaml
Auto-merging pkg/cloud/scope/machine_test.go
Auto-merging go.sum
CONFLICT (content): Merge conflict in go.sum
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Bump CAPI to v1.1.5 and e2e test Kubernetes versions to v1.24.0
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.5

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Drop v1alpha3 to v1beta1 upgrade tests AWSMachinePool minSize should be allowed to go to 0
7 participants