Closed consideRatio closed 2 weeks ago
Merging this PR will trigger the following deployment actions.
Cloud Provider | Cluster Name | Upgrade Support? | Reason for Support Redeploy | Upgrade Staging? | Reason for Staging Redeploy |
---|---|---|---|---|---|
aws | nasa-ghg | Yes | Following helm chart values files were modified: support.values.yaml | No | |
aws | nasa-veda | Yes | Following helm chart values files were modified: support.values.yaml | No | |
aws | nmfs-openscapes | Yes | Following helm chart values files were modified: support.values.yaml | No | |
aws | jupyter-meets-the-earth | Yes | Following helm chart values files were modified: support.values.yaml | No | |
aws | earthscope | Yes | Following helm chart values files were modified: support.values.yaml | No |
No production hub upgrades will be triggered
:tada::tada::tada::tada:
Monitor the deployment of the hubs here :point_right: https://github.com/2i2c-org/infrastructure/actions/runs/11660921803
Fixes five remaining clusters for https://github.com/2i2c-org/infrastructure/issues/4878:
nmfs-openscapes was a truly standalone account, but earthscope, jupyter-meets-the-earth, nasa-ghg, nasa-veda, were not standalone accounts. This means that we have failed to enable the cost allocation tags and need to followup with the community about this.