-
Notifications
You must be signed in to change notification settings - Fork 67
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] NeuroHackademy 2022 #1620
Comments
Confirmed! You can take it down whenever you are ready. Thanks! We've already migrated off data that we'd like to retain, so it is OK to delete everything stored there. |
I believe this event is over and the associated hub has been decommissioned. I am closing this issue. |
I reopened it because we need to merge #1721 and confirm some of the items listed above before closing it 😉. |
I've merged the PR and I confirm I followed all the manual decommissioning steps in the docs |
Thanks @GeorgianaElena! |
Summary
The hub is transient and event-focused hub and the event is over: #1300 (comment)
Info
Task List
Phase I
Phase 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.)
config/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.config/clusters/<cluster_name>/cluster.yaml
file.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.
terraform 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: