helm: Helm v3.7.0 OCI Helm push to ecr gives 404 Not found
I was trying to use the OCI chart repo push with the new 3.7 release, and keep getting below error, repository exist.
Error: failed commit on ref "manifest-sha256:917752d9a5d35b444079a0179f18a17babe5264248961f86a6e07250c0081833": unexpected status: 404 Not Found
Output of helm version: 3.7.0
Output of kubectl version: NA
Cloud Provider/Platform (AKS, GKE, Minikube etc.): EKS
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 18 (6 by maintainers)
Do not append a repository name or a tag. Use the following:
both the repository name and tag are discovered from the chart name and version.
No. As this is experimental code, things can change in a breaking manner.
Repository names and tags are no longer modifiable by the user. This matches the same workflow with chart repositories, where the name and the version are provided by the chart. That way the user only has to provide the repository name and the name of the chart they wish to fetch in the form
helm pull bitnami/wordpress.Please see https://github.com/helm/community/blob/main/hips/hip-0006.md for more details. If you have feedback on the HIP, please feel free to discuss it on the mailing list, or submit an alternative proposal.
@bytebae certain container registry services require you to create the repo namesapce ahead of time. Let’s add some docs on this before moving Helm OCI out of experimental. Moving to milestone.
While I can understand the reasoning behind this change, this is not how it should have been implemented. The experimental feature is there exactly for this: to experiment breaking changes. We had a specific behaviour in the experimental version that was used by a lot of people and people seemed to be relatively happy about it (at least I was). Now, you completely changed the behaviour and merged it straight to master/prod with no one from the community testing the new behaviour and giving feedback in a newer experimental version all the while giving the excuse that the feature was previously experimental…What’s the point of the experimental commands then?