Migrate secrets provider repo to use the helm chart for deploying conjur in automation about kubernetes-conjur-deploy HOT 4 OPEN

@izgeri before we will start to work on this task, we will share our thoughts how to implement it and where, Thanks for your great inputs.

from kubernetes-conjur-deploy.

@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.

from kubernetes-conjur-deploy.

@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?

from kubernetes-conjur-deploy.

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

from kubernetes-conjur-deploy.