Minio-console does not work with AKS ingress. #2343

williamsun-hha · 2024-10-07T14:46:39Z

NOTE

If this case is urgent, please subscribe to Subnet so that our 24/7 support team may help you faster.

Minio-console does not work with AKS ingress controller

Expected Behavior

With ingress controller, Minio console URL should work normally but I got a 400 error.

Current Behavior

I deployed Minio to Azure AKS with helm. Operator (helm install
--namespace minio-operator
--create-namespace
minio-operator minio/operator) (k get all -n minio-operator
NAME READY STATUS RESTARTS AGE
pod/minio-operator-74dc88668d-86qxb 1/1 Running 0 11h
pod/minio-operator-74dc88668d-s6xgc 1/1 Running 0 11h
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/operator ClusterIP 10.0.29.110 4221/TCP 11h
service/sts ClusterIP 10.0.142.65 4223/TCP 11h
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/minio-operator 2/2 2 2 11h
NAME DESIRED CURRENT READY AGE
replicaset.apps/minio-operator-74dc88668d 2 2 2 11h). and Tenant (helm install --namespace tenant-ns
--create-namespace tenant minio/tenant), (k get all -n tenant-ns
NAME READY STATUS RESTARTS AGE
pod/myminio-pool-0-0 2/2 Running 0 11h
pod/myminio-pool-0-1 2/2 Running 0 11h
pod/myminio-pool-0-2 2/2 Running 0 11h
pod/myminio-pool-0-3 2/2 Running 0 11h
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/minio ClusterIP 10.0.153.222 443/TCP 11h
service/myminio-console ClusterIP 10.0.158.52 9443/TCP 11h
service/myminio-hl ClusterIP None 9000/TCP 11h
NAME READY AGE
statefulset.apps/myminio-pool-0 4/4 11h) . The deployment seems successful. But I am not able to connect to myminio-console with Azure approute NGINX ingress. Here is the ingress rule configured (http:
paths:

path: /
pathType: Prefix
backend:
service:
name: myminio-console
port:
number: 9443). Can you please point me to the right direction? Thank you very much for your help in advance! From this document (https://min.io/docs/minio/kubernetes/openshift/operations/install-deploy-manage/deploy-minio-tenant.html#create-tenant-connect-tenant), the deployment is successful

This is on the document (The *-console service corresponds to the MinIO Console. Administrators should use this service for accessing the MinIO Console and performing administrative operations on the MinIO Tenant.
). Thank you very much for your help!

Ingress controller is working normally since all of the other applications deployed are working normally. From the error code, it appears the console service does not work.

Possible Solution

If a work around to configure the ingress, that would be great while the issue being worked on.

Steps to Reproduce (for bugs)

With ingress controller, Minio console URL should work normally but I got a 400 error.

Current Behavior

I deployed Minio to Azure AKS with helm. Operator (helm install
--namespace minio-operator
--create-namespace
minio-operator minio/operator) (k get all -n minio-operator
NAME READY STATUS RESTARTS AGE
pod/minio-operator-74dc88668d-86qxb 1/1 Running 0 11h
pod/minio-operator-74dc88668d-s6xgc 1/1 Running 0 11h
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/operator ClusterIP 10.0.29.110 4221/TCP 11h
service/sts ClusterIP 10.0.142.65 4223/TCP 11h
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/minio-operator 2/2 2 2 11h
NAME DESIRED CURRENT READY AGE
replicaset.apps/minio-operator-74dc88668d 2 2 2 11h). and Tenant (helm install --namespace tenant-ns
--create-namespace tenant minio/tenant), (k get all -n tenant-ns
NAME READY STATUS RESTARTS AGE
pod/myminio-pool-0-0 2/2 Running 0 11h
pod/myminio-pool-0-1 2/2 Running 0 11h
pod/myminio-pool-0-2 2/2 Running 0 11h
pod/myminio-pool-0-3 2/2 Running 0 11h
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/minio ClusterIP 10.0.153.222 443/TCP 11h
service/myminio-console ClusterIP 10.0.158.52 9443/TCP 11h
service/myminio-hl ClusterIP None 9000/TCP 11h
NAME READY AGE
statefulset.apps/myminio-pool-0 4/4 11h) . The deployment seems successful. But I am not able to connect to myminio-console with Azure approute NGINX ingress. Here is the ingress rule configured (http:
paths:

path: /
pathType: Prefix
backend:
service:
name: myminio-console
port:
number: 9443). Can you please point me to the right direction? Thank you very much for your help in advance! From this document (https://min.io/docs/minio/kubernetes/openshift/operations/install-deploy-manage/deploy-minio-tenant.html#create-tenant-connect-tenant), the deployment is successful

This is on the document (The *-console service corresponds to the MinIO Console. Administrators should use this service for accessing the MinIO Console and performing administrative operations on the MinIO Tenant.
). Thank you very much for your help!

Ingress controller is working normally since all of the other applications deployed are working normally. From the error code, it appears the console service does not work.

Context

Without ingress, we may not be able to use minio.

Regression

helm release v5.2.0

Your Environment

Version used (minio --version): [helm release v5.2.0]
Server setup and configuration: AKS
Operating System and version (uname -a): AKS 1.30

The text was updated successfully, but these errors were encountered:

jiuker · 2024-10-18T02:03:58Z

Could you check this values.yaml?

operator/helm/tenant/values.yaml

Lines 460 to 478 in 54a9f26

    
           ingress: 
        
             api: 
        
               enabled: false 
        
               ingressClassName: "" 
        
               labels: { } 
        
               annotations: { } 
        
               tls: [ ] 
        
               host: minio.local 
        
               path: / 
        
               pathType: Prefix 
        
             console: 
        
               enabled: false 
        
               ingressClassName: "" 
        
               labels: { } 
        
               annotations: { } 
        
               tls: [ ] 
        
               host: minio-console.local 
        
               path: / 
        
               pathType: Prefix

ramondeklein · 2024-10-18T10:07:10Z

Can you show the output of curl -v https://<console-hostname> (it appears you publish MinIO console on without a subpath).

williamsun-hha · 2024-10-18T14:08:48Z

Thank you very much for your help, Sir! From the helm chart, api and console ingress are disabled. Let me enable them and test them and report back! Really appreciate it and have a great weekend! Sent from Yahoo Mail for iPhone On Friday, October 18, 2024, 3:07 AM, Ramon de Klein ***@***.***> wrote: Can you show the output of curl -v https://<console-hostname> (it appears you publish MinIO console on without a subpath). — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

williamsun-hha · 2024-10-18T19:39:23Z

Thank you very much for your help! I enable them and console and api in the values.yaml. It works perfectly. Really appreciate it! Have a great weekend! Sent from Yahoo Mail for iPhone On Thursday, October 17, 2024, 7:04 PM, jiuker ***@***.***> wrote: Could you check this values.yaml? https://github.com/minio/operator/blob/54a9f26436c5dce41aab6d06fadfcc23eb2681eb/helm/tenant/values.yaml#L460-L478 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

williamsun-hha · 2024-10-18T21:21:00Z

Thank you very much for your help! I enabled the console and api on exposeService. Then console and api are working. But console on 9443 is stop working now. On the console ingress. I did the test as you instructed, I got 502 Bad Gateway error. Thank you very much for your help! Sent from Yahoo Mail for iPhone On Friday, October 18, 2024, 3:07 AM, Ramon de Klein ***@***.***> wrote: Can you show the output of curl -v https://<console-hostname> (it appears you publish MinIO console on without a subpath). — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

williamsun-hha · 2024-10-19T03:54:13Z

Hi Ramon, I am able to get the console working on service port. The ingress is still a challenge. Thanks Sent from Yahoo Mail for iPhone On Friday, October 18, 2024, 3:07 AM, Ramon de Klein ***@***.***> wrote: Can you show the output of curl -v https://<console-hostname> (it appears you publish MinIO console on without a subpath). — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

williamsun-hha · 2024-10-21T04:40:32Z

Also I do not have any issue setting up ingress for bitnami Minio. Both console and s3api works perfectly. Thanks Sent from Yahoo Mail for iPhone On Friday, October 18, 2024, 8:54 PM, William Sun ***@***.***> wrote: Hi Ramon, I am able to get the console working on service port. The ingress is still a challenge. Thanks Sent from Yahoo Mail for iPhone On Friday, October 18, 2024, 3:07 AM, Ramon de Klein ***@***.***> wrote: Can you show the output of curl -v https://<console-hostname> (it appears you publish MinIO console on without a subpath). — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

williamsun-hha added community triage labels Oct 7, 2024

jiuker transferred this issue from minio/minio Oct 18, 2024

jiuker closed this as completed Oct 18, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Minio-console does not work with AKS ingress. #2343

Minio-console does not work with AKS ingress. #2343

williamsun-hha commented Oct 7, 2024

jiuker commented Oct 18, 2024 •

edited

Loading

ramondeklein commented Oct 18, 2024

williamsun-hha commented Oct 18, 2024 via email

williamsun-hha commented Oct 18, 2024 via email

williamsun-hha commented Oct 18, 2024 via email

williamsun-hha commented Oct 19, 2024 via email

williamsun-hha commented Oct 21, 2024 via email

Minio-console does not work with AKS ingress. #2343

Minio-console does not work with AKS ingress. #2343

Comments

williamsun-hha commented Oct 7, 2024

NOTE

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

Current Behavior

Context

Regression

Your Environment

jiuker commented Oct 18, 2024 • edited Loading

ramondeklein commented Oct 18, 2024

williamsun-hha commented Oct 18, 2024 via email

williamsun-hha commented Oct 18, 2024 via email

williamsun-hha commented Oct 18, 2024 via email

williamsun-hha commented Oct 19, 2024 via email

williamsun-hha commented Oct 21, 2024 via email

jiuker commented Oct 18, 2024 •

edited

Loading