Prerequisites for running virtualized Istio based services in HCL OneTest™ Server
You can find information about the tasks that you must complete before you run virtualized Istio based services in HCL OneTest™ Server.
Configuring virtualized Istio based services in HCL OneTest™ Server
When you intend to virtualize services in the Istio mesh in HCL OneTest™ Server, you can create stubs in HCL OneTest™ API.
When you create the Istio stubs in HCL OneTest™ API, you must ensure that you are aware of the fully qualified domain name (FQDN) or the short name of the service that you want to virtualize in the Kubernetes cluster that hosts HCL OneTest™ Server.
<service-name>.<namespace>.<svc>.<cluster-name>
<service-name>
reviews.bookinfo.svc.myclusterThe short name of the service is as follows:
reviews
You must enter the host of the service that you want to virtualize, in the Host field of the physical transport in HCL OneTest™ API. You can provide either the FQDN or the short name of the service.
Considerations for running of stubs that virtualize Istio services
Before you run the stubs that virtualize services in namespaces contained in the HCL OneTest™ Server Kubernetes cluster, you must install HCL OneTest™ Server with the demo configuration.
After you author the virtualized Istio based services, you must commit the virtual service resources to a repository and add the repository to the project on HCL OneTest™ Server. You can configure a run of the virtualized Istio service. See Configuring a run of a virtual service.
Collection of usage metrics
If you want HCL OneTest™ Server to display the usage statistics of the virtual service instances, you must install the Prometheus server at the time of server installation.