Defining group as a subdomain in domain

[akorp]

I found some projects which define group as a subdomain part of a domain and omit it later while defining api.

kubebuilder init --domain mygroup.mydomain.io && && kubebuilder create api --version v1 --kind Mykind vs
kubebuilder init --domain mydomain.io && kubebuilder create api --group mygroup --version v1 --kind Mykind

> cat PROJECT
...
  domain: mygroup.mydomain.io
  kind: Mykind
PROJECT

vs

> cat PROJECT
...
  domain: mydomain.io
  group: mygroup
  kind: Mykind
PROJECT

The files PROJECT will be different, but API the same.

NAME    APIVERSION              NAMESPACED   KIND
mykind  mygroup.mydomain.io/v1  true         MyKind

Is there any practical difference between those two options?

[camilamacedo86]

Here's a refined version of your draft. It clarifies the points you're discussing and makes the technical details more concise:

I'm not completely certain I follow your comment, but let me address the main point regarding API domain configurations in Kubebuilder.

In Kubebuilder, the "domain" should be specified only for the domains and groups that you create APIs for. These values are crucial as they generate the endpoints. If your project requires a multi-group setup, you can enable this option following the guide provided here: https://book.kubebuilder.io/migration/multi-group

To understand its usage see: https://book.kubebuilder.io/faq#how-does-the-value-informed-via-the-domain-flag-ie-kubebuilder-init---domain-examplecom-when-we-init-a-project

I am closing this one as sorted out but feel free to re-open if you see that has a need.