The information in this doc is based on Juju version 3.5.5, and may not accurately reflect other versions of Juju.
See also: destroy-controller, unregister
Summary
Forcibly terminate all machines and other associated resources for a Juju controller.
Usage
juju kill-controller [options] <controller name>
Options
| Flag | Default | Usage |
|---|---|---|
-B, --no-browser-login |
false | Do not use web browser for authentication |
--no-prompt |
false | Do not ask for confirmation |
-t, --timeout |
5m0s | Timeout before direct destruction |
Details
Forcibly destroy the specified controller. If the API server is accessible, this command will attempt to destroy the controller model and all models and their resources.
If the API server is unreachable, the machines of the controller model will be destroyed through the cloud provisioner. If there are additional machines, including machines within models, these machines will not be destroyed and will never be reconnected to the Juju controller being destroyed.
The normal process of killing the controller will involve watching the models as they are brought down in a controlled manner. If for some reason the models do not stop cleanly, there is a default five minute timeout. If no change in the model state occurs for the duration of this timeout, the command will stop watching and destroy the models directly through the cloud provider.