Angular Universal SSR kubernetes BrowserSync console errors

Viewed 26

Angular Universal application running in development keeps throwing a console error related to BrowserSync API

console error related to browserSync API

It seems Angular SSR makes these calls automatically, and there's really no way to configure the behaviour of the framework to modify the BrowserSync API calls.

My Angular Universal application is running in a local docker-desktop kubernetes cluster. It uses the following Ingress resource to route traffic to mydomain.com (that maps to localhost in the hosts file of my local workstation)

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: ingress-srv
  annotations:
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/use-regex: "true"
spec:
  rules:
    - host: mydomain.com
      http:
        paths:
          - path: /api/serviceA
            pathType: Prefix
            backend:
              service:
                name: service-a-srv
                port:
                  number: 3000
          - path: /api/serviceB
            pathType: Prefix
            backend:
              service:
                name: service-b-srv
                port:
                  number: 3001
          - path: /?(.*)
            pathType: Prefix
            backend:
              service:
                name: web-client-srv
                port:
                  number: 4200

ServiceA and ServiceB are both clusterIP services that point to NodeJS apps running in simple kubernetes pods. There are no reverse proxies in my configuration other than the nginx-ingress controller that uses this Ingress resource.

What is this reason for this CONNECTION_REFUSED error?

How can I set up Angular SSR with Kubernetes so that these HTTP calls from the framework to BrowserSync API work as expected?

0 Answers
Related