Skip to content

ci: fix deployment issue with multiple clusters in same region #29427

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

Merged

Conversation

mhofstetter
Copy link
Member

@mhofstetter mhofstetter commented Nov 28, 2023

Currently, the tests ci-eks & ci-aws-cni fail due to issues deploying multiple clusters with the same name in the same region.

Therefore, this commit uses a different region for k8s version v1.24 to ensure that only one cluster gets deployed per region.

Note: This is the quick fix. As mentioned in the related issue, it might be better to ensure a unique name via other measures.

Fixes: #29004
Fixes: #29426

Currently, the tests `ci-eks` & `ci-aws-cni` fail due to issues deploying
multiple clusters with the same name in the same region.

Therefore, this commit uses a different region for k8s version v1.24 to
ensure that only one cluster gets deployed per region.

Fixes: cilium#29004

Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
@mhofstetter mhofstetter added kind/bug/CI This is a bug in the testing code. area/CI Continuous Integration testing issue or flake release-note/ci This PR makes changes to the CI. labels Nov 28, 2023
@mhofstetter mhofstetter marked this pull request as ready for review November 28, 2023 07:40
@mhofstetter mhofstetter requested review from a team as code owners November 28, 2023 07:40
@mhofstetter mhofstetter requested a review from brlbil November 28, 2023 07:40
@mhofstetter
Copy link
Member Author

/test

@brb
Copy link
Member

brb commented Nov 28, 2023

Nice find!

Note: This is the quick fix. As mentioned in the related issue, it might be better to ensure a unique name via other measures.

@mhofstetter Could you create a GH issue? 🍕

@brb brb added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Nov 28, 2023
@maintainer-s-little-helper maintainer-s-little-helper bot removed the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Nov 28, 2023
@brb
Copy link
Member

brb commented Nov 28, 2023

@mhofstetter Do we need to backport it to stable branches?

@mhofstetter
Copy link
Member Author

mhofstetter commented Nov 28, 2023

@brb

@mhofstetter Could you create a GH issue? 🍕

Already there: #29426

@mhofstetter Do we need to backport it to stable branches?

IMO this should not be necessary as long as the PR introducing the overlapping clusters in the same region #29004 doesn't get backported.

@brb
Copy link
Member

brb commented Nov 28, 2023

Already there: #29426

Your "Fixes" comment in the PR description will close it.

@brb brb added this pull request to the merge queue Nov 28, 2023
Merged via the queue into cilium:main with commit 33b2fcc Nov 28, 2023
@mhofstetter mhofstetter deleted the pr/mhofstetter/aws-eks-cluster-uniqueness branch November 28, 2023 11:27
@mhofstetter
Copy link
Member Author

Your "Fixes" comment in the PR description will close it.

Yep, I reopened it with a comment :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/CI Continuous Integration testing issue or flake kind/bug/CI This is a bug in the testing code. release-note/ci This PR makes changes to the CI.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CI: ci-awscni & ci-eks - AlreadyExistsException: Stack [eksctl-cilium-cilium-<runid>-1-cluster] already exists
4 participants