add docs for "kubeflow arena" component

[thesuperzapper]

To be honest, I was not aware of Arena until recently, but as it is developed in the Kubeflow GitHub org, it deserves a place on the website.

I have used the same OWNERS as the kubeflow/arena repository.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: thesuperzapper
Once this PR has been reviewed and has the lgtm label, please assign animeshsingh for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[google-oss-prow]

The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the kubeflow org. You can then trigger verification by writing /verify-owners in a comment.

• denverdino
  • User is not a member of the org. User is not a collaborator. Satisfy at least one of these conditions to make the user trusted.
• happy2048
  • User is not a member of the org. User is not a collaborator. Satisfy at least one of these conditions to make the user trusted.
• wsxiaozhang
  • User is not a member of the org. User is not a collaborator. Satisfy at least one of these conditions to make the user trusted.

[thesuperzapper]

Tagging the owners of kubeflow/arena @cheyang @wsxiaozhang @denverdino @happy2048

And community leads to approve the PR: @jbottum @zijianjoy @james-jwu @chensun

[thesuperzapper]

Well... #3556 (comment) certainly raises some questions.

Perhaps an alternative proposal is to move the kubeflow/arena repository to its own GitHub org.

[varodrig]

@thesuperzapper should we close this PR?

[thesuperzapper]

@thesuperzapper should we close this PR?

@varodrig we still need to decide the future of "Kubeflow Arena" separate to this PR, but if it decides to become an official component, it will need a presence on the docs.

Here are the related issues about the ambiguous status of Kubeflow Arena as a component:

• WG sponsorship for arena arena#405
• [Discussion] Arena project roadmap community#683

Perhaps we should leave it open to remind us?

[varodrig]

• [Discussion] Arena project roadmap community#683

I see that will be discussed on the community meeting. we can wait till then. thank you