feat: support admin/config/set for minioJob

[jiuker]

feat: support admin/config/set for minioJob

mc admin config set ALIAS/ audit_webhook:IDENTIFIER  \
   endpoint="https://webhook-1.example.net"          \
   auth_token="TOKEN"                                \
   client_cert="cert.pem"                            \
   client_key="cert.key"

How to test:
1.deploy operator with envOPERATOR_STS_ENABLED = on
2.deploy tenant
3.deploy minioJob

apiVersion: v1
kind: ServiceAccount
metadata:
  name: mc-job-sa
---
apiVersion: sts.min.io/v1alpha1
kind: PolicyBinding
metadata:
  name: mc-job-bingding
spec:
  application:
    serviceaccount: mc-job-sa
  policies:
    - consoleAdmin
---
apiVersion: job.min.io/v1alpha1
kind: MinIOJob
metadata:
  name: minio-test-job
spec:
  serviceAccountName: mc-job-sa
  tenant:
    name: mytest-minio
  commands:
    - op: admin/config/set
      args:
        webhookName: "webhook1"
        endpoint:    "endpoint1"
        auth_token:  "token1"
        client_cert: "certContent"
        client_key:  "keyContent"

[shtripat]

Is it like we always allow setting audit_webhook only? How about setting notify_webhook and lambda_webhook configs? Should we allow setting type as well in CR?

[jiuker]

Is it like we always allow setting audit_webhook only? How about setting notify_webhook and lambda_webhook configs? Should we allow setting type as well in CR?

That's ok. You can set webhookName like notify_webhook:xxx or lambda_webhook:yyyy @shtripat

[shtripat]

While verification after applying the job CR, I see below error

$ kubectl get miniojobs.job.min.io -oyaml | yq '.items[0].status' 
message: Get tenant tenant-ns/tenant1 error:tenants.minio.min.io "tenant1" not found
phase: Error

whereas tenant is created and initialized fine

$ kubectl get tenants.minio.min.io -A 
NAMESPACE   NAME      STATE         AGE
tenant-ns   tenant1   Initialized   5m49s

[shtripat]

Verified. Works as expected. A minor one.

[shtripat]

lgtm