See KOGITO-3129 and docs at https://docs.google.com/document/d/1TRByiC7WKD9E1zmrzRVAzSQPbzsaxiHzzmQqGz3TpdY/edit?ts=5f468186#heading=h.58zhsna2twsx

If an user wish to deploy a custom Kogito service that requires monitoring (by using the monitoring add-on), they would have to provide this information in the KogitoRuntime CR resource. This information is already known by the service, having to add it again in the CR is double the work needed from users perspective.

Since now we have the endpoint being served by the same deployment image (KOGITO-3206), the operator could fetch this endpoint for the infrastructure metadata and react upon it.

This enhancement is to deploy the Kogito service with an optional initContainer so the operator would fetch this info before the application gets deployed. Once it's ready, the initContainer could shutdown. This should be optional because we can have scenarios where users would like to just deploy a simple service without infra dependencies/extra configurations.