Service registry configuration | General configuration
Upstream attributes help manage gateway routing and protection rules for services registered behind boruta. They define where a request is forwarded, which public paths expose the service, and which security rules the gateway applies before proxying traffic.
Service registry upstreams can be customized through either the Administration API, the user interface, or static configuration files. The configuration is organized around:
- General configuration
- URIs
- Authorization
- Security
General configuration parameters
Node defines where the upstream is active. global upstreams are used by the main gateway entrypoint. A service registry node name makes the upstream active for the matching sidecar or microgateway node.
Virtual host restricts matching to requests received for a specific host. Leave it empty to match any host. When both a virtual-host upstream and a path-only upstream can match, the virtual-host upstream is selected first.
Scheme defines the protocol used to reach the upstream service. Accepted values are http and https.
Host is the network host of the upstream service.
Port is the network port of the upstream service.
User interface
The general configuration tab defines where the upstream is active and which backend service the gateway forwards traffic to.
