Overview: Application networking
Radius networking resources allow you to model:
- Communication between services
- Communication between a user and a service
Service to service communication
Radius containers can define connections to other containers, just like they can define connections to dependencies.
Network connections are defined as strings containing:
- The scheme (protocol) of the connection (http, https, tcp, etc.)
- The target container/service to connect to (basket, catalog, etc.)
- The port to connect to (80, 443, etc.)
For example, a frontend container may need to connect to a basket container. The frontend container would define a connection to the basket container, with the scheme
http, the target
basket, and the port
3000. The connection would look like this:
For more information on how to do service to service networking, visit the service networking how-to guide:How-To: Service to service networking
gateway defines how requests are routed to different resources, and also provides the ability to expose traffic to the internet. Conceptually, gateways allow you to have a single point of entry for traffic in your application, whether it be internal or external.
Refer to the Gateway schema for more information on how to model gateways.
Gateways support TLS termination. This allows incoming encrypted traffic to be decrypted with a user-specific certificate and then routed, unencrypted, to the specified routes. TLS certificates can be stored or referenced via a Radius secret store.
A gateway can be configured to passthrough encrypted SSL traffic to an HTTP route and container. This is useful for applications that already have SSL termination configured, and do not want to terminate SSL at the gateway.
To set up SSL passthrough, set
true on the gateway, and set a single route with no
path defined (just
Was this page helpful?
Sorry to hear that. If you would like to also contribute a suggestion visit and tell us how we can improve.