KUR8 icon indicating copy to clipboard operation
KUR8 copied to clipboard

kur8 not working - latest version

Open MatanAmoyal opened this issue 3 years ago • 3 comments

Hey

i tried to install kur8 using the you installation guide (also tried to change the service to be Nodeport) but the UI not really loading. I get just white screen (http code 200). (chrome, firefox and safari)

I tried to point the service to the pod with port 3000 and port 3068 (as i saw in logs). no errors in logs..

installation path: https://github.com/oslabs-beta/Kur8/blob/dev/infra/k8s/kur8-depl.yaml https://github.com/oslabs-beta/Kur8/blob/dev/infra/k8s/fabric8-rbac.yaml

➜ ~ curl -o /dev/null -k -s -w '%{http_code}\n' http://10.187.84.10:30771/ 200

image

logs:

[email protected] dev concurrently "cross-env NODE_ENV=development webpack serve --hot --open" "cross-env NODE_ENV=development nodemon ./server/index.js" [1] [nodemon] 2.0.12 [1] [nodemon] to restart at any time, enter rs [1] [nodemon] watching path(s): . [1] [nodemon] watching extensions: js,mjs,json [1] [nodemon] starting node ./server/index.js [1] jj [1] Listening on port: 3000 [0] ℹ 「wds」: Project is running at http://localhost:3068/ [0] ℹ 「wds」: webpack output is served from /build/ [0] ℹ 「wds」: Content not from webpack is served from /app/client/public [1] (node:61) [DEP0152] DeprecationWarning: Custom PerformanceEntry accessors are deprecated. Please use the detail property. [1] (Use node --trace-deprecation ... to show where the warning was created) [0] ℹ 「wdm」: asset bundle.js 4.85 MiB [emitted] (name: main) [0] asset index.html 233 bytes [emitted] [0] orphan modules 441 KiB [orphan] 279 modules [0] runtime modules 29.9 KiB 15 modules [0] modules by path ./node_modules/ 3.59 MiB [0] cacheable modules 3.58 MiB 689 modules [0] ./node_modules/webpack/hot/ sync nonrecursive ^./log$ 170 bytes [built] [code generated] [0] ./node_modules/moment/locale/ sync ^./.$ 3.21 KiB [optional] [built] [code generated] [0] modules by path ./client/src/ 241 KiB [0] modules by path ./client/src/components/ 158 KiB 23 modules [0] modules by path ./client/src/pages/ 33.2 KiB [0] modules by path ./client/src/pages/AlertsPage/.js 14.4 KiB 2 modules [0] modules by path ./client/src/pages/GetStartedPage/.js 10.5 KiB 2 modules [0] modules by path ./client/src/reducers/.js 29.8 KiB 7 modules [0] modules by path ./client/src/actions/.js 14.4 KiB 4 modules [0] modules by path ./client/src/.js 5.79 KiB 3 modules [0] webpack 5.47.1 compiled successfully in 26658 ms [0] ℹ 「wdm」: Compiled successfully.

MatanAmoyal avatar Aug 18 '21 05:08 MatanAmoyal

@MatanAmoyal, Interesting it seems like it should be running properly and has compiled correctly. Have you tried accessing it through: http://localhost:3068/ ? Let me know if that works for you?

jimmycngo avatar Aug 18 '21 14:08 jimmycngo

Hey so yes, with port-forward it is working, but with nodeport i get white screen. now it is not connecting to exist Prometheus with proxy errors. i tried to port-forward to the Prometheus and I successfully connected in browser on port 9090 to prometheus-ui. tried the solution with the ingress but not worked (Prometheus and kur8 are not in same namespace). Have any option to set the endpoint of the exist prometheus somewhere in the kur8 UI or in deployment command?

MatanAmoyal avatar Aug 19 '21 10:08 MatanAmoyal

Matan, KUR8 is currently set up to be accessed using a Cluster IP service. You could modify the deployment YAML files here. You can also adjust the PORT at which the service is looking for. The backend of KUR8 is on port 3000 whereas the front end is on 3068.

If you wanted to use nodeport, try adding that service to the deployment file.

jimmycngo avatar Aug 19 '21 14:08 jimmycngo