secrets-provider-for-k8s
secrets-provider-for-k8s copied to clipboard
Fix demo
While improving out tests, we broke our demo. We should fix this so it is easier to demo the secrets-provider.
Also, it is best no to use ./demo/pet-store-env.sh.yml | $cli create -f -
and create a generated yml
file instead. This is better for the demo as we can load the YAML file that is created by ourselves.
TODO:
- [ ] look into when
DAP_MASTER_CLUSTER
should be false - [ ] open PR for issue opened in
kubernetes-conjur-deploy
(https://github.com/cyberark/kubernetes-conjur-deploy/issues/117) - [ ] get E2E with demo (with DAP as is today)
- [ ] get E2E with demo (with OSS, not on high priority but is a "nice to have")
R&D Boost Progress: The following should be used as a reference to pick up where I left off
- WIP PR: https://github.com/cyberark/secrets-provider-for-k8s/pull/81
- Demo script references an RDS instance that has been removed so must create and deploy a Postgres DB to Openshift
- There currently is a problem tagging and pushing
demo-tag
. Doing so manually is successful
docker tag demo-app:1.1.0 docker-registry-default.openshift-311.itci.conjur.net/test-app-5-74cbd079-0/demo-app
docker push docker-registry-default.openshift-311.itci.conjur.net/test-app-5-74cbd079-0/demo-app
but unsuccessful in code..
You can port forward
oc port-forward service/test-app-secretless 8080:8080
curl -i -d @- -H "Content-Type: application/json" localhost:8080/pet \
<< EOF
{
"name": "My Special Pet Name"
}
EOF
curl -i localhost:8080/pet