Add kustomization overlay: katib-openshift

[maanur]

What this PR does / why we need it:
Current version of Katib have some issues and inconveniences when deployed to OpenShift, so I tried to introduce a workaround in form of kustomization overlay.

Workaround to #1512, but only for OpenShift 4.4+

Special notes for your reviewer:
Tested against OpenShift 4.6.21

Release note:

NONE

[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.

[aws-kf-ci-bot]

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

[maanur]

@googlebot I signed it!

[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.

[maanur]

@googlebot I signed it!

[andreyvelich]

Thank you for this effort, this is very helpful!
I think we should wait until we merge this PR: #1498, since we are making some changes to store Katib manifests.
After that, we can rebase this PR and merge it.

/cc @yanniszark @davidspek @johnugeorge @gaocegege

[davidspek]

@andreyvelich I'll work on my PR tomorrow, hopefully it will then be ready to merge. If after that any help is needed with this PR I'm happy to provide assistance.

[andreyvelich]

Thank you for your help @davidspek!

[andreyvelich]

@maanur I apologies for the delays on this PR.
Please, can you rebase and we can merge it ?

[andreyvelich]

/ok-to-test

[davidspek]

/test kubeflow-katib-presubmit

[davidspek]

I've added some comment to help migrate this PR to implement the changes introduced in #1498. After these changes this PR should be good to go.

[maanur]

Manually tested against OpenShift version 4.6.21

[davidspek]

@maanur Looks good to me.
/lgtm

[andreyvelich]

Thank you for this effort @maanur!
I left few comments from my side.

It would be great if you could also left your review @yanniszark @nakfour @gaocegege @johnugeorge

[andreyvelich]

Thank you for the changes @maanur.
/lgtm
/hold for the review from others.

[davidspek]

/lgtm

[andreyvelich]

I think we can merge it.
Thank you for this effort @maanur!
/hold cancel
/approve

[google-oss-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andreyvelich, maanur

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 [andreyvelich]

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