[KOGITO-3749-community] - Release Kogito 0.17 #2576
[KOGITO-3749-community] - Release Kogito 0.17 #2576
Conversation
Hi @Kaitou786. Thanks for your PR. I'm waiting for a operator-framework member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the 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/test-infra repository. |
f89dea8
to
c7db1fc
Compare
Signed-off-by: Tarun Khandelwal <tarkhand@redhat.com>
c7db1fc
to
715e67c
Compare
@spolti Since you are previous contributor, can you please have a look for these changes, if you are fine with them. Thanks |
/ok-to-test |
/lgtm |
Waiting for @spolti to react. And i will merge it |
/lgtm |
Hi @mvalarh I'm responsible for the Kogito Operator. We are aware of this release, please go ahead! And thanks for reaching out! |
Signed-off-by: Tarun Khandelwal tarkhand@redhat.com
Thanks submitting your Operator. Please check below list before you create your Pull Request.
Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.
New Submissions
Updates to existing Operators
replaces
property?package.yaml
?Your submission should not
upstream-community-operators
andcommunity-operators
at onceOperator Description must contain (in order)
Operator Metadata should contain
Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here