CODEWITHSUNDEEP
kuberneteskubernetes-ingressnginx-ingress
user3583252
user3583252

Reputation: 493

Kubernetes Ingress not loading static assets

I have a ReactJS front end, Spring boot backend app deployed on a baremetal Kubernetes cluster which is running Kubernetes Ingress and requests are proxied to it by HAProxy. When visiting the URL of the app, I can see it loads the index.html of the app but all other requests to static assets are not done properly.

The ingress resource of my app:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
namespace: app
name: app-ingress
annotations:
    kubernetes.io/ingress.class: "nginx"
    nginx.ingress.kubernetes.io/ssl-redirect: "false"
    nginx.ingress.kubernetes.io/rewrite-target: /$3
spec:
rules:
- host: devops
    http:
    paths:
    - path: /dev/app1(/|$)(.*)
        backend:
        serviceName: app1
        servicePort: 80

When inspecting the page which loads using Chrome Developer tools, I see that there are 6 outgoing calls to the static assets. The call that retrieves the index.html of the app completes succesfully but the calls that retrieve the static assets (ex: http://devops/dev/app1/static/js/4.2761693d.chunk.js) does not work properly as it retrieves the index.html page as well. (only the index.html page is served by all calls basically)

I had a feeling it is because of the nginx.ingress.kubernetes.io/rewrite-target annotation but removing it causes a 404 even on the index.html page.

I am using nginx ingress controller 0.25.1

EDIT:

This is the output when I exec into the container and run curl localhost:8080/dev/app1/static/js/4.2761693d.chunk.js (error fallback page)

enter image description here

This is the output when I run curl localhost:8080/tatic/js/4.2761693d.chunk.js (correctly loads the css)

enter image description here

Upvotes: 4

Views: 8923

Answers (3)

Darren Quadros
Darren Quadros

Reputation: 111

Im using kubernetes 1.25.2 along with Nginx-Ingress v2.4.1 https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/

Just us the below 2...the Path should have / at the end.

annotations: nginx.org/rewrites: "serviceName=app1-svc rewrite=/;serviceName=app2-svc rewrite=/"

spec: path: /app1/

below is my Ingress resource file manifest...

apiVersion: networking.k8s.io/v1 
kind: Ingress 
metadata:
  name: relouat-ingress
  namespace: relouat
  annotations:    
    #nginx.ingress.kubernetes.io/rewrite-target: /$2
     nginx.org/rewrites: "serviceName=app1-svc rewrite=/;serviceName=app2-svc rewrite=/"     
spec:
  ingressClassName: nginx  
  rules:
  - host: uat.relo.com
    http:
      paths:
      - backend:
          service:
            name: app1-svc
            port:
              number: 2041
        path: /app1/
        pathType: Prefix
      - backend:
          service:
            name: app2-svc
            port:
              number: 2042
        path: /app2/
        pathType: Prefix

Upvotes: 0

user3583252
user3583252

Reputation: 493

Somehow, when I change the rewrite annotation to this, it works:

nginx.ingress.kubernetes.io/rewrite-target: /$2

I didnt change anything else.

Now the application is accessible at devops/dev/app1/ (but it does not work without the / at the end)

I am not sure how this works. I had no logic behind it, I was just changing values in the ingress file to see if anything works.

Can someone explain why it works?

Upvotes: 1

Akin Ozer
Akin Ozer

Reputation: 991

You are most likely using rewrite target for wrong reasons. In this case all elements should start with /dev/app1 including inner calls. What you are doing is working for index page because you wrote it to have "/dev/app1" in before and ingress redirected it to "/" but inner call just called "/static/js/4.2761693d.chunk.js" . This caused the problem basically, because ingress didn't know the route therefore your service never get called to get the js file.

Upvotes: 0

Related Questions