You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: this is about Rancher Dashboard UI Extension not about Docker/Rancher desktop extension
We need $title, it should consist of following steps:
Enabling the Rancher Extensions support
Adding the rancher extension repository (when the extension is not shipped via official rancher channels)
Installing Epinio over Rancher via official Rancher App chart repo - a graphical wizard using questions.yml file.
Note: if E is installed via rancher the DEX and CORS are configured to accept also requests from rancher itself by using rancher internal variable global.cattle.url (populated automatically). If installing E out of rancher by helm CLI the needed value can set via --set rancher.url=https://<my-rancher-url flag.
Installing the Epinio extension from the extension repo
Usage of the Epinio extension within Rancher - where to find the E dashboard in Rancher, how to do auth (local+dex supported for now). The basic usage is identical with standalone Epinio UI, there will be just an extra rancher side bar present in addition.
with Improve landing experience when using ui extension ui#367 users will be able to install the ui extension, go to the epinio page and select a cluster to install epinio on (which takes them to the cluster's helm install wizard)
Note: this is about Rancher Dashboard UI Extension not about Docker/Rancher desktop extension
We need $title, it should consist of following steps:
Note: if E is installed via rancher the DEX and CORS are configured to accept also requests from rancher itself by using rancher internal variable
global.cattle.url
(populated automatically). If installing E out of rancher by helm CLI the needed value can set via--set rancher.url=https://<my-rancher-url
flag.Internal docu:
https://github.com/epinio/ui/blob/main/docs/developer/README.md#production-flow
Update: The idea is to follow existing Kubewarden documentation where the extension part is covered.
The text was updated successfully, but these errors were encountered: