You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@eladkug should this issue be moved to the secrets-provider repo?
To be clear, I am not suggesting we add a helm chart / OSS flow to this project (k8s-conjur-deploy) - I would either suggest you leverage our script to deploy Conjur OSS via the helm chart here in your own project, or we create a central CI utility project that can host tooling like this that we use in multiple pipelines (eg to deploy Conjur OSS to K8s, to deploy DAP to AWS, etc)
I have a slight preference to you copying our bash into your project vs creating a central pipeline-utils repo, because I don't have a clear vision for the structure of that repo and there's a high risk of it becoming a junk drawer. Either way, no changes would be made to this project.
@izgeri we are beginning our work in the Secrets Provider deploying the Conjur OSS via Helm. I want to understand a bit why we don't want to add the ability to deploy Conjur via Helm in this repo (k8s-conjur-deploy) for the OSS flow?
I'll let @diverdane weigh in on whether it would be useful to have any helper scripts / utils in this repo for deploying / configuring Conjur OSS in K8s - I know this is something he's been working on lately
Tovli
changed the title
Migrate secrets provider repo to use the helm chart
Migrate secrets provider repo to use the helm chart for deploying conjur in automation
May 10, 2021
Need to add support for OSS with helm chart.
@izgeri have an e2e test using the helm chart and secretless here (in a github action): https://github.com/cyberark/conjur-oss-suite-release/blob/master/.github/workflows/e2e-tests.yml .
For now our secrets provider repo will continue to work off of a branch of k8s-deploy.
DOD:
The text was updated successfully, but these errors were encountered: