See KOGITO-3129 and documentation at https://docs.google.com/document/d/1TRByiC7WKD9E1zmrzRVAzSQPbzsaxiHzzmQqGz3TpdY/edit?ts=5f468186#heading=h.cjitbxwvp468
To serve the generated infrastructure information of a given Kogito service (custom or supporting), we would need an HTTP web server. But instead of installing httpd, NGINX or any other binaries in the image, hence increasing the final image size, we will create a custom HTTP lightweight serving code in Go. This code can be compiled and installed in the image as a native executable.
The image should provide:
1. The HTTP server installed
2. A way to start the container with this new executable instead of starting the application when running the container
- blocks
-
KOGITO-3129 Kogito service infrastructure metadata endpoint support
- Closed
-
KOGITO-3207 Consume infrastructure metadata information from Kogito service being deployed
- Closed
- is blocked by
-
KOGITO-3204 Generate Monitoring, Persistence and Events infrastructure information as a static file in build time
- Closed