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

Tweak CI so kops setup step only runs for AWS hubs #682

Merged
merged 2 commits into from
Sep 14, 2021

Conversation

sgibson91
Copy link
Member

@sgibson91 sgibson91 commented Sep 14, 2021

Merging #673 introduced a bug to do with curl when installing kops manually. This is breaking CI for all hubs, but should only affect hubs deployed on AWS not GCP. This PR adds in some provider information into the matrix job and updates the condition on the kops install step to only run when the provider is AWS.

@sgibson91 sgibson91 requested review from yuvipanda and damianavila and removed request for yuvipanda September 14, 2021 09:18
@sgibson91 sgibson91 self-assigned this Sep 14, 2021
@sgibson91 sgibson91 marked this pull request as ready for review September 14, 2021 09:19
@sgibson91 sgibson91 merged commit acfa3ef into 2i2c-org:master Sep 14, 2021
@damianavila
Copy link
Contributor

This is lovely @sgibson91, thanks!
Btw, we should "technically" install kops with kops-based clusters such as Farallon (and eventually Openscapes).
Carbonplan one, even when it is a AWS cluster, it is supported by EKS, so we do not need kops there.
Still, I think this PR is "conceptually" easier for others to understand, so I would be +1 on keeping it as is even when we are installing kops in the Carbonplan job when that is not actually needed 😉.

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