-
Notifications
You must be signed in to change notification settings - Fork 15
Deploying the demo app
Ensure that you have git installed and fetch the repository:
$ git clone https://github.com/conjurinc/kubernetes-conjur-demo
Cloning into 'kubernetes-conjur-demo'...
remote: Enumerating objects: 57, done.
remote: Counting objects: 100% (57/57), done.
remote: Compressing objects: 100% (43/43), done.
remote: Total 337 (delta 24), reused 35 (delta 14), pack-reused 280
Receiving objects: 100% (337/337), 3.44 MiB | 5.61 MiB/s, done.
Resolving deltas: 100% (152/152), done.MiB/s, done.
Resolving deltas: 100% (191/191), done.
$ cd kubernetes-conjur-demo
[kubernetes-conjur-demo] $
In addition to the environment variables used in deploying Conjur, to deploy the demo app you must also set the following environment variables:
export AUTHENTICATOR_ID=openshift-test # can be set to anything (should indicate deploy env)
export TEST_APP_NAMESPACE_NAME=test-app # can be set to anything
As with the deployment step there are a series of scripts in the root of the repository numbered 0-7, each performs a step as described in the filename. The file start runs each in series to deploy the test app from start to finish, though again the manual steps are recommended. When complete, it will have deployed a small app that retrieves a secret using Summon and via the Conjur REST API and returns the secret when queried. Finally it will print out a demonstration of the secret having been successfully retrieved from Conjur.
When the final script is run, you will see that the two different flows (Conjur authentication via sidecar authenticator and via init container authenticator) are both able to retrieve a secret from Conjur either via Summon or using the Conjur REST API.