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] snowex.uwhackweek #2031
Comments
Thanks @consideRatio !
No. You can go ahead and wipe everything. Out of curiosity though, what is the general procedure for this? Are there docs with recommended options (e.g. an S3 bucket, lab server with a big usb-mounted hard drive, etc.) It could be something we want to do in the future. |
@scottyhq for now it seems we don't have such policies for migrating data well defined, see this documentation: https://infrastructure.2i2c.org/en/latest/hub-deployment-guide/hubs/other-hub-ops/delete-hub.html#migrate-data I recall Yuvi has done some work to package things into s3 buckets and provide links for users though. |
@scottyhq I see a S3 snowex-scratch bucket, is this fine to remove as well? |
@scottyhq there is still https://staging.uwhackweeks.2i2c.cloud up and running as I haven't worked to tear everything down, but only the snowex hub part of the uwhacksweek cluster. If everything uwhackweeks related should be cleaned up, there are further actions to take for us. Let us know if that is the case! |
Yes!
Yes, we're not anticipating any events in the near future so everything can be removed. Thanks @consideRatio ! |
Summary
It was a hack event that is now over.
Info
Task List
Phase I
UPDATE: Erik asked Scott via freshdesk ticket about this
Phase II - Hub Removal
(These steps are described in more detail in the docs at https://infrastructure.2i2c.org/en/latest/hub-deployment-guide/hubs/other-hub-ops/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 clusterterraform workspace delete <NAME>
config/clusters/<cluster_name>
directory and all its contentsdeploy-hubs.yaml
validate-clusters.yaml
The text was updated successfully, but these errors were encountered: