Testing internal services in Kubernetes
After you set up a Kubernetes cluster, you can use Rational® Integration Tester to test internal services in Kubernetes that are not exposed through an ingress gateway to external clients.
When you set up a Kubernetes cluster that runs various services, you can use Rational® Integration Tester to create tests or stubs to test the applications or service endpoints owned by the Kubernetes services. Rational® Integration Tester supports testing of the applications that use HTTP or HTTPS transports for communication.
Prerequisites
You must have completed the setting up of the latest version of a Kubernetes cluster in your IT infrastructure and ensured that various services run in the Kubernetes cluster.
- The name of the service that you want to test.
- The cluster IP address of the service and the port that the service uses in the cluster.
- The namespace that contains the service. Note: If you do not provide a namespace, Rational® Integration Tester considers the default value of the namespace as default.
- The certificate details of the Kubernetes cluster that are required to authenticate the connection requests from Rational® Integration Tester.
Task flow for testing internal services in Kubernetes
You can find information about the tasks that you can follow to test the internal services in Kubernetes.
Task | Go to... |
---|---|
Configure the Kubernetes cluster as a physical resource to connect from Rational® Integration Tester in the Physical View tab of the Architectural perspective. | Configuring a physical connection to a Kubernetes cluster |
Synchronize the application resources owned by an internal service of a Kubernetes cluster. | Synchronizing application resources of a Kubernetes cluster service in Rational Integration Tester |
Run the tests and stubs created by using the synchronization feature in Rational® Integration Tester. | Running tests and stubs |