-
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
kie-kogito-serverless-operator-335: Operator driven service discovery API Phase4 #338
kie-kogito-serverless-operator-335: Operator driven service discovery API Phase4 #338
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one minor comment! Thank you!
@ricardozanini your suggestions were added. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one left over. Thank you!!
@ricardozanini left over removed! |
8f2b336
to
7dfd11f
Compare
… API Phase4 - Add the discovery of Openshift DeploymentConfigs and Routes to the service discovery API
… API Phase4 - Code review suggestions 1
… API Phase4 - Code review suggestions 2
… API Phase4 - Augment the service uri query parameters
7dfd11f
to
0dd922d
Compare
Closes #335 |
… API Phase4 (apache#338) * kie-kogito-serverless-operator-335: Operator driven service discovery API Phase4 - Add the discovery of Openshift DeploymentConfigs and Routes to the service discovery API * kie-kogito-serverless-operator-335: Operator driven service discovery API Phase4 - Code review suggestions 1 * kie-kogito-serverless-operator-335: Operator driven service discovery API Phase4 - Code review suggestions 2 * kie-kogito-serverless-operator-335: Operator driven service discovery API Phase4 - Augment the service uri query parameters
… API Phase4 (apache#338) * kie-kogito-serverless-operator-335: Operator driven service discovery API Phase4 - Add the discovery of Openshift DeploymentConfigs and Routes to the service discovery API * kie-kogito-serverless-operator-335: Operator driven service discovery API Phase4 - Code review suggestions 1 * kie-kogito-serverless-operator-335: Operator driven service discovery API Phase4 - Code review suggestions 2 * kie-kogito-serverless-operator-335: Operator driven service discovery API Phase4 - Augment the service uri query parameters
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.