Cleanup

cub cluster down tears down a cluster's live kind cluster; with --delete-config it also deletes the cluster's ConfigHub side — the target, and every deployment bound to it.

To clean up everything in dev:

cub cluster down --name dev --delete-config

You can remove the --delete-config option if you want to keep your config. Same operation for prod:

cub cluster down --name prod --delete-config

Finally, remove the component. --recursive deletes its remaining variants first, which by now is only the base, with everything in them:

cub component delete --recursive cubbychat

To remove one variant on its own, cub variant delete cubbychat/dev does the same for one.

If you kept either cluster's config, its deployments are still there and go with the component. A deployment's units were cloned from the base's, which is why the two have to be deleted together, as --recursive does in one request. See deleting referenced entities.

Under the hood

Each variant is stored as a space, named for the component and variant joined with a dash, cubbychat-base. That is the name the --space flag in help text takes, and cub space delete cubbychat-base --recursive is what cub variant delete cubbychat/base runs.