forked from apache/incubator-kie-kogito-serverless-operator
-
Notifications
You must be signed in to change notification settings - Fork 0
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 9691 test 2 #2
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…… (#809) * [KOGITO-4731] - Conditions should reflect latest evaluated status - Review comments * Gix Lint issue * Remove failed condition when service recovered from failure * Set failed condition to false when reconcilation recovered from failure
* [KOGITO-3105] - Missing status for failures for KogitoRuntime CRs * Set reconcilation time to 1min Co-authored-by: Vaibhav <[email protected]>
Signed-off-by: Karel Suta <[email protected]>
…using OC client (#830) Signed-off-by: Karel Suta <[email protected]>
…on (#835) Signed-off-by: Karel Suta <[email protected]>
…on (#835) Signed-off-by: Karel Suta <[email protected]>
* KOGITO-4858 Automatic build of examples * update * Moved to pkg * lint correction * update * small update on examples images deploy
* KOGITO-4858 Automatic build of examples * update * Moved to pkg * lint correction * update * small update on examples images deploy
When deployed with custom probes.
…stry (#848) Signed-off-by: Karel Suta <[email protected]>
Signed-off-by: Karel Suta <[email protected]>
* [KOGITO-5005] - Operator print irrelevant metadata in logs * Fix Kustomize version and release note
* [KOGITO-5005] - Operator print irrelevant metadata in logs * Fix Kustomize version and release note
* fix explainability dto * add space
…egistry (#865) Signed-off-by: Karel Suta <[email protected]>
…s (#868) * [KOGITO-5104] - RHPAM Kogito operator creates wrong default image tags * fix failing olm test
…s (#868) * [KOGITO-5104] - RHPAM Kogito operator creates wrong default image tags * fix failing olm test
…s (#868) * [KOGITO-5104] - RHPAM Kogito operator creates wrong default image tags * fix failing olm test
…#1438) Fixes: - https://github.com/kiegroup/kogito-operator/security/dependabot/46 - https://github.com/kiegroup/kogito-operator/security/dependabot/45 - https://github.com/kiegroup/kogito-operator/security/dependabot/42 - https://github.com/kiegroup/kogito-operator/security/dependabot/40 - https://github.com/kiegroup/kogito-operator/security/dependabot/38 - https://github.com/kiegroup/kogito-operator/security/dependabot/47 - https://github.com/kiegroup/kogito-operator/security/dependabot/43 Signed-off-by: Your Name <[email protected]>
…os ticket (#1448) Signed-off-by: Your Name <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the change:
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.