Operator console changes to allow enabling of SFTP for tenant

[shtripat]

Added console changes for enabling SFTP while tenant creation

How to verify the changes

Steps-1: Create a kind cluster with below details

$ cat kind-config.yaml
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
  - role: control-plane
  - role: worker
  - role: worker
  - role: worker
  - role: worker

$ kind create cluster --config kind-config.yaml

Step-2: Build the operator image and load to the kind cluster

$ TAG=minio/operator:sftp make all
$ kind load docker-image docker.io/minio/operator:sftp

Step-3: Prepare the operator.yaml as below

$ kubectl kustomize . > operator-test.yaml

Step-4: Update the operator-test.yaml file and set the operator image names as docker.io/minio/operator:sftp

$ sed -i "s/minio\/operator:v5.0.6/docker.io\/minio\/operator:sftp/g" operator-test.yaml 

Step-5: Deploy the operator

$ kubectl apply -f operator-test.yaml

Step-6: Port forward to operator and open operator console

$ kubectl minio proxy

Step-7: Create tenant as per below details

Step-8: You should be able to see <tenant-name>-hl service as below

$ kubectl get svc -A
NAMESPACE        NAME               TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                  AGE
default          kubernetes         ClusterIP      10.96.0.1       <none>        443/TCP                  2d2h
kube-system      kube-dns           ClusterIP      10.96.0.10      <none>        53/UDP,53/TCP,9153/TCP   2d2h
minio-operator   console            ClusterIP      10.96.209.137   <none>        9090/TCP,9443/TCP        5h38m
minio-operator   operator           ClusterIP      10.96.44.57     <none>        4221/TCP                 5h38m
minio-operator   sts                ClusterIP      10.96.155.144   <none>        4223/TCP                 5h38m
tenant-ns        minio              LoadBalancer   10.96.236.190   <pending>     443:30693/TCP            5h35m
tenant-ns        tenant-1-console   LoadBalancer   10.96.243.4     <pending>     9443:30643/TCP           5h35m
tenant-ns        tenant-1-hl        ClusterIP      None            <none>        9000/TCP,8022/TCP        5h35m

Step-9: Port forward to services as below to access through sftp

$ kubectl port-forward service/tenant-1-hl -n tenant-ns 8022
$ kubectl port-forward service/minio -n tenant-ns 9443:443

Step-10: Use sftp to access MinIO bucket/objects

$ kubectl get secrets/tenant-1-user-0 -n tenant-ns -oyaml | yq '.data."CONSOLE_ACCESS_KEY"' | base64 -d
WZaBqLMGYViJ0Sba

$ kubectl get secrets/tenant-1-user-0 -n tenant-ns -oyaml | yq '.data."CONSOLE_SECRET_KEY"' | base64 -d
XMPAlfUUM4rnaAnGTxPKzeYYcBiRlUVr

$ mc alias set m1 https://localhost:9443 WZaBqLMGYViJ0Sba XMPAlfUUM4rnaAnGTxPKzeYYcBiRlUVr --insecure
Added `m1` successfully.

$ mc mb m1/test-bucket --insecure
Bucket created successfully `m1/test-bucket`.

$ mc cp /etc/issue m1/test-bucket --insecure
/etc/issue:                     28 B / 28 B ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.00 KiB/s 0s

$ sftp -P 8022 WZaBqLMGYViJ0Sba@localhost
The authenticity of host '[localhost]:8022 ([::1]:8022)' can't be established.
ECDSA key fingerprint is SHA256:wvTkjD8weTabgPkcsl+z1V1WOiKhsHzdtkdtpm3s7Fw.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '[localhost]:8022' (ECDSA) to the list of known hosts.
WZaBqLMGYViJ0Sba@localhost's password: 
Connected to localhost.
sftp> ls test-bucket/
test-bucket/issue  
sftp> ls test-bucket/issue 
test-bucket/issue    
sftp> 

[jiuker]

LGTM

[anjalshireesh]

Tested, working as expected.

[pjuarezd]

Tested, working.