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 when you deploy an application on a machine cloud versus a Kubernetes cloud.

Contents:

Machine deployment


What happens when you run juju deploy on a machine cloud.


The result of running juju deploy on a machine cloud (see esp. the “Regular Unit”), assuming a typical scenario where the units is deployed on a new machine of its own.

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.

See more: Machine > Machines and system (LXD) containers

Kubernetes deployment


What happens when you run juju deploy on a Kubernetes cloud.


The result of running juju deploy on a Kubernetes cloud (see esp. the “Regular Unit”), assuming a typical scenario with just one workload container per pod (depending on the charm, there may be more and there may be none).