Closed majst01 closed 7 months ago
During implementation a few questions came up:
DNSSEC
or DNSOverTLS
?FallbackNTP
?During implementation a few questions came up:
- Do we want to support things like
DNSSEC
orDNSOverTLS
? should be possible to define- timesyncd does not support non-standard ports. How should we handle wrong port configs? a. fail generation of files completely b. generate everything, skip wrong port, only fail if no port is valid c. just use port 123 and log that the port was misconfigured (preferred) d. always use port 123 without logging
Then port must not be specified for DNS in my opinion, use the same struct for all 3 types (DNS, NTP and Registry) is probably not a good idea
- Do we want to support
FallbackNTP
?
dont think so, if 2 or more ntp servers are defined, this should be enough
Looking at other cloudprofiles, they do simply add only the addresses to the cloudprofile:
Can this be closed?
add this into webhook/controlplane/ensurer.go
Implement the EnsureAdditionalFiles Interface.
Related: https://github.com/fi-ts/proxy-services/issues/4