Module backend_tls 

Available on crate feature gateway-api only.

BackendTLSPolicy: which Service ports rws reaches over TLS, trusting which CAs, under which name. A policy targets Services in its namespace (optionally one port, by name); between two policies for the same target the older wins and the other is Conflicted, and a port’s own policy beats one for the whole Service. The client configuration is built once per distinct policy content and shared.

Structs

BackendTls

How rws connects to a backend a policy covers.

Evaluated

A policy’s verdict: accepted (with its configuration) or why not.

Functions

build

The client configuration for validation, trusting ca_pem (the platform’s roots when None).

evaluate

Every policy’s verdict, by (namespace, name), oldest first.

for_service

The policy for a Service port: the one naming the port, else the one for the whole Service. None: plain HTTP; Some(Err): a policy covers it but isn’t usable — requests fail rather than go out in the clear.