mirror of https://github.com/k3s-io/k3s
![]() When MASTER_RESERVED_IP is set to elastic IP from AWS, then aws/util.sh will associate it with master instance and assign it to KUBE_MASTER_IP. If no MASTER_RESERVED_IP is set, new elastic ip will be requested from amazon. This allows cluster certificates to be generated for an IP that doesn't change between stopping & starting cluster instances. The requested elastic ip is not released when kube-down.sh is run. I think it is good because user could have created DNS records and it would be bad if the IP was removed. He can reuse it next time through MASTER_RESERVED_IP when setting up cluster again. |
||
---|---|---|
.. | ||
addons | ||
aws | ||
azure | ||
gce | ||
gke | ||
images | ||
juju | ||
libvirt-coreos | ||
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-network.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.