Closed liutao841204 closed 2 years ago
Please provide the information below:
安装完成后,接口一直404
same as you
Please provide the information below:
- Does your cluster have a default ingress class? If not, please provide the ingress class you want to use.
- How did you access the zadig-portal service?
I install with helm, remove ingress just use NodePort manually
@Mr-YYM As for now, you cannot use this way to access zadig system. In our ingress there are multiple ingress rules to ensure the system is working as expected. Simply removing the ingress and access the portal service directly will NOT work.
same as you, I install with helm too, use nginx-ingress I installed myself
初次安装, helm , 1.5.0, traefik ingress 主页无限闪屏无法点击 页面log:
vendor.2738da7701bd30ff9dbf.js:85 TypeError: Cannot read properties of undefined (reading 'name')
at s.<anonymous> (app.6f55cb830d573b1b754c.js:2)
at s.e._render (vendor.2738da7701bd30ff9dbf.js:85)
at s.mn.before (vendor.2738da7701bd30ff9dbf.js:85)
at mn.get (vendor.2738da7701bd30ff9dbf.js:85)
at new mn (vendor.2738da7701bd30ff9dbf.js:85)
at vendor.2738da7701bd30ff9dbf.js:85
at s.Mn.$mount (vendor.2738da7701bd30ff9dbf.js:85)
at s.Mn.$mount (vendor.2738da7701bd30ff9dbf.js:85)
at init (vendor.2738da7701bd30ff9dbf.js:85)
at vendor.2738da7701bd30ff9dbf.js:85
qe @ vendor.2738da7701bd30ff9dbf.js:85
vendor.2738da7701bd30ff9dbf.js:85 TypeError: Cannot read properties of undefined (reading 'name')
at s.<anonymous> (app.6f55cb830d573b1b754c.js:2)
at s.e._render (vendor.2738da7701bd30ff9dbf.js:85)
at s.mn.before (vendor.2738da7701bd30ff9dbf.js:85)
at mn.get (vendor.2738da7701bd30ff9dbf.js:85)
at mn.run (vendor.2738da7701bd30ff9dbf.js:85)
at fn (vendor.2738da7701bd30ff9dbf.js:85)
at Array.<anonymous> (vendor.2738da7701bd30ff9dbf.js:85)
at Xe (vendor.2738da7701bd30ff9dbf.js:85)
qe @ vendor.2738da7701bd30ff9dbf.js:85
app.6f55cb830d573b1b754c.js:1 cancel analytics request
在http://zadig.xxx.com/signin 和 http://zadig.xxx.com/v1/projects 间快速切换, 每秒四五次那种. 赔我显示器 :)
@edisonwd @fanlix I have fix this problem, please verify these three Ingress has been correct configured:
[root@k8s-master ingress]# kubectl get Ingress -n zadig
NAME CLASS HOSTS ADDRESS PORTS AGE
pe-main <none> * 10.108.238.231 80 14m
poetry <none> * 10.108.238.231 80 13m
services <none> * 10.108.238.231 80 16m
@edisonwd @fanlix I have fix this problem, please verify these three Ingress has been correct configured:
[root@k8s-master ingress]# kubectl get Ingress -n zadig NAME CLASS HOSTS ADDRESS PORTS AGE pe-main <none> * 10.108.238.231 80 14m poetry <none> * 10.108.238.231 80 13m services <none> * 10.108.238.231 80 16m
I do not understand how to configure ingress, I configured it according to following figure.
@Mr-YYM As for now, you cannot use this way to access zadig system. In our ingress there are multiple ingress rules to ensure the system is working as expected. Simply removing the ingress and access the portal service directly will NOT work.
@edisonwd As this answer said, there are multiple ingress rules to ensure the system is working as expected.. So you must configure Ingress sources.
you can use kubectl get Ingress
to check if you Ingress configure. If you have no Ingress Controller installed, you cannot add thetag.ingressController=false
param.
@Mr-YYM As for now, you cannot use this way to access zadig system. In our ingress there are multiple ingress rules to ensure the system is working as expected. Simply removing the ingress and access the portal service directly will NOT work.
@edisonwd As this answer said, there are multiple ingress rules to ensure the system is working as expected.. So you must configure Ingress sources.
you can use
kubectl get Ingress
to check if you Ingress configure. If you have no Ingress Controller installed, you cannot add thetag.ingressController=false
param.
I have installed nginx-ingress-controller myself
@edisonwd
what kubectl get Ingress -n [your_zadig_ns]
show
@edisonwd we have same problem. i use traefik, you use yourself's nginx-ingress
@Mr-YYM
NAME CLASS HOSTS ADDRESS PORTS AGE
services <none> zadig.xxx.fun 10.16.175.214 80 6h34m
pe-main <none> zadig.xxx.fun 10.16.175.214 80 6h34m
poetry <none> zadig.xxx.fun 10.16.175.214 80 6h34m
其中一个:
$ kb describe -n zadig ingress pe-main
Name: pe-main
Namespace: zadig
Address: 10.16.175.214
Default backend: default-http-backend:80 (<error: endpoints "default-http-backend" not found>)
Rules:
Host Path Backends
---- ---- --------
zadig.xxx.fun
/api/hub aslan:25000 (10.42.0.99:25000)
/ zadig-portal:80 (10.42.0.114:80)
Annotations: kubernetes.io/ingress.class: traefik
meta.helm.sh/release-name: zadig
meta.helm.sh/release-namespace: zadig
nginx.ingress.kubernetes.io/proxy-connect-timeout: 120
nginx.ingress.kubernetes.io/proxy-read-timeout: 3600
nginx.ingress.kubernetes.io/proxy-send-timeout: 3600
nginx.ingress.kubernetes.io/ssl-redirect: false
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal UPDATE 24s (x713 over 5h55m) nginx-ingress-controller Ingress zadig/pe-main
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
zadig zadig 6 2021-10-15 10:44:07.533567729 +0800 CST deployed zadig-1.5.0 1.5.0
@Mr-YYM
1、安装方式
helm upgrade --install zadig --namespace zadig koderover-chart/zadig --set endpoint.FQDN=ko.ad.com --set tags.ingressController=false --set ingress-nginx.controller.ingressClass=nginx --set mongodb.persistence.storageClass=longhorn --set minio.persistence.storageClass=longhorn
2、安装完成后打开url页面一直报错404
检查发现poetry日志存在404
我也遇到了,这么严重的问题居然20多天过去了没人答复
@zlfzy this issue have been resolved already. What do you mean by no response?
This issue will be marked as resolved since the original problem is resolved
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
zadig zadig 1 2021-11-22 11:21:50.193896699 +0800 CST deployed zadig-1.5.0 1.5.0
一个半月, 依然闪屏.
还把issue关了.
此项目,,,,,,,,,,, 放弃.
@edisonwd @fanlix I have fix this problem, please verify these three Ingress has been correct configured:
[root@k8s-master ingress]# kubectl get Ingress -n zadig NAME CLASS HOSTS ADDRESS PORTS AGE pe-main <none> * 10.108.238.231 80 14m poetry <none> * 10.108.238.231 80 13m services <none> * 10.108.238.231 80 16m
@fanlix The fix to this problem has already been proposed. The resolver even mentioned you to make sure you get the solution.
我看到有2人已经把答案发在了这个issue里面,都是为了你的情况定制的,且在第二人回复后你完全没有任何回应。建议你看一下尝试后再给出回复。
Ingress is a necessary resource, and ingress-controller can use the ingress-controller that Zadig comes with or already in the cluster.
If you want to use the ingress-controller that comes with Zadig, you can use the ingress default configuration when installing with helm, or explicitly specify tags.ingressController=true
and ingress-nginx.controller.ingressClass=zadig-nginx
.
If you want to use the existing ingress-controller in the cluster, you can use kubectl get ingressclasses
or check ingress-controller deployment first, and then use kubectl -n <NAMESPACE OF INGRESS CONTROLLER DEPLOYMENT> get deployment <NAME OF INGRESS CONTROLLER> -o yaml | grep ingress-class
to query ingressClass, then install with helm by explicitly specifying tags.ingressController=false
and ingress-nginx.controller.ingressClass=<INGRESS CLASS>
.
目前的可用方法, 后人可能用到:
我使用如下命令进行安装: helm upgrade --install zadig --namespace zadig koderover-chart/zadig --version=1.1.0 \ --set endpoint.type=IP \ --set endpoint.IP=192.168.10.100 \ --set tags.ingressController=false \ --set tags.minio=fals
安装完成后,修改了 zadig-portal服务端口为30000,然后打开浏览器登录,发现界面一直在自动刷新