mirror of https://github.com/k3s-io/k3s
![]() This ensures nfs-common is installed on GCE, and provides a more functional explanation/example. I launched two replication controllers so that there were busybox pods to poke around at the NFS volume, and so that the later wget actually works (the original example would have to work on the node, or need some other access to the container network). After switching to two controllers, it actually makes more sense to use PV claims, and it's probably a configuration that makes more sense for indirection for NFS anyways. |
||
---|---|---|
.. | ||
addons | ||
aws | ||
centos | ||
gce | ||
gke | ||
images | ||
juju | ||
kubemark | ||
libvirt-coreos | ||
mesos/docker | ||
ovirt | ||
rackspace | ||
saltbase | ||
ubuntu | ||
vagrant | ||
vsphere | ||
README.md | ||
common.sh | ||
get-kube.sh | ||
kube-down.sh | ||
kube-env.sh | ||
kube-push.sh | ||
kube-up.sh | ||
kube-util.sh | ||
kubectl.sh | ||
options.md | ||
test-e2e.sh | ||
test-network.sh | ||
test-smoke.sh | ||
update-storage-objects.sh | ||
validate-cluster.sh |
README.md
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.