gateway reaches the controller over tls with its own client leaf when the tcp listener is on
This commit is contained in:
parent
17fffaae79
commit
187ed82de0
1 changed files with 768 additions and 49 deletions
|
|
@ -291,6 +291,22 @@ in
|
|||
'';
|
||||
};
|
||||
|
||||
verifiedProxyToWithClientCert = lib.mkOption {
|
||||
type = lib.types.functionTo (lib.types.functionTo lib.types.lines);
|
||||
internal = true;
|
||||
readOnly = true;
|
||||
description = ''
|
||||
Read-only: `name -> { certificate, key } -> lines`. The
|
||||
`verifiedProxyTo` lines plus `proxy_ssl_certificate` and
|
||||
`proxy_ssl_certificate_key`, for an upstream that requires the
|
||||
gateway to present a client certificate. `certificate` and `key` are
|
||||
host paths nginx can read (the key `0640` to the `nginx` group).
|
||||
|
||||
Separate from `verifiedProxyTo` so that every existing caller keeps
|
||||
rendering exactly what it rendered.
|
||||
'';
|
||||
};
|
||||
|
||||
securityHeaders = lib.mkOption {
|
||||
type = lib.types.lines;
|
||||
internal = true;
|
||||
|
|
|
|||
Loading…
Reference in a new issue