[WIP] [KOGITO-8945] Defined a Traits API to customize a Kubernetes Service

[amadhusu]

Description of the change: https://issues.redhat.com/browse/KOGITO-8945

Motivation for the change: Setting up Traits API similar to Camel's approach to enhance the Profile model of deployment.

Checklist

• Add or Modify a unit test for your change
• Have you verified that tall the tests are passing?

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.

If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

[spolti]

instead being inside v1alpha08, maybe move to another place, maybe api/common_objects.go or something else, wdyt?

[amadhusu]

I could do that, but do you suggest moving the trait directory here as well? So all future traits like ingress etc are in something like api/trait/ingress.go for example.

[amadhusu]

@spolti As I am not using this struct anymore, this file base.go became unnecessary. Also I moved out the trait directory under api/trait to simplify the hierarchy. Let me know what you think.

[spolti]

@davidesalerno @amadhusu the purpose of the traits is to identify which trait needs to be configured automatically, right?

if so, don't we need to define it on the cr?

@amadhusu can you please provide a example CR as well the tests for this? If the service trait is auto == true, the service for the workflows needs to be created.

[amadhusu]

@spolti There is a sample CR with a basic test case for checking the workflow. I will work on the controller for the implementation of this so we can see it in action. I will create other examples and test cases for different Service Types as well once I am done with the Controller Implementation for the same.