-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[KOGITO-9417] Introduce workflowproj-apiserver #185
base: main
Are you sure you want to change the base?
Conversation
4772b78
to
738d208
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@ricardozanini enjoy the GHA fix :) |
7f6486b
to
44368b4
Compare
Hi @ricardozanini, I gave it a try, following these steps:
It is expected that only one deployment/service/route set is created with the name |
f17a035
to
03e8d10
Compare
* Refactored and factorized cr & cli steps/framework * updates
3e87076
to
928c12e
Compare
Signed-off-by: Ricardo Zanini <zanini@redhat.com>
928c12e
to
dbfe4cc
Compare
Signed-off-by: Ricardo Zanini <zanini@redhat.com>
Signed-off-by: Ricardo Zanini <zanini@redhat.com>
@caponetto for a tech preview, I think we are there. Let me know when you will have time to test with Kubesmarts. |
Signed-off-by: Ricardo Zanini <zanini@redhat.com>
@ricardozanini is this still relevant? |
Yes. We had other priorities, but we will eventually get back to it for Kubesmarts. |
Description of the change:
See: https://issues.redhat.com/browse/KOGITO-9417
Draft/Design stage, please don't review.
Motivation for the change:
Checklist
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 the7.67.x
branch).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.