@@ -31,6 +31,7 @@ Conjur Open Source is part of the CyberArk Privileged Access Security Solution w
31
31
* [ Deploying Without LoadBalancer Support (e.g. for KinD, MiniKube, KataCoda)] ( #deploying-without-loadbalancer-support-eg-for-kind-minikube-katacoda )
32
32
* [ Debugging] ( #debugging )
33
33
* [ PostgreSQL Database Password Restrictions] ( #postgresql-database-password-restrictions )
34
+ - [ What's Next? Deploy an Example Application That Uses Conjur Secrets] ( #whats-next-deploy-an-example-application-that-uses-conjur-secrets )
34
35
- [ Deleting the Conjur Deployment] ( #deleting-the-conjur-deployment )
35
36
* [ Uninstalling the Chart via Helm Delete] ( #uninstalling-the-chart-via-helm-delete )
36
37
* [ Cleaning Up Kubernetes Secrets Not Managed by Helm] ( #cleaning-up-kubernetes-secrets-not-managed-by-helm )
@@ -200,7 +201,7 @@ container to create an account during startup. To retrieve the credentials
200
201
for this account, perform the following commands:
201
202
202
203
``` sh-session
203
- ACCOUNT_NAME =<conjur-account-name>
204
+ CONJUR_ACCOUNT =<conjur-account-name>
204
205
CONJUR_NAMESPACE=<conjur-namespace>
205
206
HELM_RELEASE=<helm-release>
206
207
POD_NAME=$(kubectl get pods --namespace "$CONJUR_NAMESPACE" \
@@ -209,7 +210,7 @@ POD_NAME=$(kubectl get pods --namespace "$CONJUR_NAMESPACE" \
209
210
kubectl exec --namespace "$CONJUR_NAMESPACE" \
210
211
"$POD_NAME" \
211
212
--container=conjur-oss \
212
- -- conjurctl role retrieve-key "$ACCOUNT_NAME ":user:admin | tail -1
213
+ -- conjurctl role retrieve-key "$CONJUR_ACCOUNT ":user:admin | tail -1
213
214
```
214
215
215
216
> Note: If you have ` logLevel ` set to ` debug ` , the ` tail -1 ` command will truncate the output.
@@ -219,14 +220,14 @@ If you set `account.create` to `false`, or did not provide a value, an admin acc
219
220
need to be created. To create an account, use the following commands:
220
221
221
222
``` sh-session
222
- ACCOUNT_NAME =<Name for Conjur account to be created>
223
+ CONJUR_ACCOUNT =<Name for Conjur account to be created>
223
224
POD_NAME=$(kubectl get pods --namespace "$CONJUR_NAMESPACE" \
224
225
-l "app=conjur-oss,release=$HELM_RELEASE" \
225
226
-o jsonpath="{.items[0].metadata.name}")
226
227
kubectl exec --namespace $CONJUR_NAMESPACE \
227
228
$POD_NAME \
228
229
--container=conjur-oss \
229
- -- conjurctl account create $ACCOUNT_NAME | tail -1
230
+ -- conjurctl account create $CONJUR_ACCOUNT | tail -1
230
231
```
231
232
The credentials for this account will be provided after the account has been created.
232
233
Store these in a safe location.
@@ -452,6 +453,40 @@ The following restrictions apply to the PostgreSQL database password:
452
453
[ "-", ".", "_ ", or "~ "]
453
454
- Password length must be less than or equal to 64 characters.
454
455
456
+ ## What's Next? Deploy an Example Application That Uses Conjur Secrets
457
+
458
+ If you are new to Conjur, you may be interested in learning more about how
459
+ Conjur security policy can be configured and an application can
460
+ be deployed that uses Conjur OSS to safely manage secrets data.
461
+
462
+ This repository contains a set of scripts that can:
463
+
464
+ - Create a [ Kubernetes-in-Docker] ( https://github.com/kubernetes-sigs/kind )
465
+ (KinD) cluster on your local machine
466
+ - Helm install a Conjur OSS cluster on that KinD cluster
467
+ - Enable the
468
+ [ Conjur Kubernetes Authenticator] ( https://docs.conjur.org/Latest/en/Content/Operations/Services/k8s_auth.htm )
469
+ (authn-k8s) (as a security admin)
470
+ - Load Conjur security policies for some example applications
471
+ (as a security admin)
472
+ - Deploy instances of a simple "Pet Store" application each using
473
+ one of the following Conjur authentication broker/clients:
474
+ - [ Secretless Broker] ( https://github.com/cyberark/secretless-broker ) sidecar container
475
+ - [ Conjur Kubernetes Authenticator Client] ( https://github.com/cyberark/conjur-authn-k8s-client )
476
+ sidecar container
477
+ - [ Conjur Kubernetes Authenticator Client] ( https://github.com/cyberark/conjur-authn-k8s-client )
478
+ init container
479
+ (as an application developer/deployer)
480
+
481
+ Please refer to the [ README.md] ( ../examples/kubernetes-in-docker/README.md )
482
+ file in the ` ../examples/kubernetes-in-docker ` directory for more details
483
+ on how to run these demo scripts.
484
+
485
+ These scripts will also generate some application-specific Conjur policy
486
+ YAML files and Kubernetes application manifests as concrete examples of
487
+ how applications can be deployed that use Conjur Kubernetes authentication
488
+ to safely retrieve secrets.
489
+
455
490
## Deleting the Conjur Deployment
456
491
457
492
Uninstalling or deleting a Conjur deployment involves two steps:
0 commit comments