Add a machine cloud¶

First, check thelist of supported machine clouds to see if your cloud is supported, or the cloud-specific doc linked from there to see if your cloud must meet any prerequisites.

Then, if your cloud is a public cloud or a localhost LXD cloud: Juju likely already knows about it, so you can skip this step; runjujuclouds to verify.

Otherwise, to add a machine cloud to Juju, run theadd-cloud command:

juju add-cloud

This will start an interactive session where you’ll be asked to choose a cloud type (from a given list), the name that you want to use for your cloud, the API endpoint, the authentication type, etc. Juju will use this to create a cloud definition.

The command also has a manual mode where you can specify the desired cloud name and cloud definition file in-line; whether you want this definition to be known just to the Juju client or also to an existing controller (the latter creates what is known as a multi-cloud controller); etc.

Add a Kubernetes cloud¶

First, check thelist of supported clouds to see if your cloud is supported, or the cloud-specific doc linked from there to see if your cloud must meet any prerequisites.

Then, if you’re using a localhost MicroK8s cloud installed from a strictly confined snap: Juju likely already knows about it, so you can skip this step; runjujuclouds to verify.

Otherwise, to add a Kubernetes cloud to Juju:

1. Prepare your kubeconfig file.

2. Run theadd-k8s command followed by the desired cloud name:

juju add-k8s <cloud name>

Juju will check the default location for the kubeconfig file and use the information in there to create a cloud definition.

The command also allows you to specify a non-default kubeconfig file path (via theKUBECONFIG environment variable); in the case where you have multiple cluster definitions and credentials in your kubeconfig file, which cluster and credential to use; what name you want to assign to your new cloud; whether you want to make this cloud known just to the client or also to an existing controller (the latter gives rise to what is known as a multi-cloud controller); etc.

View all the known regions¶

To see which regions Juju is aware of for any given cloud, use theregions command. For example, for theaws cloud, run:

juju regions aws

Client Cloud Regionsus-east-1us-east-2us-west-1us-west-2ca-central-1eu-west-1eu-west-2eu-west-3eu-central-1eu-north-1eu-south-1af-south-1ap-east-1ap-south-1ap-southeast-1ap-southeast-2ap-southeast-3ap-northeast-1ap-northeast-2ap-northeast-3me-south-1sa-east-1

The command also has flags that allow you to select a specific controller, choose an output format or file, etc.

Manage the default region¶

Set the default region. To set the default region for a cloud, run thedefault-region command followed by the name of the cloud and the name of the region that you want to start using as a default. For example:

juju default-region aws eu-central-1

If at any point you want to reset this value, drop the region argument and pass the--reset flag.

Get the default region. To get the current default region for a cloud, run thedefault-region command followed by the name of the cloud. For example:

juju default-region azure-china

Update a public cloud¶

To synchronise the Juju client with changes occurring on public clouds (e.g. cloud API changes, new cloud regions) or on Juju’s side (e.g. support for a new cloud), run theupdate-public-clouds command:

juju update-public-clouds

The command also allows you to specify whether you want this update to happen on the client or a controller.

Update a private cloud¶

To update Juju’s definition for a private cloud, run theupdate-cloud command followed by the cloud name and the-f flag followed by the path to the new cloud definition file. For example:

juju update-cloud mymaas -f path/to/maas.yaml

The command also allows you to indicate whether the update should happen on the client or the controller; to update the definition on a controller to match the one on the client; etc.