• 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/
      

      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:

      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.

            [KOGITO-6697] [SW] Enhance Service Discoverability

            After first research, we've decided to go without Stork.

            Ricardo Zanini added a comment - After first research, we've decided to go without Stork.

            Don't forget to update the related guides: https://github.com/kiegroup/kogito-docs/pull/18

            Ricardo Zanini added a comment - Don't forget to update the related guides: https://github.com/kiegroup/kogito-docs/pull/18

              rhn-support-fspolti Filippe Spolti
              rhn-support-zanini Ricardo Zanini
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: