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
Enable EKS upgrade test #3229
Enable EKS upgrade test #3229
Conversation
@pydctw: This issue is currently awaiting triage. If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the The 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. |
/test? |
@pydctw: The
The following commands are available to trigger optional jobs:
Use
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. |
/test pull-cluster-api-provider-aws-e2e-eks |
/hold |
The upgrade test actually passed.
|
The failure is in the eks cluster test - it failed while trying to create a secret for AWSClusterStaticIdentity.
Are we supposed to set up AWSClusterStaticIdentity once and use for both upgrade and regular eks tests? I thought they should be set up per cluster but will do more investigation. |
Unknown CLA label state. Rechecking for CLA labels. Send feedback to sig-contributor-experience at kubernetes/community. /check-cla |
They should be done once in the bootstrap cluster. So we probably need to move: ginkgo.By("setting up AWS static credentials")
shared.SetupStaticCredentials(ctx, namespace, e2eCtx) To the shared test setup. So somewhere in Node1BeforeSuite when the bootstrap cluster has been created. We will also need to move the credential cleanup: ginkgo.By("Deleting AWS static credentials")
shared.CleanupStaticCredentials(ctx, namespace, e2eCtx) to the shared test teardown. So somewhere in Node1AfterSuite. |
c2ba25f
to
bb0e874
Compare
/test pull-cluster-api-provider-aws-e2e-eks |
@richardcase, thanks for the idea. I have moved SetupStaticCredentials and CleanupStaticCredentials functions to suite.go so that it can be set up once and used for both tests. Note that I refactored AWSClusterStaticIdentity functions as part of this.
|
/hold cancel |
e2e test passed and from the logs we can see the upgrade test is running. So: /lgtm |
[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 |
Looks likes a flake with envtest. Rerunning the test /retest |
/hold until above comment is addressed. |
pull-cluster-api-provider-aws-test passed but it's failing at pull-cluster-api-provider-aws-verify. Looks like the CI env is slow or sth today. Failed at verify, which has never failed for the PR before.
/retest |
Update k8s version to EKS supported versions. Set up AWSClusterStaticIdentity for the managed test suite. A few refactoring of the code. - Not to specify namespace in AWSClusterStaticIdentity as it is a cluster-scoped object. - Delete DeleteClusterSpec helper func that could be replaced with CAPI framework function.
/test pull-cluster-api-provider-aws-e2e-eks |
/test pull-cluster-api-provider-aws-verify |
Having an issue with the env today. pull-cluster-api-provider-aws-verify continues to fail. Will try again later.
|
/lgtm |
/test pull-cluster-api-provider-aws-verify |
All tests passed. /hold cancel |
What type of PR is this?
What this PR does / why we need it:
Enable EKS upgrade test, updated k8s version to EKS supported versions and setup AWSClusterStaticIdentity in a central location for use by multiple EKS tests.
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 #3228
Special notes for your reviewer:
Checklist:
Release note: