juju destroy-controller [options] <controller name>
Destroys a controller.
--debug (= false)
Equivalent to --show-log --logging-config==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
-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 (= 30m0s)
Timeout before each individual hosted model destruction is aborted
--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 (= false)
Do not ask for confirmation
All models (initial model plus all workload/hosted) associated with the
controller will first need to be destroyed, either in advance, or by
If there is persistent storage in any of the models managed by the
controller, then you must choose to either destroy or release the
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.
# 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
Last updated 1 year, 3 months ago.