Kubectl端口转发MinIO控制台遇broken pipe及timeout问题求助
MinIO控制台端口转发连接异常问题排查
问题现象
- 端口转发访问MinIO控制台时,连接仅短暂可用,终端反复输出连接处理日志:
Handling connection for 9000 Handling connection for 42935 Handling connection for 42935 ... - 片刻后出现管道断裂错误:
E0128 18:22:01.801739 40952 portforward.go:378] error copying from remote stream to local connection: readfrom tcp6 [::1]:42935->[::1]:50796: write tcp6 [::1]:42935->[::1]:50796: write: broken pipe - 最终持续输出超时及管道断裂报错:
E0128 18:22:31.738313 40952 portforward.go:346] error creating error stream for port 42935 -> 42935: Timeout occurred Handling connection for 42935 E0128 18:22:32.120930 40952 portforward.go:346] error creating error stream for port 42935 -> 42935: write tcp 192.168.0.16:50776->34.133.9.102:443: write: broken pipe ... - 控制台页面可显示但持续加载,登录时页面不断刷新直至崩溃或超时。
当前部署配置
apiVersion: apps/v1 kind: Deployment metadata: name: minio-deployment namespace: minio-ns spec: replicas: 1 selector: matchLabels: app: minio template: metadata: labels: app: minio spec: containers: - name: minio image: minio/minio args: - server - /data - --console-address - ":42935" volumeMounts: - name: minio-pv-storage mountPath: /data volumes: - name: minio-pv-storage persistentVolumeClaim: claimName: minio-pv-claim --- apiVersion: v1 kind: Service metadata: name: minio-service namespace: minio-ns spec: selector: app: minio ports: - name: minio port: 9000 targetPort: 9000 - name: minio-console port: 42935 targetPort: 42935 type: LoadBalancer --- apiVersion: v1 kind: PersistentVolumeClaim metadata: name: minio-pv-claim namespace: minio-ns spec: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi
已执行的调整操作
- 将MinIO Service的类型从ClusterIP修改为LoadBalancer
- 在MinIO容器启动参数中添加
--console-address ":42935",并在Service中暴露该端口
内容的提问来源于stack exchange,提问作者Leo Lad
相关产品推荐
相关产品推荐

