auth

Paddy 2015-06-29

176:fc68085eb40d Go to Latest

auth/services/authd.json

Add kubernetes definitions. Define a replication controller that will spin up authd servers (using Ducky right now--other instances should rename the ducky parts appropriately). Also, my understanding of which labels go where may be shaky, which is probably evidenced by the fact that all of these things share the same lables. _Whatever_. It also hooks the generated pods up to the JWT secret volume, so they can properly read the JWT secret. Also, created a LoadBalancer Service that will route traffic to the pods created by the Replication Controller.

History
paddy@176 1 {
paddy@176 2 "kind":"Service",
paddy@176 3 "apiVersion":"v1",
paddy@176 4 "metadata":{
paddy@176 5 "name":"ducky-authd",
paddy@176 6 "labels":{
paddy@176 7 "name":"authd",
paddy@176 8 "context": "ducky",
paddy@176 9 "repo": "secondbit--authd",
paddy@176 10 "role": "auth"
paddy@176 11 }
paddy@176 12 },
paddy@176 13 "spec":{
paddy@176 14 "ports": [
paddy@176 15 {
paddy@176 16 "name": "http",
paddy@176 17 "port": 80,
paddy@176 18 "targetPort": "http"
paddy@176 19 }
paddy@176 20 ],
paddy@176 21 "selector":{
paddy@176 22 "name":"authd",
paddy@176 23 "context": "ducky",
paddy@176 24 "repo": "secondbit--authd",
paddy@176 25 "role": "auth"
paddy@176 26 },
paddy@176 27 "type": "LoadBalancer"
paddy@176 28 }
paddy@176 29 }