From 313f89c2d9d2b64b5584ae2882e2dc88be7aa1eb Mon Sep 17 00:00:00 2001 From: Sean Knox Date: Sun, 4 Mar 2018 12:24:51 -0800 Subject: [PATCH] (azure): change default location, add info (#7629) * (azure): change default location, add info * (ubuntu): fix CLI typo --- docs/getting-started-guides/ubuntu/installation.md | 8 +++++++- docs/getting-started-guides/ubuntu/troubleshooting.md | 2 +- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/getting-started-guides/ubuntu/installation.md b/docs/getting-started-guides/ubuntu/installation.md index 85665e8597..521a130907 100644 --- a/docs/getting-started-guides/ubuntu/installation.md +++ b/docs/getting-started-guides/ubuntu/installation.md @@ -90,9 +90,15 @@ juju bootstrap aws/us-east-2 or, another example, this time on Azure: ``` -juju bootstrap azure/centralus +juju bootstrap azure/westus2 ``` +If you receive this error, it is likely that the default Azure VM size (Standard D1 v2 [1 vcpu, 3.5 GB memory]) is not available in the Azure location: +``` +ERROR failed to bootstrap model: instance provisioning failed (Failed) +``` + + You will need a controller node for each cloud or region you are deploying to. See the [controller documentation](https://jujucharms.com/docs/2.2/controllers) for more information. Note that each controller can host multiple Kubernetes clusters in a given cloud or region. diff --git a/docs/getting-started-guides/ubuntu/troubleshooting.md b/docs/getting-started-guides/ubuntu/troubleshooting.md index 134b6cd672..335cf23dd7 100644 --- a/docs/getting-started-guides/ubuntu/troubleshooting.md +++ b/docs/getting-started-guides/ubuntu/troubleshooting.md @@ -46,7 +46,7 @@ During normal operation the Workload should read `active`, the Agent column (whi Status can become unwieldy for large clusters, it is then recommended to check status on individual services, for example to check the status on the workers only: - juju status kubernetes-workers + juju status kubernetes-worker or just on the etcd cluster: