minio-instance-pool pods unable to connect to kubeapi

Bug

Description

As of Big Bang 3.17.0, the minio-instance-pools have trouble communicating with the kubeapi. I suspect this is because of the networking changes from the bb-common update. I believe this comes down to a mismatch between the pod-selector being created with the new bb-common compared to how the minio-instance-pool pods are labeled. The selectors on the network policy objects have "app.kubernetes.io/name=minio-instance" but the pods have no matching label.

When looking at logs using --all-containers:

2026/03/03 02:20:14 validator.go:65: Get "https://10.96.0.1:443/apis/minio.min.io/v2/namespaces/minio/tenants/minio-minio-minio-instance": net/http: TLS handshake timeout
panic: Get "https://10.96.0.1:443/apis/minio.min.io/v2/namespaces/minio/tenants/minio-minio-minio-instance": net/http: TLS handshake timeout

goroutine 1 [running]:
github.com/minio/operator/sidecar/pkg/validator.Validate({0x7ffd722f8b1a, 0x1a})

BigBang Version

Big Bang 3.17.0, minio 7.1.1-bb.16

Workaround

Force a label to be added to the minio-instance-pools by updating the Big Bang configmap with:

  minio:
    values:
      upstream:
        tenant:
          poolsMetadata:
            labels:
              app.kubernetes.io/name: minio-instance