[
https://issues.apache.org/jira/browse/YUNIKORN-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Coric updated YUNIKORN-2606:
----------------------------------
Description:
-We need a link to the external application that will display logs and more
details about the application or the pod itself.-
-External URLs can be defined in the form of a string template that can be set
as an env variable.-
-If the variable is present on build time, the Logs link will be visible on the
UI.-
To minimize changes in the YuniKorn itself and enable maximal customization and
easy connection with the YuniKorn History Server (YHS) that is being developed,
the easiest solution would be to add externally loaded component by using
module federation. Components will be served by the YHS server (changes on YHS
endpoints would reflect in web components as well) and loaded in YuniKorn web
with Module Federation.
This ticket should add the required configuration for loading a custom module
that will be enabled through the env variables. If env is not set, YuniKorn
will work as usual (no changes to the default behavior)
!image-2024-05-07-18-25-08-070.png|width=1240,height=647!
was:
-We need a link to the external application that will display logs and more
details about the application or the pod itself.-
-External URLs can be defined in the form of a string template that can be set
as an env variable.-
-If the variable is present on build time, the Logs link will be visible on the
UI.-
To minimize changes in the YuniKorn itself and enable maximal customization and
easy connection with the YuniKorn History Server (YHS) that is being developed,
the easiest solution would be to add externally loaded component by using
module federation. Components will be served by the YHS server (changes on YHS
endpoints would reflect in web components as well) and loaded in YuniKorn web
with Module Federation.
This ticket should add required configuration for loading custom module that
will be enabled through the env variables.
!image-2024-05-07-18-25-08-070.png|width=1240,height=647!
> Implement env variable (on build time) for to use Module Federation for
> loading custom sidebar component
> --------------------------------------------------------------------------------------------------------
>
> Key: YUNIKORN-2606
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2606
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: webapp
> Reporter: Denis Coric
> Assignee: Denis Coric
> Priority: Major
> Attachments: image-2024-05-07-18-25-08-070.png
>
>
> -We need a link to the external application that will display logs and more
> details about the application or the pod itself.-
> -External URLs can be defined in the form of a string template that can be
> set as an env variable.-
> -If the variable is present on build time, the Logs link will be visible on
> the UI.-
> To minimize changes in the YuniKorn itself and enable maximal customization
> and easy connection with the YuniKorn History Server (YHS) that is being
> developed, the easiest solution would be to add externally loaded component
> by using module federation. Components will be served by the YHS server
> (changes on YHS endpoints would reflect in web components as well) and loaded
> in YuniKorn web with Module Federation.
> This ticket should add the required configuration for loading a custom module
> that will be enabled through the env variables. If env is not set, YuniKorn
> will work as usual (no changes to the default behavior)
> !image-2024-05-07-18-25-08-070.png|width=1240,height=647!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
