EKS DNS Workaround

aws_eks_config

# file: aws_eks_config.yml
# AWS EKS ClusterConfig used to setup the BinderHub / JupyterNotebooks K8s cluster
# using a workaround from https://discourse.jupyter.org/t/binder-deployed-in-aws-eks-domain-name-resolution-errors/766/10
# to fix broken DNS resolution
--- 
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig

metadata:
  name: eks-dns-production
  region: eu-central-1

nodeGroups:
  - name: eks-dns-workers-production
    instanceType: t2.small
    minSize: 0
    maxSize: 4
    desiredCapacity: 2
    preBootstrapCommands:
        # Replicate what --enable-docker-bridge does in /etc/eks/bootstrap.sh
        # Enabling the docker bridge network. We have to disable live-restore as it
        # prevents docker from recreating the default bridge network on restart
       - "cp /etc/docker/daemon.json /etc/docker/daemon_backup.json"
       - "echo -e '.bridge=\"docker0\" | .\"live-restore\"=false' >  /etc/docker/jq_script"
       - "jq -f /etc/docker/jq_script /etc/docker/daemon_backup.json | tee /etc/docker/daemon.json"
       - "systemctl restart docker"

Workaround to fix docker-on-docker dns resolution errors at AWS EKS
use: eksctl create cluster --config-file aws_eks_config.yml
Woraround based on the comments at the Jupyter Forum: https://discourse.jupyter.org/t/binder-deployed-in-aws-eks-domain-name-resolution-errors/766