Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
consul [2016/12/12 05:38]
root created
consul [2020/01/27 05:45] (current)
root [Configuration setup using Key Value pairs - Web UI]
Line 8: Line 8:
 </​code>​ </​code>​
  
 +
 +== In Kube minikube == 
 +Consul setup is a simple ​
 +
 +<code bash>
 +docker pull consul
 +kubectl create -f kube-consul.yaml ​
 +</​code> ​
 +
 +or in helm3 
 +
 +<​code>​
 +helm3 install consul --version xx --generated-name ​
 +</​code>​
 +
 +
 +that sets up a pod running consul in our minikube environment. ​
 +
 +Consul creates a volume called /​consul/​data on to which you can store configuration **key-value pairs** in JSON format that could be directly imported using consul kv import @file.json. consul kv export > file.json can be used to export all stored configuration separated into JSON blobs by namespace.
 +
 +The consul commands can be run from inside the Consul container by starting ​ a shell in it using 
 +<​code>​
 +docker exec -ti <​consul-container-name>​ /bin/sh
 +</​code>​
 +
 +== Configuration setup using Key Value pairs - Web UI == 
 +
 +The namespaces for each microservice are defined either manually in the UI or via REST calls such as:
 +
 +The CLI is app(or namespace)/​key and value 
 +<code bash>
 +consul kv put my-app/​my-key my-value
 +</​code>​
 +
 +or similar via the web interface ​
 +
 +{{https://​forum.forgerock.com/​app/​uploads/​2018/​04/​Screen-Shot-2018-04-29-at-4.11.12-PM.png?​600px}}
 +
 +
 +
 +
 +== Links and Reference == 
 +* https://​forum.forgerock.com/​2018/​04/​runtime-config-for-forgerock-microservices-consul/​
 
consul.1481549911.txt.gz · Last modified: 2016/12/12 05:38 by root
 
RSS - 200 © CrosswireDigitialMedia Ltd