Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Customise how often requests are made to repos to check for updates to Helm charts #3304

Open
Makeshift opened this issue Nov 4, 2024 · 1 comment
Labels
impact/reliability Something that feels unreliable or flaky kind/enhancement Improvements or new features

Comments

@Makeshift
Copy link

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

When iterating and deploying a Pulumi project rapidly, one can run into rate limits enforced by third-party repositories:

kubernetes:helm.sh/v3:Release (karpenter-controller):
    error: kubernetes:helm.sh/v3:Release resource 'karpenter-controller': property chart value {oci://public.ecr.aws/karpenter/karpenter} has a problem: GET "https://public.ecr.aws/v2/karpenter/karpenter/tags/list?last=...": unexpected status code 429: toomanyrequests: Rate exceeded; check the chart name and repository configuration.

This feature request is for an option to cache the Helm chart (or the metadata for the Helm chart, unsure which one is causing the limit to be hit), and to introduce an option that has the helm.Release resource use this cached data for a user-defined period of time before attempting to update it.

Affected area/feature

@Makeshift Makeshift added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team labels Nov 4, 2024
@blampe blampe added impact/reliability Something that feels unreliable or flaky and removed needs-triage Needs attention from the triage team labels Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact/reliability Something that feels unreliable or flaky kind/enhancement Improvements or new features
Projects
None yet
Development

No branches or pull requests

2 participants