search

SAP / jenkins-library

Jenkins shared library for Continuous Delivery pipelines.
https://www.project-piper.io
Apache License 2.0
779 stars 589 forks source link

`helmExecute` - support multiple source repositories #4873

Closed mpern closed 10 hours ago

mpern commented 6 months ago

To ensure reproducible deployments with helm chart repositories during CD, you need to run helm dependencies build to ensure to use the charts as defined in the Chart.lock file.

https://helm.sh/docs/helm/helm_dependency_build/

To use build, you need to register the chart repository beforehand, otherwise it is rejected for security reasons (see helm/helm/issues/8036 for details).

At the moment helmExecute only supports a single chart repository (sourceRepository* parameters) which is not enough for more complex deployments which can depend on multiple repositories.

mpern commented 6 months ago

on a related note:

Can someone please give clear guidance on when to use helmExecute and/or kuberentesDeploy?

both commands have a big overlap in functionality (both support helm3) but don't support the same use caases / behave slightly differently. :(

github-actions[bot] commented 4 months ago

Thank you for your contribution! This issue is stale because it has been open 60 days with no activity. In order to keep it open, please remove stale label or add a comment within the next 10 days. If you need a Piper team member to remove the stale label make sure to add @SAP/jenkins-library-team to your comment.

loewenstein commented 4 months ago

@anilkeshav27 this sound's like a reasonable request and also the ask for guidance is.

I'd even go as far as stating that the Piper team should consider adding a helmBuild step for the build stage to include instead of relying on the defaults of helmExecute.

github-actions[bot] commented 2 months ago

Thank you for your contribution! This issue is stale because it has been open 60 days with no activity. In order to keep it open, please remove stale label or add a comment within the next 10 days. If you need a Piper team member to remove the stale label make sure to add @SAP/jenkins-library-team to your comment.

loewenstein commented 2 months ago

@anilkeshav27 I don't think this should be marked stale.

github-actions[bot] commented 1 week ago

Thank you for your contribution! This issue is stale because it has been open 60 days with no activity. In order to keep it open, please remove stale label or add a comment within the next 10 days. If you need a Piper team member to remove the stale label make sure to add @SAP/jenkins-library-team to your comment.

github-actions[bot] commented 10 hours ago

Issue got stale and no further activity happened. It has automatically been closed. Please re-open in case you still consider it relevant.