Disclaimer: This release
contains access to the virtual services that virtualize the Istio based
services feature in HCL OneTest™ Server as a Tech
Preview. The Tech Preview is intended for you to view the capabilities for
virtualized services offered by HCL OneTest™ Server, and to
provide your feedback to the product team. You are permitted to use the
information only for evaluation purposes and not for use in a production
environment. HCL provides
the information without obligation of support and "as is" without warranty
of any kind.
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
Restriction: You can run the Istio stubs only in
the HCL OneTest™ Server cluster or a
remote Kubernetes cluster.
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.
The FQDN of the service is as
follows:
<service-name>.<namespace>.<svc>.<cluster-name>
The short name of the service is as follows:
<service-name>
For example, if you want to virtualize the HTTP traffic in the service named as
reviews that runs in a namespace named as
bookinfo, and in the resource named as
svc
in the Kubernetes cluster named as
mycluster, then the FQDN of
the service is as follows:
reviews.bookinfo.svc.mycluster
The 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.
Note: The pass-through action in the stubs is not supported.
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.
When you install
HCL OneTest™ Server by
using the
demo configuration, then
HCL OneTest™ Server is preconfigured to
use the
bookinfo namespace as the virtualization
namespace.
Note: You can change or add virtualization namespaces by adding the
helm installation argument execution.istio.namespaces along
with a list of namespaces in a helm command.
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.
