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

linc: add cluster, and deploy support chart and staging hub #3854

Merged
merged 1 commit into from
Mar 27, 2024

Conversation

consideRatio
Copy link
Contributor

@consideRatio consideRatio commented Mar 26, 2024

Resolves part 1 and 2 of #3828, and parts of part 3 which was about deploying a staging hub. Details about that hub isn't locked in place yet, so I did parts.

Unrelated test failure

Note that the test failure is unrelated, which stems from me removing autoformat removed whitespace in a file inside config/clusters/templates. I tried to patch a job to not trigger incorrectly on those files but failed. Opened #3855 related to this.

@consideRatio consideRatio requested a review from a team as a code owner March 26, 2024 20:39
Copy link

github-actions bot commented Mar 26, 2024

Merging this PR will trigger the following deployment actions.

Support and Staging deployments

Cloud Provider Cluster Name Upgrade Support? Reason for Support Redeploy Upgrade Staging? Reason for Staging Redeploy
aws linc Yes Following helm chart values files were modified: support.values.yaml, enc-support.secret.values.yaml Yes Following helm chart values files were modified: enc-staging.secret.values.yaml, common.values.yaml, staging.values.yaml

Production deployments

No production hub upgrades will be triggered

Comment on lines +183 to +185
failure_2i2c-aws-us: "${{ env.failure_2i2c-aws-us }}"
failure_2i2c-uk: "${{ env.failure_2i2c-uk }}"
failure_2i2c: "${{ env.failure_2i2c }}"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I sorted these alphabetically, makes it less likeley that we get merge conflicts compared to appending - but mostly because its easier to read.

@consideRatio consideRatio force-pushed the pr/linc branch 2 times, most recently from e3557e1 to e36de56 Compare March 26, 2024 21:11
@consideRatio consideRatio merged commit 3997eb2 into 2i2c-org:main Mar 27, 2024
17 of 19 checks passed
Copy link

🎉🎉🎉🎉

Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/8450195248

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.

2 participants