When you create an API Rule for a service, the API Gateway Controller creates an Istio Virtual Service for you behind the kyma-gateway. The Istio Virtual Service defines the rules that control how requests for a service are routed within an Istio service mesh. By creating an API Rule, you have a higher-level abstraction of Istio VirtualServices and Oathkeeper Access Rules that allows you to provision services quickly and securely. References: Using the API Gateway to Expose Services, Exposing a Service in Kyma with API Rules

The command kubectl get services lists all the services in the current namespace1. The get command is used to display one or more resources in Kubernetes2. The services argument specifies the type of resource to list. To list services in a differentnamespace, you can use the --namespace or -n flag3. References: Kubectl commands to list services, deployments and pods from namespace …, kubectl Cheat Sheet | Kubernetes, How to get the current namespace of current context using kubectl - Stack Overflow

 A service mesh in Kyma typically consists of two components: the data plane and the control plane12. The data plane is responsible for handling the communication between the microservices in the cluster. It consists of a set of sidecar proxies (Envoy) that are injected into each pod and intercept the traffic. The control plane is responsible for managing the configuration and policies of the data plane. It consists of a set of components (Istio) that provide features like service discovery, security, traffic management, observability, and more12. References: Discovering the Service Mesh, SAP BTP – KYMA – SERVICE MESH | SAP Blogs