search

vmware-tanzu / kubeapps

A web-based UI for deploying and managing applications in Kubernetes clusters
Other
4.95k stars 707 forks source link

kubeapps Pacakage repository Not working with OCI based harbor artifacts #7862

Open vijimgowda opened 3 months ago

vijimgowda commented 3 months ago

Summary kubeapps not able to sync charts from package repository for OCI based charts steps followed

pushed helm chart to harbor ( stored as OCI ) Goto add Package Repository Add OCI harbor "URL" select "Packaging Format" as "Helm Charts" selected "Scope" as Namespaced repository (using the "$namespace" namespace) Selected "Package Storage Type" "OCI Registry" Selected "Authentication" "Basic Auth" ( Username and Password ) Added "Filtering" "List of repository" ( my oci repository name ) submitted "INSTALL REPOSITORY" Package Repository successfully added and appeared in "Namespaced Repositories:"

Issue :

Not visible in Catalog option and upgrade option not shown in Application Tile

upgrade_button_disabled catalog_issue
vijimgowda commented 2 months ago

Any update on this issue

vijimgowda commented 2 months ago

4670 Team help us to resolve above issue

beltran-rubo commented 2 months ago

This is not supported in Kubeapps right now. This was implemented for Bitnami Helm charts in DockerHub in a previous version:

Kubeapps v2.9.0 (chart version 14.0.1) is a minor release that fixes some bugs and introduces working support for listing a catalog of apps when your charts are stored in an OCI registry (without having to list them manually). Specifically, this release supports registries on dockerhub, such as Bitnami's "oci://registry-1.dockerhub.io/bitnamicharts". This feature is behind a flag ociCatalog.enabled=true until we support more registries.