https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# extensions
a
This message was deleted.
l
seems the issue is similar to the above thread https://rancher-users.slack.com/archives/C04PPGWAWNR/p1727712074667999 @billions-vase-14972 can you please help me out with the solution.
s
Can you confirm your rancher container/s can reach out to the repo (shell in and curl from one of them)?
l
yes it is able to
s
Is the index.yaml from the error reachable though? That will be the helm repo that contains the charts that reference your image
l
no. pinging the IP gives destination host unrechable
I have generated the ECI using this command: 
yarn publish-pkgs -c -p -r $<http://docker.io|docker.io> -o ${IMAGE_NAMESPACE} -i ${IMAGE_PREFIX}
This added the image in docker.io I am installing the image using
not sure where the IP is getting picked from
s
interesting. i think @billions-vase-14972 might be able to assist further. haven't dug into this process before, but looking at the text it seems the image is bundled into a local helm repo. there'll be a deployment in the upstream cluster that should be serving the repo's yaml but isn't. that process is really intended for air-gapped environments though. is that a restriction or can the standard publish to github/gitlab process also work for you?
l
usually we dont prefer to keep public git repos. for dev purpose, we keep repos private. while I was going through this doc, I came across the note
Copy code
Note: Currently, we only support publishing Extension Helm charts into a public Github repository, if you inted to deploy an extension from a private repository/registry, we recommend utilizing the Extension Catalog Image method.
so we went ahead with ECI way.
b
There are a few things to check here. • First you shouldn't need the 
<http://docker.io|docker.io>
prefix to your image name when building or importing, unless your 
system-default-registry
is set to something other than the default or you are storing this somewhere other than dockerhub. • Check the service endpoint that is created when you import the ECI ◦ This would be within the 
cattle-ui-plugin-system
namespace • Ensure the deployment is running and the index.yaml is accessible from within the container I was able to import your image as: 
portworx/px-rancher-extension:0.1.0
- the cluster repo is properly connected and I see the extension within my available list. I'm unable to install it due to the 
<http://catalog.cattle.io/kube-version|catalog.cattle.io/kube-version>: '>= 1.16.0-0 < 1.29.0-0'
annotation set on the extension. As long as your kube version is less than 1.29 you should be able to install it.
👍 1
l
not sure what am I doing wrong here! @billions-vase-14972 for me its always failing with the similar error
Screen Recording 2024-10-29 at 6.55.51 PM.mov
s
i think we've already confirmed the second part of 3 (repo yaml unreachable from within container)
l
the service is running but the deployment is not
Copy code
root@ip-10-13-88-201:~# kubectl -n cattle-ui-plugin-system get svc
NAME                       TYPE        CLUSTER-IP    EXTERNAL-IP   PORT(S)    AGE
px-rancher-extension-svc   ClusterIP   10.43.40.15   <none>        8080/TCP   12m
root@ip-10-13-88-201:~# kubectl -n cattle-ui-plugin-system get deploy -o wide
NAME                   READY   UP-TO-DATE   AVAILABLE   AGE   CONTAINERS    IMAGES                                SELECTOR
px-rancher-extension   0/1     1            0           13m   container-0   portworx/px-rancher-extension:0.1.0   <http://catalog.cattle.io/ui-extensions-catalog-image=px-rancher-extension|catalog.cattle.io/ui-extensions-catalog-image=px-rancher-extension>
root@ip-10-13-88-201:~# kubectl -n cattle-ui-plugin-system get pods
NAME                                    READY   STATUS             RESTARTS        AGE
px-rancher-extension-5b7b47cbcf-8ggsw   0/1     CrashLoopBackOff   7 (2m17s ago)   13m
this is the events for pod describe
b
Do you have a few minutes where you could walk me through your setup?
l
Thanks @billions-vase-14972. I'll check with our team and will revert back on this
b
Just catching up on this thread and noticed this: 
<http://catalog.cattle.io/kube-version|catalog.cattle.io/kube-version>: '>= 1.16.0-0 < 1.29.0-0'
@loud-cricket-41513 would it be possible to bump the upper bounds to kube-version 1.31 ?
l
yes @blue-agency-84818 just now I have updated it in this image 
portworx/px-rancher-extension:0.1.0
along with this, while debugging it with @billions-vase-14972 we found another issue. due to some of our dev environment issues, the deployment is not able to come up
so I am not able to install the plugin via ECI way. may be some issues with our dev environment. This week is a holidays week in India. So will check with my team on monday and will revert back on this.
b
Thanks. Keep us posted.
l
Hi Team, helm way worked for us. Now able to install the extension via helm from a public github repo. Have some doubts for the support on air-gapped clusters. for air-gapped, is ECI the only way to install a plugin or by forking our public repo to a private repo will work?
s
That would work, any git repo that's accessible by rancher should be fine. if auth is required the Apps / Repository would need creds
l
Great. Thanks for the clarification.
Hi Team, I was trying upgrade my extension for Rancher 2.10. I followed the provided doc and I published a new version with all required annotations. but i am hitting this error in the Extension Page.
my bad. there was a typo in annotation.
👍 2
Open in Slack
PreviousNext
Powered by