That sounds great indeed ! Gonna take a deeper look asap.
Regards JB Le 9 oct. 2018 à 13:41, à 13:41, Antonin Stefanutti <anto...@stefanutti.fr> a écrit: >Hi Riccardo, > >This looks very promising! I think having a Web UI for Camel-K would be >very valuable. > >Here are my quick feedback: >- It’d be great to have the UI self-hosted. For it to work while >avoiding to configure CORS on the API server, it is possible to proxy >the communication to the API server and use in-cluster client config to >connect to it. >- It is possible to use OAuth 2 server metadata to discover OAuth >endpoints, as documented in [1] and [2]. >- Creating an OAuth client generally requires cluster-admin permission >and it's possible to use a service account as OAuth client to alleviate >that requirement [3]. > >[1] https://tools.ietf.org/id/draft-ietf-oauth-discovery-08.html >[2] >https://docs.okd.io/latest/architecture/additional_concepts/authentication.html#oauth-server-metadata >[3] >https://docs.openshift.com/container-platform/3.10/architecture/additional_concepts/authentication.html#service-accounts-as-oauth-clients > >Antonin > >> On 9 Oct 2018, at 09:15, Riccardo Forina <ricca...@forina.eu> wrote: >> >> Hello everybody, >> >> in the last few days, I have been working on a GUI for camel-k, for a >few reasons: >> - I know nothing about Camel, so this seemed a good way to test the >water >> - Nicola asked me if I could do it :D >> >> The main, and only, goal was to edit a custom resource and save it. >Since to do that I had to figure out how to talk with the server, I >added also a custom resource definitions "explorer" (it's just a list >of CRDs really...). >> >> This is as POC as it gets, so don't expect to find it particularly >useful (well the editing part works, so I guess it's useful if you need >that!). >> >> I'd like to know what you guys think about this and if it can be >useful for the project. >> >> The code's here https://github.com/riccardo-forina/camel-k-ui and you >can see a demo here >https://drive.google.com/open?id=1OzDPGdAEtU8PajZxJY5HKXQ1OyrH6s79 >> >> About the technical details, it's a React app bootstrapped with >create-react-app (the typescript version) and with 2 external >dependencies: >> - react-patternfly (version 3) >> - monaco-editor, which is the editor component used by Visual Studio >Code >> >> If you want to test it out locally, the process is: >> $ yarn >> $ yarn start >> $ point a browser to http://localhost:3000 >> >> You then need to add a new OAuth client to the server. In the >README.md there is a copy-pastable snippet to create one, already set >up to work with the app running locally on the default port. >> >> Cheers, >> Riccardo
