External Service

A simple HTTP service can be defined as follows

Consuming an external service in from within the mesh can be done using the standard .mesh name resolving, for example httpbin.mesh.

Consuming an external service in from within the mesh can be done by filling the proper outbound section of the relevant dataplane resource:

• tags the external service can include an arbitrary number of tags, where kuma.io/service is a mandatory one. The special kuma.io/protocol tag is also taken into account and supports the standard Kuma protocol values. It designates the specific protocol being used by that service.

As with other services, avoid overlapping of service names under with already existing ones. A good practice would be to derive the tag value from the domain name or IP of the actual external service.