Open yuanminhui opened 9 months ago
Following the deployment guide, I stumbled over two steps that require/check the communication with the deployed services on k8s:
2.2 安装 Jupyterhub ... # 将 jupyterhub 服务暴露出来，使浏览器可以直接访问.拿到 token 之后，就可以关掉这个端口转发。 kubectl -n bioos port-forward --address 0.0.0.0 service/hub 8081:8081 打开浏览器访问：http://服务器IP/jupyterhub, 申请新 token. 2.4 安装 Bioos 服务 ... # 端口转发： kubectl -n ingress-nginx port-forward --address 0.0.0.0 service/ingress-nginx-controller 8888:80 ... 打开浏览器访问 http://服务器IP/workspace，至此完成 bioos 安装.
2.2 安装 Jupyterhub ...
# 将 jupyterhub 服务暴露出来，使浏览器可以直接访问.拿到 token 之后，就可以关掉这个端口转发。 kubectl -n bioos port-forward --address 0.0.0.0 service/hub 8081:8081
打开浏览器访问：http://服务器IP/jupyterhub, 申请新 token.
2.4 安装 Bioos 服务 ...
# 端口转发： kubectl -n ingress-nginx port-forward --address 0.0.0.0 service/ingress-nginx-controller 8888:80
... 打开浏览器访问 http://服务器IP/workspace，至此完成 bioos 安装.
Follow the deployment guide at https://bio-os.gitbook.io/userguide/bu-shu/getting-set-up/bu-shu-bioos or https://github.com/Bio-OS/helm-charts/blob/main/README.md.
Successful installation and interaction with k8s backend services.
Error status of bioos access is the same with jupyterhub access.
Describe the bug
Following the deployment guide, I stumbled over two steps that require/check the communication with the deployed services on k8s:
To Reproduce
Follow the deployment guide at https://bio-os.gitbook.io/userguide/bu-shu/getting-set-up/bu-shu-bioos or https://github.com/Bio-OS/helm-charts/blob/main/README.md.
Expected behavior
Successful installation and interaction with k8s backend services.
Screenshots
Error status of bioos access is the same with jupyterhub access.