d8d1468f03
* 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. |
||
|---|---|---|
| .. | ||
| cloudinit | ||
| ami.tf | ||
| ingress.tf | ||
| outputs.tf | ||
| variables.tf | ||
| workers.tf | ||