-
Notifications
You must be signed in to change notification settings - Fork 65
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
[Decommission Hub] Azure Hub for Carbon Plan #1618
Comments
Joe noted on Slack that the sponsorship account has been closed out for this hub and that the cluster/hub are down for good: https://2i2c.slack.com/archives/C01DB2JRP8W/p1661288927380899 I asked a clarifying question on whether this means we need to run If it's a case of cleaning up files, I'm more than happy to do that. |
@jhamman confirmed in Slack that all resources should be deleted in Azure, so we just need to clean up our repo |
@sgibson91 we should probably also delete the terraform workspace we used. |
@yuvipanda Yup, I had made a mental note but not written it down before a meeting 😄 |
PR to update the template here: #1653 |
PR to remove the cluster here: #1654 |
Thanks @sgibson91! |
Summary
Carbon Plan wishes to decommission their hub on Microsoft Azure. They will continue to use their AWS-based hub.
Info
Task List
Phase I
- [ ] Confirm with Community Representative that the hub is no longer in use and it's safe to decommission- [ ] Confirm if there is any data to migrate from the hub before decommissioning- [ ] If yes, confirm where the data should be migrated to- [ ] Confirm a 2i2c Engineer has access to the destination in order to complete the data migration- [ ] If no, confirm it is ok to delete all the data stored in the user home directoriesPhase II - Hub Removal
(These steps are decribed in more detail in the docs at https://infrastructure.2i2c.org/en/latest/howto/hubs/delete-hub.html.)
- [ ] Manage existing data (migrate data from the hub or delete it)- [ ] Remove the appropriateconfig/clusters/<cluster_name>/<hub_name>.values.yaml
files. A complete list of relevant files can be found under the appropriate entry in the associatedcluster.yaml
file.- [ ] Remove the associated hub entry from theconfig/clusters/<cluster_name>/cluster.yaml
file.- [ ] Remove the hub deployment-helm --namespace HUB_NAME delete HUB_NAME
-kubectl delete namespace HUB_NAME
Phase III - Cluster Removal
This phase is only necessary for single hub clusters.
- [ ] Runterraform plan -destroy
andterraform apply
from the appropriate workspace, to destroy the clusterconfig/clusters/<cluster_name>
directory and all its contentsdeploy-hubs.yaml
validate-clusters.yaml
The text was updated successfully, but these errors were encountered: