[Feature] Please publish the api as distinct go module

[alvaroaleman]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

Importing the kube ray api (ray-operator/apis/ray) causes an import of the entire ray-operator and in turn a transient dependency on anything the ray operator depends on. Can we avoid that by making the api its distinct sub module in order to allow projects to import it without then depending on the entire ray-operator?

Use case

Programatically create ray CRs

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!