Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better documentation as what this does for a user #36

Open
erik78se opened this issue Oct 16, 2023 · 2 comments
Open

Better documentation as what this does for a user #36

erik78se opened this issue Oct 16, 2023 · 2 comments

Comments

@erik78se
Copy link

The documentation on this item can use some love to help someone setup a controller.

Why would I use this and with what? What is the impact?

controller-url:

@barrettj12
Copy link
Contributor

Juju sets up the correct value here, the user should not have to set this config key.

@erik78se
Copy link
Author

I bootstrapped a juju 2.9.45 controller into aws. Then I manually deployed the charm on-to the machines like this:

juju switch admin/controller
juju enable-ha
juju deploy juju-controller --to 0
juju add-unit juju-controller --to 1
juju add-unit juju-controller --to 2

This is because I want to be able to relate it to haproxy down the road since I want to be able to use the controller with a public DNS name "my-controller.foo.bar" and somehow be able to expose a valid certificate for it.

Or - there might be a better way to achieve this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants