Skip to content

Commit 78a3a42

Browse files
Added step to destroy stack.
1 parent 402d125 commit 78a3a42

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

INSTALLING_ONTO_EXISTING_CLUSTER_README.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ This guide helps you install and use **OCI AI Blueprints** for the first time on
88
4. Learn how to add existing nodes in the cluster to be used by blueprints.
99
5. Deploy a sample recipe to that node.
1010
6. Test your deployment and undeploy
11+
7. Destroy the stack
1112

1213
There is an additional section at the bottom for users who have the nvidia-gpu-operator installed, and would like to use Multi-Instance GPUs with H100 nodes visit [this section](./INSTALLING_ONTO_EXISTING_CLUSTER_README.md#multi-instance-gpu-setup).
1314

@@ -176,6 +177,12 @@ curl -L -H "Content-Type: application/json" -d '{"model": "/models/NousResearch/
176177
- go to Api Root -> deployment_logs
177178
- Look for: Directive decommission -> Ingress deleted -> Deployment deleted -> Service deleted -> Directive / decommission / completed.
178179

180+
## Step 7: Destroy the stack
181+
Destroying the OCI AI Blueprints stack will not destroy any resources which were created or destroyed outside of the stack such as node pools or helm installs. Only things created by the stack will be destroyed for the stack. To destroy the stack:
182+
183+
1. Go to the console and navigate to Developer Services -> Resource Manager -> Stacks -> Your OCI AI Blueprints stack
184+
2. Click "Destroy" at the top
185+
179186
## Multi-Instance GPU Setup
180187
If you have the nvidia gpu operator already installed, and would like to reconfigure it because you plan on using Multi-Instance GPUs (MIG) with your H100 nodes, you will need to manually update / reconfigure your cluster with helm.
181188

0 commit comments

Comments
 (0)