Doc into FAQ: Further explanation about domain and apis

[camilamacedo86]

Feature Request

Describe the problem you need a feature to resolve.

How and where is the domain informed used?

Currently, the tool does not support work with multi-domains to create the APIs by default. For more info check the issue kubebuilder/issues/2394 raised to add this support Therefore, you will check below that when you use the subCommand create api you will not need to inform the domain anymore. You will only inform the group, the Kind and the Version to create the APIs(s) and/or Controllers with the purpose to reconcile them and then, all will be scaffolded using this domain which is stored in the PROJECT file.

Be aware that you can work with external and core types which would have another domain, but the tool is not fully helping out with. For further info see the issue kubebuilder/issues/1999.

Describe the solution you'd like.

• How the domain is used in the tools? Can I create apis for different domains ( we need also cover how controller-gen uses it )
• How to create a controller to reconcile external and core types?

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.