Networking

Yelken allows extensive networking configuration for your projects to accommodate complex networking requirements. You can access your services internally inside the environment or expose them to the internet.

To let other services inside the environment access your service internally, you need to define the ports it listens on. Then you can use the internal domain name assigned to your service to access it in your other services. Once you define the ports of your service, you can expose them to the internet too.

For advanced networking configuration, Yelken provides network settings at two different levels: Project and Service. At project level, you can:

• Add one or more of your own custom domains.
• Add route definitions per domain that targets port of a service in any environment.

This allows you to use a single domain and direct incoming HTTP requests to a service with respect to the request's path.

INFO

Currently, defining only HTTP routes for domains are supported. It is planned to provide TLS routes which enable you to connect services over TCP with TLS like databases or cache services.

Please note that there is no limitation in terms of accessing services over TCP internally.

At service level, you can:

• Define the ports your service listens on. A service can listen on multiple ports.
• Directly expose it to internet with a domain provided to you by Yelken. You do not have to have a custom domain to access your services through internet.

For more information about project and service networking, please check the following documentations.

• Domains & Routes
• Service