-
Notifications
You must be signed in to change notification settings - Fork 187
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
ECR: helm charts do not pull if from the root of the repository #951
Comments
Also I couldn't find any examples (anywhere on the web really) of someone using flux for private ECR helm repositories. What is the exact format of the helm release and repo object that I would expect to work? |
In your hemRepository, the url should be |
It still does not work with the root path. I'm looking around and found others having issues with ECR. Is there a recommended setup? |
Here is the debug log message I get
However I have verified that the service account for the source-controller has a role attached to it, and I get no error messages about being unable to authenticate against ECR. |
can you verify that the policy attached to the role gives you read permission to all your repositories? |
After may attempts to get This is validated by looking at how other people are using ECR and noticing they all have a |
thanks for the issue. Can you post the output of |
To clarify, it is working now because I moved the ECR repository from
|
I managed to reproduce this using our OCI integration test infra in https://github.com/fluxcd/pkg/tree/main/oci/tests/integration . HelmRepo: apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmRepository
metadata:
name: demo
namespace: default
spec:
type: "oci"
interval: 1m0s
provider: aws
url: oci://1234567890.dkr.ecr.us-east-2.amazonaws.com HelmChart: apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmChart
metadata:
name: demo
namespace: default
spec:
interval: 1m
chart: demo
reconcileStrategy: ChartVersion
sourceRef:
kind: HelmRepository
name: demo
version: "0.1.0" The failure is originating from helm registry client where it calls Here's the error, same as the one pasted above:
0.1.0 is the chart version that I used. |
I did further testing for this and found out that the issue was in the contextual login. |
Proof I can pull from the helm CLI.
Helm release Object
Relevant error logs from the source controller
Current source controller image
Strange part is "123123123.dkr.ecr.us-west-2.amazonaws.com/trino/trino:1.1.5: not found". Should that be only one
trino
?The text was updated successfully, but these errors were encountered: