When you install the Kueue Operator on an OCP cluster via the web console, the only API object available for creation in the Installed Operators view is the `Kueue` CR.

This is inconsistent with the user experience for other Operators. For example, if you install the Serverless Operator, the APIs listed include:

• `KnativeServing`
• `KnativeEventing`
• `KnativeKafka`

Admins do not need to switch from a console experience to a CLI experience to create objects that enable functionality for users on the cluster, they can do everything in the same console.

I am proposing that, once you install the Kueue Operator, the `Kueue` CR should possibly be created by default, depending on the selections you made during the installation process, and then the API objects that are available from the Installed Operators view would be `ClusterQueue`, `LocalQueue` and `Job` CRs instead.