secrets-provider-for-k8s
secrets-provider-for-k8s copied to clipboard
cyberark
Cyberark secrets provider for k8s
For the M1 push to file feature the Secrets provider will use Kubernetes annotations to list the secrets that will be retrieved from Conjur. When configured for push to file,...
## Description Review the test framework being used in the Secrets Provider project. Identify what tests they run (unit, integration, e2e) and how each are set up. The outcome of...
Our tests were written in bash and moving to bdd may solve us several problems : 1. Analyse the results with jenkins is not easy 2. Reduce our time while...
**Feature Overview & Customer Need** We would like to increase the amount of secrets supported by Secret provider. Secret provider should support in minimum 550 secrets as secrets can be...
We have several items marked as high operational risks in our blackduck scan and we should figure out why (see image) After speaking with Ori from Sec team, he mentioned...
Our pipeline currently builds a helm chart as part of the build pipeline. We now want to be able to push packaged helm chart to the helm-charts repository as part...
This card is a continuation of the previous effort, [deploying a local dev env](https://github.com/cyberark/secrets-provider-for-k8s/commit/a1b09475db7b51fa0aa1ec2364284e4b007997ac). The previous effort allowed a dev to deploy a local k8s cluster and does not support...
Currently the main Dockerfile suffers from the following problems: - [ ] No .dockerignore - Meaning ALL files and folders are part of the Dockerfile context (It can't be overestimated,...
Currently the integration tests in Jenkins takes about an hour to run. Need investigation why it takes so long to run the tests on secrets provider. The magnitude of the...
We need to introduce HELM into our technical skills. We want to refactor the k8s secrets integration tests to deploy using HELM so it will be easier to manage -...
