updated the catalog for the secrets-bridge v1.2.0 release

This commit is contained in:
Bill Maxwell
2016-12-01 09:55:14 -08:00
parent 85ffaf7566
commit ee01de0379
10 changed files with 137 additions and 2 deletions
@@ -1,6 +1,7 @@
.catalog:
name: "Secrets Bridge Agent"
version: 0.0.1-rancher1
maximum_rancher_version: v1.2.0-pre3
description: |
Agent side of secrets bridge between Rancher and Vault
questions:
@@ -0,0 +1,20 @@
## Secrets Bridge Agents (Experimental)
---
###Status: Experimental POC (Read: Do NOT use for production)
Only works with Hashicorp Vault server in dev mode currently.
---
#### Description:
This is the agent component for the Vault secrets bridge with Rancher. This service will be deployed in the environment running applications that need secrets. This service does not have direct access to Vault, it communicates with the Secrets Bridge server.
#### Setup
See [setup guide](https://github.com/rancher/secrets-bridge/blob/master/docs/setup.md)
#### Pre-reqs:
An instance of Secrets Bridge server running.
#### Running this app
As services come up, this service will send events to the Secrets Bridge based on Docker start events. The server will (Not currently enforced) verify the signed token with Rancher server and get the launching containers Rancher environment, stack, service and Docker ID. With that information the Secrets Bridge server will check with Vault in the `configPath/environment/stack/service/container_name` for a key called policies. It checks from most specific and recursively looks down to the environment key. It uses the most specific match.
@@ -0,0 +1,10 @@
secrets-bridge:
image: rancher/secrets-bridge:v0.2.0
command: agent --bridge-url ${BRIDGE_URL}
volumes:
- /var/run/docker.sock:/var/run/docker.sock
privileged: true
labels:
io.rancher.container.create_agent: true
io.rancher.container.agent.role: agent
io.rancher.scheduler.global: true
@@ -0,0 +1,12 @@
.catalog:
name: "Secrets Bridge Agent"
minimum_rancher_version: v1.2.0
version: 0.1.0-rancher1
description: |
Agent side of secrets bridge between Rancher and Vault
questions:
- variable: BRIDGE_URL
type: string
label: "Secrets Bridge URL"
required: true
description: "Should be the http(s)://address:port version of the url"
+1 -1
View File
@@ -1,4 +1,4 @@
name: "Secrets Bridge Agents"
description: "Agent side of bridge between Vault and Rancher"
version: "0.0.1-rancher1"
version: "0.1.0-rancher1"
category: Security