Open zhengyansheng opened 5 days ago
➜ ~ k get pods |grep portal-deployment portal-deployment-65b6468fb7-6x5sf 1/1 Running 1 (4h31m ago) 4h32m portal-deployment-65b6468fb7-kwk64 1/1 Running 0 9h
Hi @zhengyansheng
Sometimes portal will take a lot of resources to build, since it runs webpack on runtime to accomodate for all different configurations.
https://github.com/uc-cdis/gen3-helm/blob/master/docs/portal/prebuild-portal.md
Can you try prebuilding your portal image instead and see if that helps?
If this helps, then most likely we need to test that your portal pods have connectivity to gather all configurations and does not get these errors:
# Browser access failed (try chrome/firefox, but not )
The connection has timed out
An error occurred during a connection to gen3.wcrcnet.cn.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web.
Also make sure it has enough resources to build webpack, sometimes we've seen adding more CPU and memory has helped.
I recommend going the prebuilding of portal route if you can get that to work, as you can decrease resources for portal needed then dramatically, as then it's just an nginx container serving static files.
use gen3-helm install in k8s cluster