Allure-Docker-Service-UI ERR_ABORTED 404

[fescobar]

Allure-Docker-Service-UI ERR_ABORTED 404

[fescobar]

Hi @semihural
Seems to be Kubernetes is not prepared to serve SINGLE PAGE APPLICATIONS, for that reason you should add another path / to your ingress like in the example: https://github.com/fescobar/allure-docker-service-examples/blob/master/allure-docker-kubernetes-example/allure-ingress-service-load-balancer.yml#L29

        paths:
          - path: /allure-api/?(.*)
            backend:
              serviceName: allure-service-load-balancer
              servicePort: 6060
          # Share your configuration if you have a better way to handle a static website
          - path: /allure-ui/?(.*)
            backend:
              serviceName: allure-service-load-balancer
              servicePort: 7070
          - path: /?(.*)
            backend:
              serviceName: allure-service-load-balancer
              servicePort: 7070

The same I will check this problem on this ticket: fescobar/allure-docker-service-ui#7

[semihural]

Hi @fescobar ,

Yeah it works like that.. But my main host serving another services actually. I mean xxx.net ı ve zalenium hub running which I suppose I can manage allure using same host with sub-path.. Can it be alternative solution that no need to add path:/

[fescobar]

@semihural I understand, but I think that is the way it works Kubernetes. It's not oriented to static web pages.