-
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] tufts.2i2c.cloud #4580
Comments
Thanks for the fast work creating this decommission request @jmunroe! Email trail to track the confirmation that it is ok to delete... Confirmed! David Grogan From: James Colliander <[email protected]> ...and a follow-up. Can you confirm whether we can shut down the hub and permanently delete all data, including data in user's home directories? Best, J. On Tue, 6 Aug 2024 at 10:06, James Colliander <[email protected]> wrote:
|
Phase 3 not required as Tufts is on a shared cluster |
Summary
Service agreement not renewed. See https://2i2c.freshdesk.com/a/tickets/1985 for context.
Info
Task List
Phase I
Phase II - Hub Removal
(These steps are described in more detail in the docs at https://infrastructure.2i2c.org/hub-deployment-guide/hubs/delete-hub/)
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
deployer use-cluster-credentials <cluster_name>
before running the above commandsPhase III - Cluster Removal
This phase is only necessary for single hub clusters.
deployer grafana central-ds remove <cluster_name>
terraform plan -destroy
andterraform apply
from the appropriate workspace, to destroy the clusterterraform workspace delete <NAME>
projects
folder associated with the relevant cloud provider (e.g.terraform/gcp/projects/
for GCP)config/clusters/<cluster_name>
directory and all its contentsdeploy-hubs.yaml
deploy-grafana-dashboards.yaml
The text was updated successfully, but these errors were encountered: