Support new Trial Template in v1beta1

[andreyvelich]

/kind feature

To support new Trial Template API in v1beta1 we need to make few changes:

• Submit new API changes (New Trial Template API controller implementation #1202).
• Change Controller logic to support new Template. Also, modify Trial CR API (New Trial Template API controller implementation #1202).
• Change examples according to the new API (New Trial Template API controller implementation #1202).
• Enable testing for v1beta1 (New Trial Template API controller implementation #1202).
• Modify validation webhook. Make sure that metadata.name and metadata.namespace in TrialSpec is omitted (New Trial Template validation #1215).
• Add more test-cases for generator.go (Add more test cases for Generator #1216).

If I missed something, please let me know.
/cc @gaocegege @johnugeorge

[issue-label-bot]

Issue Label Bot is not confident enough to auto-label this issue.
See dashboard for more details.

[issue-label-bot]

Issue Label Bot is not confident enough to auto-label this issue.
See dashboard for more details.

[issue-label-bot]

Issue-Label Bot is automatically applying the labels:

Label	Probability
area/front-end	0.82

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

[issue-label-bot]

Issue-Label Bot is automatically applying the labels:

Label	Probability
area/front-end	0.82

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

[andreyvelich]

I will start to work on the second step.

@gaocegege @johnugeorge What do you think about RunSpec in Trial CR API, should we make it unstructured and store current Trial specification?

[gaocegege]

I think we should use unstructured.

[andreyvelich]

We can close this issue, since we fully implemented this.