In Juju, deploying refers to the process where Juju uses a charm (from Charmhub or a local path) to install an application on a resource from a cloud.
Deploying on a Kubernetes cloud
The process
The result
Note: This diagram assumes a typical scenario with a single workload container (depending on the charm, there may be more and there may be none).
Deploying on a machine cloud
The process
The result
Deploying an application on a machine cloud: The result. This diagram assumes a typical scenario where the unit is deployed on a new machine of its own. (Note: The machine, model, unit, and controller agent are actually all part of the same jujud process and refer in fact to trees of workers with machine, model, unit and, respectively, controller responsibility.)
If you’re curious about deployments to a system container on a VM:
On most machine clouds, Juju makes it possible to deploy to a system container inside the machine rather to the machine directly. The result doesn’t change much: In terms of the diagram above, the only difference would be another box in between the “Regular Model Machine” and its contents and another machine agent for this box, as Juju treats system containers as regular machines.