Consul
- By Canonical Kubernetes
- Monitoring
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 1 | 11 Nov 2020 | |
| latest/edge | 1 | 11 Nov 2020 |
juju deploy consul
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
-
bootstrap-expect | int
Default: 3
The number of expected servers in the datacenter. Before a Consul cluster can begin to service requests, a server node must be elected leader. Thus, the first nodes that are started are generally the server nodes. Bootstrapping is the process of joining these initial server nodes into a cluster. We recommend 3 or 5 total servers per datacenter. A single server deployment is highly discouraged as data loss is inevitable in a failure scenario.
-
domain | string
Default: consul
By default, Consul responds to DNS queries in the 'consul. domain. This flag can be used to change that domain. All queries in this domain are assumed to be handled by Consul and will not be recursively resolved.
-
log-level | string
Default: info
The level of logging to show after the Consul agent has started. This defaults to 'info'. The available log levels are 'trace', 'debug', 'info', 'warn', and 'err'. Note that you can always connect to an agent via consul monitor and use any log level.
-
version | string
Default: 0.6.3
The version of Consul software to install.