Document how to deploy as part of a bootstrap with enable-ha

[erik78se]

When I deployed this charm, I had to do the following to get it to work in a public cloud.

• Bootstrap
  juju bootstrap my.controller.com aws/eu-north-1

• Set admin password (to avoid issues later)
  juju change-user-password

• Create a new user (so I don't need to act as admin all the time). (Log out as admin)
  juju add-user erik-lonroth
  juju grant erik-lonroth superuser
  juju logout
  juju login -u erik-lonroth

• Enable ha (spawns 2 more machines)
  enable-ha

• Deploy the charm on-to the machines.
  juju deploy juju-controller --to 0
  juju add-unit juju-controller --to 1
  juju add-unit juju-controller --to 2

Now, I don't know is it matters setting the controller-url config. The docs doesn't say. Perhaps I should...

[barrettj12]

@erik78se you should never have to deploy this charm. Juju 3.0+ automatically deploys it as required (in the controller model). In fact, I'm surprised you were allowed to deploy it, I thought Juju would block you from doing so.

Why are you trying to deploy it?

[erik78se]

I'm on a juju 2.9.45 controller.

I'm trying to deploy a controller as a replacement for JaaS since its about to be decommissioned and we need a replacement. Going to juju 3.0 is not possible for us yet so we need to get something up to migrate into.

[moula]

Bonjour @erik78se. I have always done the same as you but on my local maas cloud.
3 machines tagged on my maas and with the command : juju enable-ha -n 3 --to node2,node3 and it works. Thank's.
![Capture d’écran du 2023-10-23 13-32-48]
(https://github.com/juju/juju-controller/assets/1804815/262c6a83-8602-4035-84ba-aa64ffda79c1)