add kaoto project

[maximilianoPizarro]

Description of Changes

added kaoto project

How to test? (OpenShift DevSpaces)

From your Workspaces started, run the tasks from devfile, confirm the port to expose and open in browser:

optional: podman mode

Only run "tasks start-with-docker"

[openshift-ci]

Hi @maximilianoPizarro. Thanks for your PR.

I'm waiting for a devfile member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[thepetk]

/ok-to-test

[michael-valdron]

This has happened every time @maximilianoPizarro has opened a PR:

Being that @maximilianoPizarro is a stack owner, I'm thinking he should be added to devfile organization for this to pass, looking at the message given by the status check:

User maximilianoPizarro is not allowed to trigger CI via pull_request on this repo.

cc @thepetk @elsony

[maximilianoPizarro]

This has happened every time @maximilianoPizarro has opened a PR:

Being that @maximilianoPizarro is a stack owner, I'm thinking he should be added to devfile organization for this to pass, looking at the message given by the status check:

User maximilianoPizarro is not allowed to trigger CI via pull_request on this repo.

cc @thepetk @elsony

@Jdubrick added me to Owners in the last PR from the other project.

Thanks in Advance again @michael-valdron and team.

[thepetk]

This has happened every time @maximilianoPizarro has opened a PR:

Being that @maximilianoPizarro is a stack owner, I'm thinking he should be added to devfile organization for this to pass, looking at the message given by the status check:

User maximilianoPizarro is not allowed to trigger CI via pull_request on this repo.

cc @thepetk @elsony

@Jdubrick added me to Owners in the last PR from the other project.

Thanks in Advance again @michael-valdron and team.

This should be done for every new stack. So we should add this one here: https://github.com/devfile/registry/blob/main/.github/CODEOWNERS too.

[thepetk]

This has happened every time @maximilianoPizarro has opened a PR:

Being that @maximilianoPizarro is a stack owner, I'm thinking he should be added to devfile organization for this to pass, looking at the message given by the status check:

User maximilianoPizarro is not allowed to trigger CI via pull_request on this repo.

cc @thepetk @elsony

+1 having in mind that now he will be an owner of two stacks.

[thepetk]

Needs review from the @devfile/che-team too

[svor]

run the storybook command is failed on Che:

I suggest updating the command labels to follow a consistent format and arranging them in a logical order. This will improve clarity and make it easier to understand the execution steps.
To have something like:

instead of

[svor]

lgtm

[maximilianoPizarro]

/retest-required

[maximilianoPizarro]

Hi Team, any status about this?

@thepetk @elsony @Jdubrick

Thanks in advanced

[Jdubrick]

/ok-to-test

[Jdubrick]

/ok-to-test

[thepetk]

@maximilianoPizarro this is currently blocked by devfile/api#1702. I've already created a PR to address the issue so I'd say it will be unblocked soon.

[thepetk]

@maximilianoPizarro needs to be rebased to the latest main

[thepetk]

In general lgtm, I'll aprove once all checks are passing

/ok-to-test

[maximilianoPizarro]

In general lgtm, I'll aprove once all checks are passing

/ok-to-test

Excellent, thank you for everything. Have a nice weekend 🙌

[thepetk]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: maximilianoPizarro, svor, thepetk

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [thepetk]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[maximilianoPizarro]

Hi @Jdubrick , I just wanted to ask if the pending status on Kunflux is in any way related to the progress of the PR, or if I should simply wait for the remaining reviewers to take a look. Have a great week. Thanks in advance!

[Jdubrick]

/ok-to-test