-
Enhancement
-
Resolution: Done
-
Blocker
-
None
-
False
-
False
-
-
2022 Week 32-34 (from Aug 8), 2022 Week 35-37 (from Aug 29)
Our Kubernetes Add-on must leverage Stork (https://quarkus.io/blog/smallrye-stork-intro/) to add discoverability capability with OpenAPI REST calls.
Every time a user add a OpenAPI rest call on top of their SW, they must then configure the application to add the endpoint, for example:
quarkus.rest-client.open_weather_yaml.url=http://my.url.on.kubernetes/
This is a hurdle for users, would be way easier to do instead:
quarkus.rest-client.open_weather_yaml.url=kubernetes:serving.knative.dev/v1/mynamespace/myservice
In runtime, the engine would then discover this endpoint using the given information.
- blocks
-
KOGITO-7373 [SW] Add custom function knative
-
- Resolved
-
- incorporates
-
KOGITO-3160 Add Configuration service discovery to Serverless Workflow function definitions
-
- Closed
-
- is cloned by
-
KOGITO-7373 [SW] Add custom function knative
-
- Resolved
-
- is documented by
-
KOGITO-7841 [KWS-Guides] Document the Enhanced Service Discovery
-
- Resolved
-
- is duplicated by
-
KOGITO-3159 Add Kubernetes service discovery to Serverless Workflow function definitions
-
- Closed
-
- is incorporated by
-
SRVLOGIC-5 [core] Service discovery of OpenAPI services in workflows
-
- Closed
-
- relates to
-
KOGITO-6998 [KSW-Guides] Instruct how to have different endpoint configuration profiles for OpenAPI calls
-
- Resolved
-
-
KOGITO-8013 [SW] Enhance Service Discoverability: Improve example to use the discovery
-
- Resolved
-
-
KOGITO-6109 Adds Kubernetes Service Discovery to REST and Open API Work Items
-
- Closed
-
-
KOGITO-7915 Kubernetes addon: Add a fail-fast capability
-
- Closed
-
[KOGITO-6697] [SW] Enhance Service Discoverability
Rank | New: Ranked higher |
Link |
New:
This issue is incorporated by |
Link |
New:
This issue is duplicated by |
Link |
New:
This issue incorporates |
Labels | New: ksw-dp1 |
Description | Original: Our Kubernetes Add-on must leverage Stork ([https://quarkus.io/blog/smallrye-stork-intro/)] to add discoverability capability with OpenAPI REST calls. | New: Our Kubernetes Add-on must leverage Stork ([https://quarkus.io/blog/smallrye-stork-intro/|https://quarkus.io/blog/smallrye-stork-intro/]) to add discoverability capability with OpenAPI REST calls. |
Priority | Original: Major [ 3 ] | New: Minor [ 4 ] |
Link |
New:
This issue relates to |
Assignee | Original: Ricardo Zanini [ rhn-support-zanini ] | New: Filippe Spolti [ rhn-support-fspolti ] |
Description | Original: Our Kubernetes Add-on must leverage Stork ([https://quarkus.io/blog/smallrye-stork-intro/|https://quarkus.io/blog/smallrye-stork-intro/]) to add discoverability capability with OpenAPI REST calls. |
New:
Our Kubernetes Add-on must leverage Stork ([https://quarkus.io/blog/smallrye-stork-intro/|https://quarkus.io/blog/smallrye-stork-intro/]) to add discoverability capability with OpenAPI REST calls.
Every time a user add a OpenAPI rest call top their SW, they must then configure the application to add the endpoint, for example: {code} quarkus.rest-client.open_weather_yaml.url=http://my.url.on.kubernetes/ {code} See: https://github.com/quarkiverse/quarkus-openapi-generator/blob/main/integration-tests/example-project/src/test/java/io/quarkiverse/openapi/generator/it/WiremockOpenWeather.java#L18-L33 This is a hurdle for users, would be way easier to do instead: {code} quarkus.rest-client.open_weather_yaml.url=kubernetes:serving.knative.dev/v1/mynamespace/myservice {code} In runtime, the engine would then discover this endpoint using the given information. |
Description |
Original:
Our Kubernetes Add-on must leverage Stork ([https://quarkus.io/blog/smallrye-stork-intro/|https://quarkus.io/blog/smallrye-stork-intro/]) to add discoverability capability with OpenAPI REST calls.
Every time a user add a OpenAPI rest call top their SW, they must then configure the application to add the endpoint, for example: {code} quarkus.rest-client.open_weather_yaml.url=http://my.url.on.kubernetes/ {code} See: https://github.com/quarkiverse/quarkus-openapi-generator/blob/main/integration-tests/example-project/src/test/java/io/quarkiverse/openapi/generator/it/WiremockOpenWeather.java#L18-L33 This is a hurdle for users, would be way easier to do instead: {code} quarkus.rest-client.open_weather_yaml.url=kubernetes:serving.knative.dev/v1/mynamespace/myservice {code} In runtime, the engine would then discover this endpoint using the given information. |
New:
Our Kubernetes Add-on must leverage Stork ([https://quarkus.io/blog/smallrye-stork-intro/|https://quarkus.io/blog/smallrye-stork-intro/]) to add discoverability capability with OpenAPI REST calls.
Every time a user add a OpenAPI rest call on top of their SW, they must then configure the application to add the endpoint, for example: {code} quarkus.rest-client.open_weather_yaml.url=http://my.url.on.kubernetes/ {code} See: https://github.com/quarkiverse/quarkus-openapi-generator/blob/main/integration-tests/example-project/src/test/java/io/quarkiverse/openapi/generator/it/WiremockOpenWeather.java#L18-L33 This is a hurdle for users, would be way easier to do instead: {code} quarkus.rest-client.open_weather_yaml.url=kubernetes:serving.knative.dev/v1/mynamespace/myservice {code} In runtime, the engine would then discover this endpoint using the given information. |
Link |
New:
This issue is cloned by |
Link |
New:
This issue blocks |
Status | Original: Open [ 1 ] | New: Coding In Progress [ 3 ] |
Summary | Original: [SW] Enhance Service Discoverability with Storks | New: [SW] Enhance Service Discoverabilit |
Summary | Original: [SW] Enhance Service Discoverabilit | New: [SW] Enhance Service Discoverability |
Issue Type | Original: Enhancement [ 13 ] | New: Epic [ 16 ] |
Epic Name | New: [SW] Enhance Service Discoverability |
Link |
Original:
This issue is incorporated by |
Link |
New:
This issue is incorporated by |
Priority | Original: Minor [ 4 ] | New: Blocker [ 1 ] |
Labels | Original: ksw-dp1 | New: ksw-dp2 |
Issue Type | Original: Epic [ 16 ] | New: Enhancement [ 13 ] |
Link |
New:
This issue follows up on |
Sprint | New: 2022 Week 32-34 (from Aug 8) [ 45379 ] |
Rank | New: Ranked lower |
Git Pull Request | New: https://github.com/kiegroup/kogito-runtimes/pull/2411 | |
Status | Original: Coding In Progress [ 3 ] | New: Pull Request Sent [ 10011 ] |
Link |
New:
This issue is documented by |
Sprint | Original: 2022 Week 32-34 (from Aug 8) [ 45379 ] | New: 2022 Week 32-34 (from Aug 8), 2022 Week 35-37 (from Aug 29) [ 45379, 45381 ] |
Link |
Original:
This issue follows up on |
Link |
New:
This issue relates to |
Resolution | New: Done [ 1 ] | |
Status | Original: Pull Request Sent [ 10011 ] | New: Resolved [ 5 ] |
Fix Version/s | New: 1.28.0.Final [ 12391872 ] |
Link |
New:
This issue relates to |
Rank | New: Ranked higher |
Link |
New:
This issue relates to |