-
Notifications
You must be signed in to change notification settings - Fork 203
[helm-oci] ECR auth expires #787
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
Comments
Hello @nalbury, can you post Also can you post the source-controller logs as well please? |
As requested (had to redact some account IDs and some of the values as they're work specific): HelmRepostitory:
HelmRelease
Source Controller logs:
|
Thanks @nalbury we have identified the issue. Working on fixing this. |
Amazing thank you! |
We'll probably have to use @souleb's fork of Helm until this gets merged: helm/helm#11086 |
I have tested the fix with the following scenarios
@nalbury do you have the possibility to test the fix? See #799 |
Yup deployed an image built from your branch this morning. Should be able to verify this evening once the currently loaded token expires. |
While attempting to set up ECR as an OCI chart repo, we followed the recommended pattern here to configure a Kube secret with the required registry credentials for the OCI repo, but noticed that the source controller only seems to fetch this secret once on boot. This unfortunately means that once the ECR token expires, the source controller needs to be restarted before authentication will work again and the repo/charts can be reconciled.
Example of the state post expiration:
I know the recommended pattern linked above is from the documentation for the image automation controllers, so wondering if the source-controller is supposed to operate in the same way? It was mentioned here that some caching may be at play.
The text was updated successfully, but these errors were encountered: