Services that are exposed by your cluster must be defined as type LoadBalancer when deployed in the cloud, that is when you have multiple nodes that scale up and down. When deployed in local setups such as Minikube or when you know the IP address of the node, exposed services must be defined as NodePort.
For JasperReports IO At-Scale, there are 2 services that are potentially exposed in different situations:
| • | jrio-rest: Required for a production deployment when using a JasperReports Server repository, because all communication is performed via the REST API. |
| • | jrio-client: Used only for demonstration purposes to display the sample reports that are shipped in the jrio-client app and file-based repository. |
To expose the jrio-rest module in a production cluster, update the service configuration file jrio-at-scale-2.0.0/k8s/helm/templates/jrio-rest-service.yaml as follows:
In this example, port 8080 is the port on which the service will listen for requests.
If you are deploying the demonstration app in the jrio-client module, make the same change to the jrio-at-scale-2.0.0/k8s/helm/templates/jrio-client-service.yaml file.
Recommended Comments
There are no comments to display.