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

integ-tests: use IAMv3 API key #13

Merged

Conversation

sauterp
Copy link
Member

@sauterp sauterp commented Feb 21, 2024

Description

We use an IAMv3 key to create the test cluster and the key for the CSI secret. After each test we clean up the role and key that was created, if the CSI is torn down.

We also extend the timeout of the tests so that it has enough time to create the cluster if it does not exist yet.

To make the tests more reliable we wait for Calico and the CSI workloads to become ready and reduce the amount of requests to avoid rate limiting.

Checklist

(For exoscale contributors)

  • Changelog updated (under Unreleased block)
  • Integration tests OK

Testing

The cluster has been torn down and re-created by the CI several times during the commits in this PR.

Copy link

This pull request has been linked to Shortcut Story #88952: CSI integ tests: use v3 API key as GH secret.

@sauterp sauterp marked this pull request as ready for review February 22, 2024 17:09
@sauterp sauterp merged commit 7c33acc into main Feb 23, 2024
1 check passed
@sauterp sauterp deleted the philippsauter/sc-88952/csi-integ-tests-use-v3-api-key-as-gh-secret branch February 23, 2024 09:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants