feat(deployment): Kustomize manifest for Azure deployments

[jotaylo]

Description of your changes:
Kustomize manifest for KFP deployment using Azure Database for MySQL and MinIO gateway to Azure Blobstore

Checklist:

• The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

• Do you want this pull request (PR) cherry-picked into the current release branch?

  Learn more about cherry-picking updates into the release branch.

[kubeflow-bot]

This change is 

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[k8s-ci-robot]

Hi @jotaylo. 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.

[jotaylo]

@googlebot I signed it!

[Bobgy]

@Ark-kun let's the continue the discussion here.

We actually accepted AWS manifests from people working for AWS.
#4350

The previous AWS manifests we rejected were maintained by community.

Do you have any concerns with this?

[Bobgy]

@jotaylo I want to confirm responsibilities for putting the manifests in kfp repo:

• Before each release, we'll ask your team to verify your manifests still work for Azure
• For user issues reported specific to Azure, we'd expect response from your team members
• In the long term, you should probably maintain your own test infra that continuously ensure it's working so we can reduce some of the manual efforts before release

Do you think that's reasonable?
/cc @dtzar @eedorenko @sudivate

[eedorenko]

Do you think that's reasonable?
Sounds good to me.

/approve

[Ark-kun]

We actually accepted AWS manifests from people working for AWS.
#4350

The previous AWS manifests we rejected were maintained by community.

Do you have any concerns with this?

I do not have any concerns. I welcome all contributors. I just wanted our response to be consistent. Glad to see it is consistent.

[eedorenko]

/assign @rmgogogo

[Bobgy]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Bobgy, eedorenko

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:

• manifests/kustomize/OWNERS [Bobgy]

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

[Bobgy]

Sorry for the delay, I was on vacation.