Hello! Does <Min.io> deployment inside the single...
# ask-the-community
e
Hello! Does Min.io deployment inside the single container Flyte sandbox need additional setup to get the web interface working? I try to access it through localhost:30084 but it just redirects me to localhost:9001 and shows "can't be reached" error.
y
e
Nice, that works! The image shows 30084 so I thought it was it. I should have read it. Thank you!
y
I think we have old image
๐Ÿ‘ 1
p
The console page for minio requires port 30088 whereas the application talks to minio server on port 30084 . service o/p for minio in a sandbox env
Copy code
spec:
  clusterIP: 10.110.92.244
  externalTrafficPolicy: Cluster
  ports:
  - name: minio
    nodePort: 30084
    port: 9000
    protocol: TCP
    targetPort: minio
  - name: minio-console
    nodePort: 30088
    port: 9001
    protocol: TCP
    targetPort: minio-console
  selector:
    <http://app.kubernetes.io/instance|app.kubernetes.io/instance>: flyte
    <http://app.kubernetes.io/name|app.kubernetes.io/name>: minio
  sessionAffinity: None
  type: NodePort
status:
  loadBalancer:
    ingress:
    - hostname: localhost
๐Ÿ‘ 2
The image i guess is showing the server port and not the minio console port
k
We can probably update the image
a
I'll update the image.
167 Views