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
When kubernetes.core.helm is given the update_repo_cache: true option, the plugin runs helm repo update. This can be quite inefficient if a lot of repositories are defined.
Since the plugin has a reference to the repository in chart_ref, could it be possible to instead run helm repo update <repository>?
ISSUE TYPE
Feature Idea
COMPONENT NAME
kubernetes.core.helm
ADDITIONAL INFORMATION
I recently ran into an issue where helm installs using this plugin became extremely slow. After some debugging it turned out I had an old repository link which was not accessible from the current host. In this case its an easy fix on my side, but this change also benefits the execution speed of playbooks if a lot of repositories are defined.
SUMMARY
When kubernetes.core.helm is given the
update_repo_cache: true
option, the plugin runshelm repo update
. This can be quite inefficient if a lot of repositories are defined.Since the plugin has a reference to the repository in
chart_ref
, could it be possible to instead runhelm repo update <repository>
?ISSUE TYPE
COMPONENT NAME
kubernetes.core.helm
ADDITIONAL INFORMATION
I recently ran into an issue where helm installs using this plugin became extremely slow. After some debugging it turned out I had an old repository link which was not accessible from the current host. In this case its an easy fix on my side, but this change also benefits the execution speed of playbooks if a lot of repositories are defined.
The text was updated successfully, but these errors were encountered: