You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running into an issue accessing the MinIO server that’s part of my Milvus deployment on GKE. I installed Milvus 2.5.4 using the Helm chart, with MinIO enabled and deployed in distributed mode (4 pods). The minio service is of type ClusterIP.
I'm trying to port-forward to the MinIO Console from my local machine using:
The MinIO Console does load at http://localhost:38533, and I'm able to enter the default credentials (minioadmin:minioadmin). However, immediately after logging in, the console crashes and becomes unresponsive.
The terminal running kubectl port-forward shows repeated broken pipe errors at the same time:
error copying from remote stream to local connection: write tcp ...: write: broken pipe
Has anyone successfully exposed the MinIO console in this setup?
Any help or guidance would be greatly appreciated!
Thanks!
PD.
I'm thinking maybe I need to use a load balancer instead of Cluster IP to be able to connect.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm running into an issue accessing the MinIO server that’s part of my Milvus deployment on GKE. I installed Milvus 2.5.4 using the Helm chart, with MinIO enabled and deployed in distributed mode (4 pods). The minio service is of type ClusterIP.
I'm trying to port-forward to the MinIO Console from my local machine using:
kubectl port-forward -n milvus service/milvus-historical-minio 38809:38809
The MinIO Console does load at http://localhost:38533, and I'm able to enter the default credentials (minioadmin:minioadmin). However, immediately after logging in, the console crashes and becomes unresponsive.
Browser DevTools show:
GET http://127.0.0.1:38533/api/v1/session 403 (Forbidden)
GET http://127.0.0.1:38533/api/v1/check-version 500 (Internal Server Error)
The terminal running kubectl port-forward shows repeated broken pipe errors at the same time:
error copying from remote stream to local connection: write tcp ...: write: broken pipe
Has anyone successfully exposed the MinIO console in this setup?
Any help or guidance would be greatly appreciated!
Thanks!
PD.
I'm thinking maybe I need to use a load balancer instead of Cluster IP to be able to connect.
Beta Was this translation helpful? Give feedback.
All reactions