Skip to content

docs: Drop openshiftClusterID #438

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.

Sign up for GitHub

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

Merged
thoraxe merged 1 commit into from
Mar 6, 2019
Merged

docs: Drop openshiftClusterID #438

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions docs/05-infrastructure-nodes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -253,8 +253,6 @@ spec:
values:
- 190125-3-worker-us-west-1b
tags:
- name: openshiftClusterID
value: 45d08e94-6bf6-4fd3-988f-54a616d04252
- name: kubernetes.io/cluster/190125-3
value: owned
userDataSecret:
Expand Down Expand Up @@ -506,4 +504,4 @@ operator.

## Logging
OpenShift's log aggregation solution is not installed by default with
`4.0.0-0.2` and is not deployable in its current state of development.
`4.0.0-0.2` and is not deployable in its current state of development.
19 changes: 5 additions & 14 deletions docs/06-cleanup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,19 +1,10 @@
# Deleting the Cluster and Cleaning up
Cleaning up your cluster is trivial. However, on the off chance that the
cleanup fails, you will be left with AWS resources that are undeleted.
Finding them can be tricky, but they have a key:value tag of
`openshiftClusterID:<cluster_uuid>` and then you can carefully delete them by
hand.

Just in case, be sure to grab the UUID before destroying the cluster:

oc get clusterversion -o jsonpath='{.spec.clusterID}{"\n"}' version

If you are trying to destroy your cluster because of a failed installation,
you may not be able to use `oc`. In that case, you can look for the UUID in
the `metadata.json` asset:

jq -r .clusterID metadata.json
Cleaning up your cluster is straightforward *if* you preserved the
`metadata.json` file from cluster creation. It is usually possible to
reconstruct the file if you lose it, but that depends on still having
a functioning cluster or poking around in AWS, so it's better to just
hang on to the file.

The following command will read `metadata.json` and remove the
OpenShift 4 cluster and all underlying AWS resources that were created
Expand Down