Skip to content
This repository was archived by the owner on Mar 20, 2026. It is now read-only.
This repository was archived by the owner on Mar 20, 2026. It is now read-only.

Couldn't get operator console. Port forward is not working. #1590

@OlegPyzin

Description

@OlegPyzin

Description

kubectl port-forward -n minio-operator svc/main-console 9090:9090 fails during the login:

Handling connection for 9090
E0428 12:00:09.755599    6101 portforward.go:378] error copying from remote stream to local connection: readfrom tcp4 127.0.0.1:9090->127.0.0.1:51509: write tcp4 127.0.0.1:9090->127.0.0.1:51509: write: broken pipe
Handling connection for 9090
E0428 12:00:16.742167    6101 portforward.go:378] error copying from remote stream to local connection: readfrom tcp4 127.0.0.1:9090->127.0.0.1:51517: write tcp4 127.0.0.1:9090->127.0.0.1:51517: write: broken pipe
Handling connection for 9090
E0428 12:00:46.422940    6101 portforward.go:346] error creating error stream for port 9090 -> 9090: Timeout occurred
Handling connection for 9090
E0428 12:00:53.859326    6101 portforward.go:346] error creating error stream for port 9090 -> 9090: Timeout occurred
Handling connection for 9090
E0428 12:01:16.425885    6101 portforward.go:346] error creating error stream for port 9090 -> 9090: Timeout occurred
Handling connection for 9090
E0428 12:01:23.861442    6101 portforward.go:346] error creating error stream for port 9090 -> 9090: Timeout occurred
Handling connection for 9090
Handling connection for 9090
Handling connection for 9090
Handling connection for 9090
Handling connection for 9090
Handling connection for 9090
E0428 12:01:46.427496    6101 portforward.go:346] error creating error stream for port 9090 -> 9090: Timeout occurred
E0428 12:01:53.865114    6101 portforward.go:346] error creating error stream for port 9090 -> 9090: Timeout occurred
Handling connection for 9090
E0428 12:01:53.899094    6101 portforward.go:346] error creating error stream for port 9090 -> 9090: Timeout occurred
Handling connection for 9090
E0428 12:01:53.900632    6101 portforward.go:346] error creating error stream for port 9090 -> 9090: Timeout occurred

Expected Behavior

It should not fail and login should work.

Current Behavior

Got a white screen after entered username and password.

Possible Solution

There is no current solution provided.

Steps to Reproduce (for bugs)

  1. Create a kind cluster.
  2. Deploy minio operator.
  3. Deploy tenant with the name main.
  4. kubectl port-forward -n minio-operator svc/main-console 9090:9090
  5. Login via Browser localhost:9090

Context

Simply trying to get web admin console to administrate buckets.

Regression

Do not found the same issue.

Your Environment

  • Version used (minio-operator): 4.5.5
  • Environment name and version (e.g. kubernetes v1.17.2):
NAME        STATUS   ROLES           AGE    VERSION   INTERNAL-IP     EXTERNAL-IP   OS-IMAGE                         KERNEL-VERSION    CONTAINER-RUNTIME
control-1   Ready    control-plane   107d   v1.25.3   10.135.21.11    <none>        Debian GNU/Linux 11 (bullseye)   5.10.0-20-amd64   containerd://1.6.12
control-2   Ready    control-plane   107d   v1.25.3   10.135.9.84     <none>        Debian GNU/Linux 11 (bullseye)   5.10.0-20-amd64   containerd://1.6.12
control-3   Ready    control-plane   107d   v1.25.3   10.135.9.80     <none>        Debian GNU/Linux 11 (bullseye)   5.10.0-20-amd64   containerd://1.6.12
node-1      Ready    <none>          107d   v1.25.3   10.135.24.171   <none>        Debian GNU/Linux 11 (bullseye)   5.10.0-20-amd64   containerd://1.6.12
node-2      Ready    <none>          107d   v1.25.3   10.135.24.192   <none>        Debian GNU/Linux 11 (bullseye)   5.10.0-20-amd64   containerd://1.6.12
node-3      Ready    <none>          107d   v1.25.3   10.135.9.95     <none>        Debian GNU/Linux 11 (bullseye)   5.10.0-20-amd64   containerd://1.6.12
  • Server type and version: Virtual Machines
  • Operating System and version (uname -a): Debian GNU/Linux 11 (bullseye)
  • Link to your deployment file:
    Not apply.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions