Usage: juju destroy-controller [options] <controller name>
Summary:
Destroys a controller.
Global Options:
--debug (= false)
equivalent to --show-log --logging-config=<root>=DEBUG
-h, --help (= false)
Show help on a command or other topic.
--logging-config (= "")
specify log levels for modules
--quiet (= false)
show no informational output
--show-log (= false)
if set, write the log file to stderr
--verbose (= false)
show more verbose output
Command Options:
-B, --no-browser-login (= false)
Do not use web browser for authentication
--destroy-all-models (= false)
Destroy all hosted models in the controller
--destroy-storage (= false)
Destroy all storage instances managed by the controller
--force (= false)
Force destroy hosted models ignoring any errors
--model-timeout (= -1s)
Timeout for each step of force model destruction
--no-wait (= false)
Rush through hosted model destruction without waiting for each individual step to complete
--release-storage (= false)
Release all storage instances from management of the controller, without destroying them
-y, --yes, --no-prompt (= false)
Do not ask for confirmation
Details:
All models (initial model plus all workload/hosted) associated with the
controller will first need to be destroyed, either in advance, or by
specifying `--destroy-all-models`.
If there is persistent storage in any of the models managed by the
controller, then you must choose to either destroy or release the
storage, using `--destroy-storage` or `--release-storage` respectively.
Sometimes, the destruction of a hosted model may fail as Juju encounters errors
that need to be dealt with before that model can be destroyed.
However, at times, there is a need to destroy a controller ignoring
such model errors. In these rare cases, use --force option but note
that --force will also remove all units of any hosted applications, their subordinates
and, potentially, machines without given them the opportunity to shutdown cleanly.
Model destruction is a multi-step process. Under normal circumstances, Juju will not
proceed to the next step until the current step has finished.
However, when using --force, users can also specify --no-wait to progress through steps
without delay waiting for each step to complete.
WARNING: Passing --force with --model-timeout will continue the final destruction without
consideration or respect for clean shutdown or resource cleanup. If model-timeout
elapses with --force, you may have resources left behind that will require
manual cleanup. If --force --model-timeout 0 is passed, the models are brutally
removed with haste. It is recommended to use graceful destroy (without --force, --no-wait or
--model-timeout).
Examples:
# Destroy the controller and all hosted models. If there is
# persistent storage remaining in any of the models, then
# this will prompt you to choose to either destroy or release
# the storage.
juju destroy-controller --destroy-all-models mycontroller
# Destroy the controller and all hosted models, destroying
# any remaining persistent storage.
juju destroy-controller --destroy-all-models --destroy-storage
# Destroy the controller and all hosted models, releasing
# any remaining persistent storage from Juju's control.
juju destroy-controller --destroy-all-models --release-storage
# Destroy the controller and all hosted models, continuing
# even if there are operational errors.
juju destroy-controller --destroy-all-models --force
juju destroy-controller --destroy-all-models --force --no-wait
See also:
kill-controller
unregister
