List of supported clouds > MicroK8s
This document describes details specific to using your existing MicroK8s cloud with Juju.
See more: MicroK8s
When using the MicroK8s cloud with Juju, it is important to keep in mind that it is a (1) Kubernetes cloud and (2) not some other cloud.
See more: Cloud differences in Juju
As the differences related to (1) are already documented generically in our Tutorial, How-to guides, and Reference docs, here we record just those that follow from (2).
| Juju points of variation | Notes for the MicroK8s cloud |
|---|---|
| setup (chronological order): | |
| CLOUD | |
| supported versions: | TBA |
| requirements: | The dns and hostpath-storage must be enabled. |
| definition: | Cf. kubeconfig file.  Juju automatically defines a local cloud of this type. |
| - name: | microk8s or user-defined |
| - type: | k8s |
| - authentication types: | [oauth2, clientcertificate, userpass] |
| - regions: | [TO BE ADDED] |
| - cloud-specific model configuration keys: | operator-storage (string) Sets the storage class used to provision operator storage. workload-storage (string) Sets the preferred storage class used to provision the workload storage. |
| CREDENTIAL | |
| definition: | Cf. kubeconfig file. If you are an admin Juju user and your cloud is a local MicroK8s cloud: Juju retrieves your credential definition automatically. Run |
| CONTROLLER | |
| notes on bootstrap: | – |
| other (alphabetical order:) | |
| CONFIGURATION (model) | |
| cloud-specific: | TBA |
| CONSTRAINT | Not applicable. |
| PLACEMENT DIRECTIVE | |
<machine> |
TBA |
subnet=... |
 |
system-id=... |
|
zone=... |
TBA |
| MACHINE | |
| RESOURCE (cloud) Consistent naming, tagging, and the ability to add user-controlled tags to created instances. |
|