Ingress SubPath Not Working.

[Sam-Sundar]

Hey Team,

I'm trying to upgrade from old version of MinIo to latest one and we found we had to make multiple changes,

    spec:
      containers:
      - args:
        - server
        - /storage
        - --console-address
        - :9001
        env:
        - name: MINIO_ROOT_USER
          value: minio
        - name: MINIO_ROOT_PASSWORD
          value: minio123
        #- name: MINIO_BROWSER_REDIRECT_URL
        #  value: https://onprem-test.development.apty.io
        image: minio/minio:latest
        imagePullPolicy: IfNotPresent
        name: minio
        ports:
        - containerPort: 9000
          name: api-port
          protocol: TCP
        - containerPort: 9001
          name: console-port
          protocol: TCP
        resources:

This is my svc definition

minio-api-service         NodePort    10.96.1.117   <none>        9000:31822/TCP                  29m
minio-service             NodePort    10.96.0.155   <none>        9001:31823/TCP                  38d

This is my ingress file

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  projectcontour.io/response-timeout: infinity
  name: https-ingress
  namespace: default
spec:
  rules:
  - host: onprem-test.development.apty.io
    http:
      paths:
      - backend:
          service:
            name: minio-service
            port:
              number: 9001
        path: /minio/
        pathType: Prefix
  tls:
  - hosts:
    - onprem-test.development.apty.io
    secretName: apty-onprem
status:
  loadBalancer: {}

When i try to hit /minio, it's not opening console

[harshavardhana]

You need to tell MinIO where is your console hosted at, leaving out MINIO_BROWSER_REDIRECT_URL won't work.

It should be

value: https://onprem-test.development.apty.io/minio

[Sam-Sundar]

Hey @harshavardhana,

I did try it as mentioned in here https://github.com/minio/minio#things-to-consider. But still no luck. PFB screenshot of my deployment file. Can you please let me know what i'm missing ?

[harshavardhana]

You need also use fairly recent MinIO.

[Sam-Sundar]

Hey @harshavardhana,

I'm on latest version of MinIO, used the latest tag from both docker and quay.io, still same .. No Luck..

[Sam-Sundar]

Also @harshavardhana,

With NodePort i'm able to access, just behind ingress getting this weird issue where favicon is loading, but the app is not. 😬

[harshavardhana]

I can reproduce the problem with docker-compose and nginx

[Sam-Sundar]

Thanks a lot @harshavardhana,

If possible, can you try to reproduce on Kubernetes and ingress ? Or with subpath on compose and Nginx.

Since, main domain will reach out to our app and /minio should reach minio. This used to work with 2021 July version, before the update to this UI version.
Also, there's the same bug reported by someone else

#1908

[dvaldivia]

your nginx config is missing a rewrite_rule you need to add rewrite ^/minio/(.*) /$1 break; to the console location directive

	location /minio {
            proxy_set_header Host $http_host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
            proxy_set_header X-NginX-Proxy true;

            # This is necessary to pass the correct IP to be hashed
            real_ip_header X-Real-IP;

            proxy_connect_timeout 300;
            
            # To support websocket
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
            
            chunked_transfer_encoding off;
            rewrite   ^/minio/(.*) /$1 break;
            proxy_pass http://console;
	}

[Sam-Sundar]

Hey,

We aren't using Nginx, we are using contour ingress and I don't think Nginx ingress also has something like rewrite_rules