istio-coredns-plugin

Original repository.
https://github.com/istio-ecosystem/istio-coredns-plugin.

UPDATE: этот плагин больше не нужен с версии Istio 1.8. DNS встроен в агент istio в коляске. По умолчанию в профиле включен Sidecar DNSpreview. Вы также можете включить его вручную, установив следующую конфигурацию в операторе istio

UPDATE: This plugin is no longer necessary as of Istio 1.8. DNS is built into the istio agent in the sidecar. Sidecar DNS is enabled by default in the preview profile. You can also enable it manually by setting the following config in the istio operator

  meshConfig:
    defaultConfig:
      proxyMetadata:
        ISTIO_META_DNS_CAPTURE: "true"
        ISTIO_META_PROXY_XDS_VIA_AGENT: "true"

This repository is no longer maintained.

istio-coredns-plugin

CoreDNS gRPC plugin to serve DNS records out of Istio ServiceEntries.

The plugin runs as a separate container in the CoreDNS pod, serving DNS A records over gRPC to CoreDNS.

Hosts in service entries which also contain addresses will resolve to those addresses, as long as they're host addresses not CIDR ranges.

Service entries without addresses will by default not resolve, unless the --default-address flag is given, in which case that address will be used for address-less service entries.

Wildcard hosts in the service entries will also resolve appropriately. E.g., consider the following service entry:

apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
spec:
  hosts:
  - *.google.com
  addresses:
  - 17.17.17.17
  - 9.9.9.9
  resolution: STATIC
  endpoints:
  - ...

A query against the coreDNS pod would return the following:

$ dig +short @<coreDNSIP> A maps.google.com
17.17.17.17
9.9.9.9

$ dig +short @<coreDNSIP> A mail.google.com
17.17.17.17
9.9.9.9

$ dig +short @<coreDNSIP> A google.com
 # no response

Usage

Deploy the core-DNS service in the istio-system namespace

kubectl apply -f coredns.yaml

Update the kube-dns config map to point to this coredns service as the upstream DNS service for the *.global domain. You will have to find out the cluster IP of coredns service and update the config map (or write a controller for this purpose!).

E.g.

apiVersion: v1
kind: ConfigMap
metadata:
  name: kube-dns
  namespace: kube-system
data:
  stubDomains: |
    {"global": ["10.2.3.4"]}