kie-kogito-serverless-operator-379: Investigate why non-dev scenarios now requires JDBC configuration #386
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
… now requires JDBC configuration
- Use "latest" image tag and namespaced images generation.
|
Guys @ricardozanini @domhanak , here goes the fix to use "latest" tagged images. Would you mind review? e2e tests worked locally with minikube, let's see on the CI. Thanks! |
ricardozanini
approved these changes
Feb 7, 2024
|
@jakubschwan is checking this |
wmedvede
added a commit
to wmedvede/kogito-serverless-operator
that referenced
this pull request
Feb 19, 2024
… JDBC configuration
- kie-kogito-serverless-operator-379: Investigate why non-dev scenarios now requires JDBC configuration (apache#386)
- Use "latest" image tag and namespaced images generation.
(cherry picked from commit df462a8)
rgdoliveira
pushed a commit
to rgdoliveira/kogito-serverless-operator
that referenced
this pull request
Mar 11, 2024
… now requires JDBC configuration (apache#386) - Use "latest" image tag and namespaced images generation.
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:
Closes #379
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.xto backport the original PR to the7.67.xbranch).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.