-
Notifications
You must be signed in to change notification settings - Fork 702
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
GetAvailablePackageSummaries returns empty list from OCI Registry #7269
Comments
Also if you try to install helmchart using CLI:
It will snow From the flux side, all the resources are ok: # k get helmchart
NAME CHART VERSION SOURCE KIND SOURCE NAME AGE READY STATUS
default-podinfo podinfo 6.5.* HelmRepository podinfo 22m True pulled 'podinfo' chart with version '6.5.4'
podinfo podinfo 6.* HelmRepository podinfo 27m True pulled 'podinfo' chart with version '6.5.4'
# k get helmrepository
NAME URL AGE READY STATUS
podinfo oci://ghcr.io/stefanprodan/charts 27m True Helm repository is ready
# k get helmreleases
NAME AGE READY STATUS
podinfo 26m True Release reconciliation succeeded |
Thanks for filing the issue and providing information on how to repro it. I've been having a quick look at the issue and, yep, I can reproduce it. I'd say it is happening because of how Flux marks the repo as "ready" (source):
However, our logs show:
It seems we wrongly have assumed a "ready" state would eventually pop up:
I assume (not 100% sure, though) adding this scenario ("a HelmRepo not explicitly ready, but pointing to an OCI repo") here would make the trick:
|
Describe the bug
Catalog is empty when using FluxCD and OCI Registry.
To Reproduce
Steps to reproduce the behavior:
Install Kubeapps with FluxCD
Create:
Open Catalog, you'll get an empty list.
Request to
/apis/kubeappsapis.core.packages.v1alpha1.RepositoriesService/GetPackageRepositorySummaries
reutrns:
Expected behavior
Screenshots
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: