adc delete
Definition
Reads one or more documents (each may hold several configurations separated by the --- line) and deletes the rendered objects. Ordinary deletion of an operator document removes only its Deployment but keeps the CRDs, RBAC, ServiceAccount, Namespaces, pull secrets, and Kerberos support objects. Workload documents are fully deleted.
Usage
$ adc delete --file <file> [--file <file>...] \
[--kubeconfig <kubeconfig>] \
[--prefix <prefix>] \
[--dry-run] \
[--purge]| Parameter | Description |
|---|---|
-f, --file |
Path to a configuration YAML file. Several files can be provided by repeating the flag |
-k, --kubeconfig |
Path to a kubeconfig file. The default value is |
-p, --prefix |
Prefix that is added before |
--dry-run |
Lists the resources that would be deleted without actually deleting them |
--purge |
Specifies that an operator should be deleted along with its footprint including CRDs. Does not affect workload document deletion |
Examples
Trino operator
Checking what will be deleted if --purge is not specified:
$ adc delete -f trino-operator.yaml --dry-runOutput:
The following resources will be deleted: - Deployment/trino-operator-trino-operator
Checking what will be deleted if --purge is specified:
$ adc delete -f trino-operator.yaml --purge --dry-runOutput:
The following resources will be deleted: - CustomResourceDefinition/clusters.trino.arenadata.io - Deployment/trino-operator - RoleBinding/trino-operator-payload - Role/trino-operator-payload - RoleBinding/trino-operator-manager - Role/trino-operator-manager - ServiceAccount/trino-operator - Namespace/trino-operator
Actually deleting Trino operator along with its footprint:
$ adc delete -f trino-operator.yaml --purge