kops/cmd/kops-controller
justinsb 6133250046 gossip: support resolution of k8s.local names from pods
We add the hosts plugin to CoreDNS, and we populate a ConfigMap from
kops-controller (when in gossip mode).

This enables resolution of the internal apiserver DNS name from Pods,
even when gossip mode (k8s.local) is in use.  This should fix the
failing e2e tests which are assuming that the name in the JWT token is
resolvable from inside the cluster.

This is also a possible step towards a simpler gossip mode, now that
we have a central controller.
2021-11-19 11:02:15 -05:00
..
controllers gossip: support resolution of k8s.local names from pods 2021-11-19 11:02:15 -05:00
hack Fix boilerplate: headers & packages 2019-09-25 12:48:14 -04:00
pkg gossip: support resolution of k8s.local names from pods 2021-11-19 11:02:15 -05:00
BUILD.bazel gossip: support resolution of k8s.local names from pods 2021-11-19 11:02:15 -05:00
OWNERS Add a couple more "area" labels 2020-06-18 07:01:05 -05:00
PROJECT Fill out kops controller functionality 2019-09-25 12:04:34 -04:00
main.go gossip: support resolution of k8s.local names from pods 2021-11-19 11:02:15 -05:00