KOGITO-9971: [Guides] Dataindex deployment use cases with operator

[nmirasch]

jira: https://issues.redhat.com/browse/KOGITO-9971

Please make sure that your PR meets the following requirements:

• You have read the contributions doc
• Pull Request title is properly formatted: KOGITO-XYZ Subject
• Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
• The nav.adoc file has a link to this guide in the proper category
• The index.adoc file has a card to this guide in the proper category, with a meaningful description

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.

[tchughesiv]

does this use the new built-in data index deployment capabilities we've added to the operator? fyi, in case you hadn't seen or used it yet.
#518

granted, not sure when a new release will occur that would make this feature available

[nmirasch]

does this use the new built-in data index deployment capabilities we've added to the operator? fyi, in case you hadn't seen or used it yet. #518

granted, not sure when a new release will occur that would make this feature available

This use cases were done before that new feature, so the answer is no. For the moment they are showing a way to see that deployments working, and I think those use cases will need to be updated including that new feature you commented and that will be reflected in the doc as well. @ricardozanini WDYT?

[ricardozanini]

@nmirasch this is the reason why I mentioned you in #518 last week. Your guides should reflect that feature since we are going to release it together.

[ricardozanini]

Just to rectify my comment, we should merge this, then #518, and then open another to change this guide to link to #518. So we will have a version of this guide that won't include DI in the operator.

[ricardozanini]

Now we need to be creative and incorporate the use cases' sandbox repo here instead of linking to it.

[ricardozanini]

Can we add a little description of each?

[nmirasch]

@ricardozanini removed the ref to usecases repo and put the dataindex deployment related kustomization resources in detail. While we are waiting for the change the doc to link the new feature about the dataindex deployment reference. could you take a look? Thanks!

[domhanak]

There are some steps that are expecting something that does not exist, we need to include these in the guides.

[nmirasch]

I've added the referenced use cases to our official example here apache/incubator-kie-kogito-examples#1839 and modified the guides links to that.

[LuboTerifaj]

Hello @nmirasch ,

I checked Data Index Quarkus extensions section (data-index-quarkus-extension.adoc file) and I have a few minor comments.

There is missing an explanation, what is the difference between "Quarkus Data Index" and "Quarkus Data Index persistence" extensions.

The referenced "PostgreSQL Configuration" section does not contain all necessary information about how to configure the database properly.

Thanks!