This message was deleted.

The request url for

api/v1/namespaces/cattle-ui-plugin-system/services/<http:ui-plugin-operator:80/proxy/nutanix/0.2.1/plugin/nutanix-0.2.1.umd.min.js>

is indicating that the

ui-plugin-operator

was not able to cache the extension assets which is retrieved by the

endpoint

property within the extension chart file

<chart-dir>/templates/cr.yaml

. Wherever your extension chart and assets are housed, this location must be accessible by the operator. For reference, private repositories are not supported currently. You should also be able to check the logs of the

ui-plugin-operator

pod to get a sense of where the issue is stemming from. For more detailed info on the failure, you can turn on the debug feature within the operator chart.

Hello @billions-vase-14972 you give me a clue and i find the issue in you publish workflow despite you put the extensions in the github pages who is public you use a raw github link to the gh-pages branch in palce the pages url any way to fix it ??

The raw github link should work regardless when using the pages url as your repository url. As long as the files are actually publicly available (take the kubewarden-ui version 1.3.2 for example) then the operator can fetch these files. If it's possible, you can link me to your repository to help diagnose the issue.

the raw link was not working because repo is private for now , only pages part are public

Ah I see, unfortunately injecting the github page link from the workflow or even the

yarn publish-pkgs

script is not possible at the moment. However, you can use the extension catalog workflow to build an image that can be published to a private registry, then import the image as an extension catalog.

no problem, repo will be public soon don’t worry