typhoon/google-cloud/fedora-atomic/kubernetes/workers
Dalton Hubble d8d1468f03 Update kubelet system container image to mount /etc/hosts
* Fix kubelet port-forward on Google Cloud / Fedora Atomic
* Mount the host's /etc/hosts in kubelet system containers
* Problem: kubelet runc system containers on Atomic were not
mounting the host's /etc/hosts, like rkt-fly does on Container
Linux. `kubectl port-forward` calls socat with localhost. DNS
servers on AWS, DO, and in many bare-metal environments resolve
localhost to the caller as a convenience. Google Cloud notably
does not nor is it required to do so and this surfaced the
missing /etc/hosts in runc kubelet namespaces.
2018-04-21 18:46:56 -07:00
..
cloudinit Update kubelet system container image to mount /etc/hosts 2018-04-21 18:46:56 -07:00
ingress.tf Add Google Cloud fedora-atomic module 2018-04-21 18:46:56 -07:00
outputs.tf Add Google Cloud fedora-atomic module 2018-04-21 18:46:56 -07:00
variables.tf Add Google Cloud fedora-atomic module 2018-04-21 18:46:56 -07:00
workers.tf Add Google Cloud fedora-atomic module 2018-04-21 18:46:56 -07:00