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

nmfs-openscapes: revert use of r7i instead of r5 and hub dedicated nodes #4930

Merged
merged 1 commit into from
Oct 3, 2024

Conversation

consideRatio
Copy link
Member

@consideRatio consideRatio commented Oct 3, 2024

The reverting of hub dedicated nodes was also done on my own initiative, as I think that was also done on my initiative without explicit instruction.

Copy link

github-actions bot commented Oct 3, 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 nmfs-openscapes No Yes Following helm chart values files were modified: staging.values.yaml, common.values.yaml

Production deployments

Cloud Provider Cluster Name Hub Name Reason for Redeploy
aws nmfs-openscapes prod Following helm chart values files were modified: prod.values.yaml, common.values.yaml

@consideRatio consideRatio merged commit c95ff69 into 2i2c-org:main Oct 3, 2024
8 checks passed
Copy link

github-actions bot commented Oct 3, 2024

🎉🎉🎉🎉

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

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.

Revert moving away from r5 instances on AWS
1 participant