[GSOC] Support for various Parameter distributions in Katib

[shashank-iitbhu]

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #2059

Checklist:

• Docs included if any changes are user facing

[shashank-iitbhu]

Hey @tenzen-y
I've drafted this proposal based on the discussion in kubeflow/katib#2059.
It's still in the early stages, and I'm learning about maintaining two versions of CRD APIs and going through codebase on how to structure v1beta2 alongside v1beta1.
I'll reach out if I have any questions.

[tenzen-y]

Hey @tenzen-y I've drafted this proposal based on the discussion in kubeflow/katib#2059. It's still in the early stages, and I'm learning about maintaining two versions of CRD APIs and going through codebase on how to structure v1beta2 alongside v1beta1. I'll reach out if I have any questions.

Based on recent discussions, we decided to keep the v1beta1 API version, and then we will add parameter distribution API to the v1beta1 API. That would be great to collect early feedback from users.

[andreyvelich]

Thank you for this!
I added a few comments.
/assign @tenzen-y @johnugeorge

[shashank-iitbhu]

/area gsoc

[shashank-iitbhu]

/assign

[tenzen-y]

I added some comments.

[tenzen-y]

I added a comment for a nit.
Otherwise lgtm.

[tenzen-y]

Thank you!
/lgtm
/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tenzen-y

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 [tenzen-y]

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