Applying same console fix for the subpath issue

[cniackz]

Objective:

To fix issue: #1607 and be able to use a sub-path for Operator UI.

Story:

This issue is very similar to minio/object-browser#2045 and maybe same fix should apply here: minio/object-browser#2725

Reasoning:

I think this fix is easier than console because we don't need minio binary for Operator, hence the testing is more straightforward

How to test locally:

• Put the assets inside to test in port 9090:

cd ~/operator
make swagger-gen

cd ~/operator/web-app
yarn && yarn build

• Add a sub-path via env var as observed below

• Compile with the assets of this PR, and you will be able to load the UI from the sub-path as expected:

Thank you https://github.com/polaris-phecda @polaris-phecda for the fix!.

Also tested in k8s environment:

• Service using node port in kind:

spec:
  ports:
    - name: http
      protocol: TCP
      port: 9090
      targetPort: 9090
      nodePort: 30082
    - name: https
      protocol: TCP
      port: 9443
      targetPort: 9443
      nodePort: 31813
  selector:
    app.kubernetes.io/instance: minio-operator-console
    app.kubernetes.io/name: operator
  clusterIP: 10.96.247.6
  clusterIPs:
    - 10.96.247.6
  type: NodePort

• Console Deployment:

apiVersion: apps/v1
kind: Deployment
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/instance: minio-operator-console
      app.kubernetes.io/name: operator
  template:
    metadata:
      creationTimestamp: null
      labels:
        app.kubernetes.io/instance: minio-operator-console
        app.kubernetes.io/name: operator
    spec:
      containers:
        - name: operator
          image: docker.io/minio/operator:v5.0.4-13-g041a74ca
          args:
            - ui
            - '--certs-dir=/tmp/certs'
          ports:
            - name: http
              containerPort: 9090
              protocol: TCP
            - name: https
              containerPort: 9443
              protocol: TCP
          env:
            - name: OPERATOR_SUBPATH
              value: /minio-operator/

• Created the image:

cd ~/operator
make docker

Got

=> => naming to docker.io/minio/operator:v5.0.4-13-g041a74ca

Loaded in the local cluster:

kind load docker-image docker.io/minio/operator:v5.0.4-13-g041a74ca

• Changed images in the Deployments to test.

[allanrogerr]

Works with operator standalone binary - but in k8s I cant get it to respect the env parameter. It keeps navigating back to http://localhost:9090/login

I validated from within the operator pod:

k -n minio-operator exec -it minio-operator-5fd4bf9857-57xxj -- /bin/bash
bash-4.4$ echo $OPERATOR_SUBPATH
minio-operator

[cniackz]

Add the var in the console deployment:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: console
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/instance: minio-operator-console
      app.kubernetes.io/name: operator
  template:
    metadata:
      creationTimestamp: null
      labels:
        app.kubernetes.io/instance: minio-operator-console
        app.kubernetes.io/name: operator
    spec:
      containers:
        - name: operator
          image: docker.io/minio/operator:v5.0.4-13-g041a74ca
          args:
            - ui
            - '--certs-dir=/tmp/certs'
          ports:
            - name: http
              containerPort: 9090
              protocol: TCP
            - name: https
              containerPort: 9443
              protocol: TCP
          env:
            - name: OPERATOR_SUBPATH
              value: /minio-operator/

[allanrogerr]

Hop to a tenant doesn't seem to work - when I remove the SUBPATH env variable and restart the console pod, it works again