Port Broker
On this page
Port Broker allows your microservices to securely expose public endpoints without opening ports on your agents.
Specifying Public Containers
When deploying
applications
and microservices, you can specify a proxy
configuration when
configuring the port mappings of your container.
If proxy
is specified and set to true
, this will open a tunnel that will forward all traffic incoming onto the port exposed by the container.
If your outbound data using Port Broker requires a specific protocol, add scheme
followed by the desired protocol.
Deploying such a configuration would result in a port being opened on a public host, and all
incoming tcp traffic would be tunneled to agent-1
, port 5000.
The public address can be retrieved in the Portal (in the Application details, and/or microservice details pages), or by using edgectl .
Below is the YAML returned when describing the microservice/application.
Deploying such a configuration would result in a port being opened on a public host, and all incoming tcp traffic would be tunneled to agent-1
, port 5000.
YAML Example
...
name: msvc-1
agent:
name: agent-1
container:
...
ports:
- internal: 80
external: 5000
proxy: true
scheme: http
...