zadig-portal keeps redirecting non-stop

[liutao841204]

我使用如下命令进行安装： 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，然后打开浏览器登录，发现界面一直在自动刷新

[jamsman94]

Please provide the information below:

1. Does your cluster have a default ingress class? If not, please provide the ingress class you want to use.
2. How did you access the zadig-portal service?

[zhangsir1211]

安装完成后，接口一直404

[Mr-YYM]

same as you

[Mr-YYM]

Please provide the information below:

1. Does your cluster have a default ingress class? If not, please provide the ingress class you want to use.
2. How did you access the zadig-portal service?

I install with helm, remove ingress just use NodePort manually

[jamsman94]

@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]

same as you, I install with helm too, use nginx-ingress I installed myself

[fanlix]

初次安装, 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

[fanlix]

在http://zadig.xxx.com/signin 和 http://zadig.xxx.com/v1/projects 间快速切换, 每秒四五次那种. 赔我显示器 :)

[Mr-YYM]

@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]

@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]

@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.

[edisonwd]

@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

[Mr-YYM]

@edisonwd

what kubectl get Ingress -n [your_zadig_ns] show

[fanlix]

@edisonwd we have same problem. i use traefik, you use yourself's nginx-ingress

@Mr-YYM

• 把ingress切换为IP方式是可以使用的.
• 三个ingress

  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

• 你说的已fixed版本是多少? 我目前用的helm chart:

  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

[zhangsir1211]

@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

[muicoder]

traefik的IngressRoute资源

ingress-for-services_traefik.yaml

```yaml apiVersion: traefik.containo.us/v1alpha1 kind: IngressRoute metadata: name: services labels: {{- include "zadig.labels" . | nindent 4 }} spec: entryPoints: - web routes: - kind: Rule match: HostRegexp(`{{required ".Values.endpoint.FQDN is required for FQDN" .Values.endpoint.FQDN}}`) && PathPrefix(`/api/aslan`) middlewares: - name: middleware-replace-path-to-api-zadig services: - name: aslan port: {{ include "zadig.microservice.aslan.port" . }} {{- if .Values.tags.enterprise }} - kind: Rule match: HostRegexp(`{{required ".Values.endpoint.FQDN is required for FQDN" .Values.endpoint.FQDN}}`) && PathPrefix(`/api/aslanx`) middlewares: - name: middleware-replace-path-to-api-zadig services: - name: aslanx port: {{ include "zadig.microservice.aslan-x.port" . }} {{- end }} - kind: Rule match: HostRegexp(`{{required ".Values.endpoint.FQDN is required for FQDN" .Values.endpoint.FQDN}}`) && PathPrefix(`/api/podexec`) middlewares: - name: middleware-replace-path-to-api-zadig services: - name: podexec port: {{ include "zadig.microservice.podexec.port" . }} --- apiVersion: traefik.containo.us/v1alpha1 kind: Middleware metadata: name: middleware-replace-path-to-api-zadig spec: replacePathRegex: regex: /api/([a-z]+[/|$]*)(.*) replacement: /api/$2 ```

ingress_traefik.yaml

```yaml apiVersion: traefik.containo.us/v1alpha1 kind: IngressRoute metadata: name: pe-main labels: {{- include "zadig.labels" . | nindent 4 }} spec: entryPoints: - web routes: - kind: Rule match: HostRegexp(`{{required ".Values.endpoint.FQDN is required for FQDN" .Values.endpoint.FQDN}}`) && PathPrefix(`/api/hub`) services: - name: aslan port: {{ include "zadig.microservice.aslan.port" . }} - kind: Rule match: HostRegexp(`{{required ".Values.endpoint.FQDN is required for FQDN" .Values.endpoint.FQDN}}`) && PathPrefix(`/`) services: - name: zadig-portal port: 80 {{- if .Values.tags.enterprise }} - kind: Rule match: HostRegexp(`{{required ".Values.endpoint.FQDN is required for FQDN" .Values.endpoint.FQDN}}`) && PathPrefix(`/zadig/`) services: - name: zadig-x-doc port: 80 - kind: Rule match: HostRegexp(`{{required ".Values.endpoint.FQDN is required for FQDN" .Values.endpoint.FQDN}}`) && PathPrefix(`/api/collie`) services: - name: collie-server port: 28080 - kind: Rule match: HostRegexp(`{{required ".Values.endpoint.FQDN is required for FQDN" .Values.endpoint.FQDN}}`) && PathPrefix(`/sonar/`) services: - name: sonarqube port: 80 {{- end }} ```

poetry-ingress_traefik.yaml

```yaml apiVersion: traefik.containo.us/v1alpha1 kind: IngressRoute metadata: name: poetry labels: {{- include "zadig.labels" . | nindent 4 }} spec: entryPoints: - web routes: - kind: Rule match: HostRegexp(`{{required ".Values.endpoint.FQDN is required for FQDN" .Values.endpoint.FQDN}}`) && PathPrefix(`/api/directory`) middlewares: - name: middleware-replace-path-to-directory-zadig services: - name: poetry port: {{ include "zadig.microservice.poetry.port" . }} --- apiVersion: traefik.containo.us/v1alpha1 kind: Middleware metadata: name: middleware-replace-path-to-directory-zadig spec: replacePathRegex: regex: /api/directory(/|$)(.*) replacement: /directory/$2 ```

[i0668]

我也遇到了，这么严重的问题居然20多天过去了没人答复

[jamsman94]

@zlfzy this issue have been resolved already. What do you mean by no response?

[jamsman94]

This issue will be marked as resolved since the original problem is resolved

[fanlix]

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关了. 此项目,,,,,,,,,,, 放弃.

[jamsman94]

@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里面，都是为了你的情况定制的，且在第二人回复后你完全没有任何回应。建议你看一下尝试后再给出回复。

[flyer103]

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> .

[fanlix]

• @edisonwd 说的是helm配置,这些文档里有写. 我也是正确配置的. 如果没配好首页都是404, 没机会闪.
  • 后面@flyer103 也是重复的文档已有内容.
• @muicoder 贴的是单独的traefik配置, 并不是fix了bug, 而是用IngressRoute重写了原来Ingress的功能.
  • 这种方法首页不会闪了(页面报了几个404), 能建项目体验.
• 我给@muicoder 点了个表情赞的. 但这不是我要的解决方法.
  • 希望是正确安装后,按照文档正确配置就能跑起来的. 如@flyer103 写的那样.

目前的可用方法, 后人可能用到:

• 使用IP方式
• 自己重写ingress, 参照@edisonwd 的例子.