tailscale/cmd/k8s-operator/deploy/manifests/nameserver/svc.yaml

apiVersion: v1
kind: Service
metadata:
  name: nameserver
spec:
  selector:
    app: nameserver
  ports:
  - name: udp
    targetPort: 1053
    port: 53
    protocol: UDP
  - name: tcp
    targetPort: 1053
    port: 53
    protocol: TCP
cmd/{k8s-nameserver,k8s-operator},k8s-operator: add a kube nameserver, make operator deploy it (#11919) * cmd/k8s-nameserver,k8s-operator: add a nameserver that can resolve ts.net DNS names in cluster. Adds a simple nameserver that can respond to A record queries for ts.net DNS names. It can respond to queries from in-memory records, populated from a ConfigMap mounted at /config. It dynamically updates its records as the ConfigMap contents changes. It will respond with NXDOMAIN to queries for any other record types (AAAA to be implemented in the future). It can respond to queries over UDP or TCP. It runs a miekg/dns DNS server with a single registered handler for ts.net domain names. Queries for other domain names will be refused. The intended use of this is: 1) to allow non-tailnet cluster workloads to talk to HTTPS tailnet services exposed via Tailscale operator egress over HTTPS 2) to allow non-tailnet cluster workloads to talk to workloads in the same cluster that have been exposed to tailnet over their MagicDNS names but on their cluster IPs. DNSConfig CRD can be used to configure the operator to deploy kube nameserver (./cmd/k8s-nameserver) to cluster. Updates tailscale/tailscale#10499 Signed-off-by: Irbe Krumina <irbe@tailscale.com> 2024-04-30 19:18:23 +00:00			`apiVersion: v1`
			`kind: Service`
			`metadata:`
			`name: nameserver`
			`spec:`
			`selector:`
			`app: nameserver`
			`ports:`
			`- name: udp`
			`targetPort: 1053`
			`port: 53`
			`protocol: UDP`
			`- name: tcp`
			`targetPort: 1053`
			`port: 53`
			`protocol: TCP`