Resources / DNSService

DNSService

An authoritative DNS server for one zone inside one VPC; members are registered automatically.

Overview

APInetwork.etorm.com/v1alpha1
Resourcednsservices (cluster-scoped inside its cluster)
Short namesdns
Available inproject clusters only
Statuswritten by a controller through /status

Minimal example

apiVersion: network.etorm.com/v1alpha1
kind: DNSService
metadata:
  name: example
spec:
  vpcRef:
    name: "<name>"

Spec

FieldTypeRequiredDefaultAllowedDescription
vpcRefreference to VPCyesThe VPC served. One DNS service per VPC.
zonestringup to 253 charactersThe zone served; defaults to <vpc>.<project>.etorm.internal.
registerAccountsbooleantrueAdd <account>.<zone> for every member automatically.
forwarderslist of stringup to 4 itemsPublic IPv4 resolvers for names outside the zone; without any, outside names are refused.
recordslist of objectup to 512 itemsRecords of the zone; names are relative to it, @ is the apex. Databases and message brokers on the VPC get names automatically (see spec 0012).
records[].namestringyeslength 1 to 253Name relative to the zone; @ is the apex.
records[].typestring (one of)yesA, AAAA, CNAME, TXTRecord type. A record that follows a resource (followRef) is AAAA.
records[].valuestringlength 1 to 1000The record's data. Exactly one of value and followRef.
records[].ttlinteger600 to 86400Seconds a resolver may keep the answer. A record that follows a resource is served with at most 5.
records[].followRefobjectInstead of value: the name always answers with the current address of a resource in this project, so it follows a failover. Without an address (the resource is not running) the name does not exist.
records[].followRef.kindstring (one of)yesDatabase, MessageBrokerKind of the resource.
records[].followRef.namestringyeslength 1 to 63Name of the resource.
records[].followRef.rolestring (one of)yesprimary, replicas, serving, endpointsDatabase: primary (the node that accepts writes) or replicas (read-only nodes, else the primary). MessageBroker: serving (the node that serves now) or endpoints (every node).

Status

FieldTypeRequiredDefaultAllowedDescription
phasestringPending until the VPC is Ready, then Ready or Failed.
recordCountintegerNumber of records served, explicit and automatic.
configobject (free-form)The complete rendered configuration the gateway serves: vni, serverIp, addresses, zone, forwarders, records.
conditionslist of objectDetailed state, one entry per aspect; Ready says whether the object is usable.
conditions[].typestring
conditions[].statusstring
conditions[].reasonstring
conditions[].messagestring

Columns in listings

ColumnFrom
VPC.spec.vpcRef.name
Zone.status.config.zone
Server.status.config.serverIp
Records.status.recordCount
Phase.status.phase

Related guides

All resources