Open rafaeljesus opened 2 years ago
Hi there,
I have a pipeline with parallel steps, in which I need to deploy helm charts in parallel [1]
The problem I am facing is, apparently the helm step always run kubectl config use-context "<MY-CONTEXT>" https://github.com/codefresh-io/steps/blob/808b525d6cfb2c09774a4180de6c81afe342c6ba/graduated/helm/lib/EntrypointScriptBuilder.py#L179
kubectl config use-context "<MY-CONTEXT>"
And since volumes are shared, it fails with the following error:
error: open /codefresh/volume/sensitive/.kube/config.lock: file exists
I think one way of solving dealing with this is to expose a new field skip_kube_config_init: true|false
skip_kube_config_init: true|false
Thoughts?
[1]
Hi there,
I have a pipeline with parallel steps, in which I need to deploy helm charts in parallel [1]
The problem I am facing is, apparently the helm step always run
kubectl config use-context "<MY-CONTEXT>"https://github.com/codefresh-io/steps/blob/808b525d6cfb2c09774a4180de6c81afe342c6ba/graduated/helm/lib/EntrypointScriptBuilder.py#L179And since volumes are shared, it fails with the following error:
I think one way of solving dealing with this is to expose a new field
skip_kube_config_init: true|falseThoughts?
[1]