Ayaz Ahmed Khan 89847d5684 Explicitly defines the --kubelet-preferred-address-types parameter ... to the API server configuration. This solves the problem where if you have non-resolvable node names, and try to scale the server by adding new nodes, kubectl commands start to fail for newly added nodes, giving a TCP timeout error when trying to resolve the node hostname against a public DNS.		2018-03-05 15:25:14 +01:00
..
manifests	Explicitly defines the --kubelet-preferred-address-types parameter	2018-03-05 15:25:14 +01:00
known_users.csv.j2	kubeadm support (#1631)	2017-09-13 19:00:51 +01:00
kube-controller-manager-kubeconfig.yaml.j2	basic rbac support	2017-07-17 19:29:59 +08:00
kube-scheduler-kubeconfig.yaml.j2	basic rbac support	2017-07-17 19:29:59 +08:00
kube-scheduler-policy.yaml.j2	Fix for Issue #2141 - added policy file	2018-01-12 07:15:35 +00:00
kubeadm-config.yaml.j2	Added apiserver extra args variable for kubeadm config (#2291)	2018-02-12 10:29:46 +03:00
kubectl-kubeconfig.yaml.j2	Add HA/LB endpoints for kube-apiserver	2016-07-25 17:25:45 +02:00