Deployment
In Juju, a deployment is all the infrastructure that Juju manages and the applications running on that infrastructure. This document gives details about what a deployment looks like depending on the infrastructure – that is, what the agent, worker, charm, workload, unit, etc., setup looks like when you deploy an application on a machine cloud versus a Kubernetes cloud.
Contents:
Machine deployment
The diagram below depicts the result of running juju deploy <machine charm> on a machine cloud, assuming a typical scenario with just one unit per machine (there may be more).
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 BM/VM and its contents standing in for the system container, and two sets of machine agents and machine workers instead of one, one for the BM/VM and one for the container.
Kubernetes deployment
The diagram below depicts the result of running juju deploy <kubernetes charm> on a Kubernetes cloud, assuming a typical case with just one workload container per pod (there may be more and there may be none).
Last updated a month ago.