This topic tells you how to remove all the resources that were created during the setup of the infrastructure and the application environment. The clean-up includes the following resources:
AWS account in Tanzu Platform
The process also deletes the monitoring resources that were created.
Deleting a Space will delete all the application resources within the Space, including any applications and dependent resources such as Route53 records.
You can delete a Space using either Tanzu Platform hub or the Tanzu CLI.
tanzu space delete <space name>
Deleting an application deletes the application itself and all of the related resources that were created during the build. The related resources vary according to the type of runtime, for example:
kubernetes-carvel-package
runtime, the related resources are Package
, PackageInstall
, and the Secret
for configuring the PackageInstall
.kubernetes-fluxcd-helm-chart
runtime, the related resources are HelmRepository
, HelmRelease
, and Secret
.You can delete an application by using either the Tanzu Platform UI or the Tanzu CLI.
tanzu app delete <app name>
Deleting clusters using Tanzu CLI is not currently supported.
To delete a cluster group from your project with Tanzu Platform hub, use the following steps:
The cluster will now detach from the Tanzu Platform and initiate the deletion of the EKS node group and the control plane from AWS. The deletion process can take 30-45 minutes.
As part of the onboarding, if you created an AWS VPC and it’s no longer deleted, you can delete the VPC from your AWS account using the following steps:
When the AWS Account was on-boarded to Tanzu Platform, resources were created within the AWS account in each region for event monitoring. Removing the account from the Tanzu Platform will cleanup these resources.
Follow the instructions in the UI to Detach the cluster from the collection.
NoteSince the cluster has already been deleted, you can skip the steps for deleting the
aria-k8s
namespace in Step 1 of the instructions in the UI.
Follow the instructions in the UI to deactivate event monitoring. This will remove the cloudformation templates in region that were created for event monitoring.
NoteThis step requires the AWS CLI to be able to authenticate to your AWS account.
In the Add AWS Account step, you created a TanzuSecurityAudit role in your AWS account that gave AssumeRole permissions for Tanzu Platform. To remove this permission, do the following:
In the Create EKS Credentials step, when you created a CloudFormation stack, a number of resources were created in your AWS account. The resources created include a CloudFormation stack, IAM roles/policies, Lambda functions, Cloud Watch Events, and an SSM parameter.
NoteSome of the resources that are created may be automatically cleaned up after the credential object is deleted in Tanzu Platform.
To remove the resources:
Delete the credential resource on Tanzu Platform.
Find and delete the Lambdas.
To find the lambdas, from the AWS console, go to Lambda > Functions and search by tag.
Tanzu adds two types of tags to the lambdas:
Find and delete the Cloud Watch events.
The Cloud Watch events are listed under the Amazon Event bridge rules. These have the same tags applied as above, and there are two event rules that correspond to the two Lambdas from the previous step.
Search for the ssm
parameter in the Amazon Systems Manager parameter store.
There is one parameter that Tanzu uses called the agent token
. It has the same two tags as the two Lambdas that Tanzu adds.
Locate and delete the CloudFormation template.
The CloudFormation template starts with eks-tmc-cloud-vmware-com-
. It has a stack parameter of CredentialName
with a value equal to the name of your credential in the Tanzu Platform.
In the Create Route 53 GSLB credentials step, you created a CloudFormation stack which in turn created an IAM role and policy to support the GSLB function. To remove this permission, do the following:
Delete the credential resource from the Tanzu Platform.
On the AWS Console,
Find the CF Stack that was created for GSLB.
It starts with gslb-hub-cloud-vmware-com-
, and has a stack parameter of CredentialName
with a value equal to the name of your credential in the Tanzu Platform.
Select this stack.
On the stack details page, click Delete to delete the stack.
This removes the IAM role and associated IAM policies.