Google Cloud Logging (AKA Stackdriver Logs) interprets the default
logrus log format as "error" severity even when `level=info` is
present in the log output: ensure that the normal startup log
is not parsed as an error by setting the JSON formatter first.
Signed-off-by: Nathan J Mehl <n@oden.io>
Google Cloud Logging (AKA Stackdriver Logs) interprets the default
logrus log format as "error" severity even when `level=info` is
present in the log output: ensure that the normal startup log
is not parsed as an error by setting the JSON formatter first.
Signed-off-by: Nathan J Mehl <n@oden.io>
Note that some URLs were not updated, as there is not yet equivalent
pages on the `ans.co.uk` domain.
Signed-off-by: Rick Henry <rick.henry@assureddigitaltech.com>
If external-dns.alpha.kubernetes.io/target annotation is present on a
pod, it's value will be used as the target for the headless service.
If annotation external-dns.alpha.kubernetes.io/access=public is present,
NodeExternalIP of the node running the pod is used as the target for the
headless service.
Based on feedback having both the configuration file and command line
flags for the BlueCat provider will be used. Therefore update the
documentaiton to reflect that the JSON configuration file for the
BlueCat provider is not deprecated.
New configuration options created for setting the DNS deployment type,
as well as the DNS server to deploy. A DNS server name must be provided
and a valid DNS deployment type must be set in order for a deployment to be
initiated.
Currently, the only supported deployment type is "full deploy", however
"quick deploy" and "selective deploy" could be added in the future.
Annotation values may not be an integer, they must be handled as a
string. The current example tested on k8s 1.20.13 generates this error
message:
json: cannot unmarshal number into Go struct field ObjectMeta.metadata.annotations of type string