tiagobento commented on issue #1034: URL: https://github.com/apache/incubator-kie-issues/issues/1034#issuecomment-2059940804
@ricardozanini Hi! I was discussing this task with @thiagoelg, as he is already working on it, and we were able to understand the overall architecture and the pieces that compose the operator and what a release of it means. Our understanding is that the manager binary needs to be built and the operator image will include it. The `operator.yaml` file is actually how people install the operator, and this `operator.yaml` file has references to the images that are published to Quay.io. All `kogito-swf-builder`, `kogito-swf-devmode` and `kogito-serverless-operator` images. Let us know if we understood something wrong. Since for Apache KIE 10 we're temporarily copying the operator to `kie-tools`, it occurred to me that the description of this task might be wrong, and we'll actually need to do the release from the copy of the operator that is going to be inside `kie-tools`. To make this happen, the entire `kogito-serverless-operator` needs to be brought in into `packages/kogito-serverless-operator`, so that every part of the build can be done using the other resources that are also part of `kie-tools`, like the images. So, assuming we understood everything correctly, and assuming that we indeed need to release from `kie-tools`, we'll need to also copy some of the release jobs we have. There are some checks that can be easily ported to `kie-tools`, but the Jenkins release jobs were a bit confusing for us. @rodrigonull or @jstastny-cz do you think you may be able to help? Overall, after what we saw, we're ~80% confident that we can integrate this repo inside the `kie-tools` build without problems. The only hard part would be making the E2E tests comply with the conventions we have on `kie-tools`, but this can be addressed with temporary dedicated GitHub Actions workflows like `e2e.yml` and `check-container-builder.yml` @ricardozanini The `check.yml` job we actually wouldn't need to port, as we integrate the "codegen" part on the build itself, and the CI of `kie-tools` will check for modified files after the build. @ricardozanini Another thing that would be great for us to understand, because it has to do with how `kie-tools` handles versions, is how do we specify the version of the images that the operator depends on? Thanks for the help so far! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
