Update Consul-Registrator template to ask for Consul DC name. (#225)
This commit is contained in:
committed by
Bill Maxwell
parent
07cd1c2665
commit
2881ae2839
@@ -0,0 +1,26 @@
|
||||
# Consul-Registrator
|
||||
|
||||
### Info:
|
||||
|
||||
This templates creates a global service that deploys a Consul agent that is bound to the host's networking.
|
||||
This allows all Rancher hosts to join an existing Consul cluster.
|
||||
|
||||
Additionally, Registrator is deployed to automatically discover and register containers that are deployed on the host as Consul service entries.
|
||||
This allows for automatic service registration in Consul as Rancher schedule containers in the cluster.
|
||||
|
||||
The variables used in this template include:
|
||||
|
||||
- Hostname or IP address for the Consul cluster to join
|
||||
|
||||
The templates uses the official Consul & Registrator images
|
||||
|
||||
- [consul](https://hub.docker.com/r/_/consul/).
|
||||
- [registrator](https://hub.docker.com/r/gliderlabs/registrator/).
|
||||
|
||||
### Usage:
|
||||
|
||||
Select Consul from catalog.
|
||||
|
||||
Enter the hostname/DNS name/IP address of the Consul server to join
|
||||
|
||||
Click deploy.
|
||||
Reference in New Issue
Block a user