juju / juju/juju-controller

Documentation as how to setup a public controller

Open
#37 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
3
Forks
19
Avg merge
1d 15h
Merged PRs (30d)
8

Description

https://github.com/juju/juju-controller/blob/6b980132bc4c14a16e5d0618892f2f8b10589e1d/README.md?plain=1#L9

I've been trying to figure out what a best practice setup actually looks like with a controller. This might be the place to cover at least a basic example?

For example:

  • If I deploy more than 3 units of this charm - will it enter into ha?
  • What considerations do I need to make in terms of SSL/TLS?
  • Example how to set the juju-mgmt-space in controller config, which will cause agents to communicate with controllers via that space.
  • Example how to set the juju-ha-space in controller config that is the space used to replicate Mongo across the control plane.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked README.md section and review how a public controller is currently introduced. Document a basic setup covering high availability, SSL/TLS considerations, and examples for juju-mgmt-space and juju-ha-space; the listed questions should be answered in the resulting guidance.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, infrastructure
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.