flywithu/community-catalog
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

updating to v0.0.3 (#233)

Browse Source 
The new version of the agent, can be launched via cattle and run in a k8s environment.
This commit is contained in:
Bill Maxwell 2016-07-28 17:35:44 -07:00 committed by GitHub
parent ad23789819
commit 1e281a0c72
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
templates/secrets-bridge-agents/0/docker-compose.yml
View File

@ -1,5 +1,5 @@
secrets-bridge:
image: rancher/secrets-bridge:v0.0.2
image: rancher/secrets-bridge:v0.0.3
command: agent --bridge-url ${BRIDGE_URL}
volumes:
- /var/run/docker.sock:/var/run/docker.sock

2
templates/secrets-bridge-server/0/README.md
View File

@ -7,7 +7,7 @@ Only works with Hashicorp Vault server in dev mode currently.
#### Description:
This is the server side component for the Vault Secrets bridge with Rancher. This service should *NOT* be deployed in the same environment as user applications. It will have access to Vault, and compromising it will give the person access to *ALL* secrets available in that environment. It should instead be run in an environment reserved for the team operating Rancher.
The reason this uses a temporary Cubbyhole token to start the service is that ENV variables do show up in the Rancher API and Docker inspect commands.
The reason this uses a temporary Cubbyhole token to start the service is that ENV variables do show up in the Rancher API and Docker inspect commands. That said, if this service fails, the issuing token will expire and all app tokens will also expire.
#### Pre-reqs:

2
templates/secrets-bridge-server/0/docker-compose.yml
View File

@ -1,5 +1,5 @@
secrets-bridge:
image: rancher/secrets-bridge:v0.0.2
image: rancher/secrets-bridge:v0.0.3
environment:
CATTLE_ACCESS_KEY: ${CATTLE_ACCESS_KEY}
CATTLE_SECRET_KEY: ${CATTLE_SECRET_KEY}