[Frontend] minio client in API server can be configured with environment variables

[eterna2]

Background

I am deploying multiple kubeflow pipelines in a multi-cloud environment (AWS and Azure), and I am using minio-gateway as a proxy to Azure blob storage.

I need to have configurable minio endpoint to support multiple kubeflow pipelines deployment. Currently, it is hard-coded to the kubeflow namespace.

Related PR

#1064 is part of my PR to make minio endpoint configurable from the kfp sdk.

Related issues

#1319

Changes

This PR exposes the minio parameters as environment variables which allows me to deploy kubeflow pipelines to other namespaces.

• MINIO_ENDPOINT is composed from MINIO_HOST and MINIO_NAMESPACE so that we can do the following in the deployment yaml.

env:
  - name: MINIO_NAMESPACE
     valueFrom:
       fieldRef:
         fieldPath: "metadata.namespace"

---

This change is 

[k8s-ci-robot]

Hi @eterna2. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

Hi @eterna2. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[IronPan]

/lgtm
/approve

[IronPan]

awesome! thank you

[IronPan]

/approve cancel

[IronPan]

do you mind adding a frontend patch in here
https://github.com/kubeflow/pipelines/tree/master/manifests/namespaced-install
that set the minio namespace env for frontend?
similar to ml-pipeline-persistenceagent-deployment-patch.yaml

[eterna2]

@IronPan
Hey I have rebased with the latest HEAD with the manifest, and added the patch for pipeline-ui.

I also regenerated the namespaced-install.yaml with the updated kustomize config.

[rileyjbauer]

/ok-to-test

[IronPan]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: IronPan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [IronPan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: IronPan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [IronPan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment