8df33bc1a7
separated from the apiserver running locally on the master node so that it can be optionally enabled or disabled as needed. Also, fix the healthchecking configuration for the master components, which was previously only working by coincidence: If a kubelet doesn't register with a master, it never bothers to figure out what its local address is. In which case it ends up constructing a URL like http://:8080/healthz for the http probe. This happens to work on the master because all of the pods are using host networking and explicitly binding to 127.0.0.1. Once the kubelet is registered with the master and it determines the local node address, it tries to healthcheck on an address where the pod isn't listening and the kubelet periodically restarts each master component when the liveness probe fails. |
||
|---|---|---|
| .. | ||
| addons | ||
| aws | ||
| azure | ||
| gce | ||
| gke | ||
| images | ||
| juju | ||
| libvirt-coreos | ||
| mesos/docker | ||
| ovirt | ||
| rackspace | ||
| saltbase | ||
| ubuntu | ||
| vagrant | ||
| vsphere | ||
| common.sh | ||
| get-kube.sh | ||
| kube-down.sh | ||
| kube-env.sh | ||
| kube-push.sh | ||
| kube-up.sh | ||
| kube-util.sh | ||
| kubectl.sh | ||
| options.md | ||
| README.md | ||
| test-e2e.sh | ||
| test-network.sh | ||
| update-storage-objects.sh | ||
| validate-cluster.sh | ||
Cluster Configuration
The scripts and data in this directory automate creation and configuration of a Kubernetes cluster, including networking, DNS, nodes, and master components.
See the getting-started guides for examples of how to use the scripts.
cloudprovider/config-default.sh contains a set of tweakable definitions/parameters for the cluster.
The heavy lifting of configuring the VMs is done by SaltStack.