network: default network.enable to services.hyperhive.enable
This commit is contained in:
parent
8e50ddf016
commit
3db51deace
1 changed files with 13 additions and 9 deletions
|
|
@ -15,18 +15,22 @@ in
|
||||||
options.services.hyperhive.network = {
|
options.services.hyperhive.network = {
|
||||||
enable = lib.mkOption {
|
enable = lib.mkOption {
|
||||||
type = lib.types.bool;
|
type = lib.types.bool;
|
||||||
default = false;
|
default = config.services.hyperhive.enable;
|
||||||
example = true;
|
defaultText = lib.literalExpression "config.services.hyperhive.enable";
|
||||||
|
example = false;
|
||||||
description = ''
|
description = ''
|
||||||
Stand up the hive-internal bridge + dnsmasq resolver.
|
Stand up the hive-internal bridge + dnsmasq resolver.
|
||||||
Off by default while v1 phases in. When enabled:
|
Defaults to `config.services.hyperhive.enable` so it comes
|
||||||
a bridge interface (`bridgeName`) appears on the host with
|
on automatically with the rest of hyperhive. Requires
|
||||||
`bridgeIp` assigned, and the hive-gateway container runs a
|
`services.hyperhive.domain` to be set — the dnsmasq resolver
|
||||||
dnsmasq listening on that IP for `<hive-domain>` +
|
is authoritative for `<hive-domain>` and its sub-domains.
|
||||||
|
When enabled: a bridge interface (`bridgeName`) appears on the
|
||||||
|
host with `bridgeIp` assigned, and the hive-gateway container
|
||||||
|
runs a dnsmasq listening on that IP for `<hive-domain>` +
|
||||||
sub-domains. Agent containers still default to shared host
|
sub-domains. Agent containers still default to shared host
|
||||||
netns at v1 — the endpoint is up but only used once #14
|
netns — the endpoint is up but only used once
|
||||||
lands and flips containers to a private netns + veth peer
|
`isolateContainers = true` flips containers to private netns
|
||||||
on this bridge.
|
+ veth peers on this bridge.
|
||||||
'';
|
'';
|
||||||
};
|
};
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue