-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Support chart replication to AWS ECR #16759
Comments
Could you provide your replication rule? |
Replication mode: Push based |
If you select OCI chart, these charts are treated with Artifact, so for resource only need select artifact. The error log from your first comment shows it tried to replicate non-OCI chart in chartmuseum, could you check whether put chart in the right place(it should not in chartmuseum)? |
I tried with the artifact as well but there is no replication. |
Any update on the above issue? |
Hi,did you push your chart by helm v3 to harbor and could you share your artifact page? |
Yes, pushed chart with helm v3. |
You could refer to above docs to check whether your OCI chart is ready. |
Hi |
Could ping me by slack channel: https://cloud-native.slack.com/archives/CC1E09J6S |
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days. |
Amazon released support for alternate media types in ECR manifests. They can support storing helm charts as OCI images.
See: aws/containers-roadmap#308 (comment)
I would like to be create replication rules for syncing charts between Harbor and ECR
Currently if I try to create a replication rule to push charts from Harbor to ECR, it gives the error
I tried with the artifact in the resource block but still got the same error. It only tries to replicate the Images, not the helm charts. Below are logs of the replication when resource as charts.
2022-04-27T05:22:45Z [INFO] [/controller/replication/transfer/chart/transfer.go:92]: client for source registry [type: harbor, URL: http://harbor-core:80, insecure: true] created
2022-04-27T05:22:45Z [ERROR] [/controller/replication/transfer/chart/transfer.go:98]: failed to create client for destination registry: the adapter doesn't implement the "ChartRegistry" interface
Can someone help with this, please?
The text was updated successfully, but these errors were encountered: