mirror of https://github.com/k3s-io/k3s
![]() Automatic merge from submit-queue Fix GKE kube-up to correctly find an IGM from a multi-zone cluster I've confirmed that this successfully brings up a cluster, fixing the immediate issue with the new e2e test. Sorry about not properly vetting it in the original PR (#24075). This does cause a warning message to be printed based on the handling of the NUM_NODES variable though, which I could fix if you guys think it's worth it: ``` Detected 6 ready nodes, found 6 nodes out of expected 3. Found more nodes than expected, your cluster may not behave correctly. ``` @quinton-hoole |
||
---|---|---|
.. | ||
addons | ||
aws | ||
azure | ||
centos | ||
cloudimages | ||
gce | ||
gke | ||
images | ||
juju | ||
kubemark | ||
lib | ||
libvirt-coreos | ||
mesos/docker | ||
ovirt | ||
rackspace | ||
saltbase | ||
ubuntu | ||
vagrant | ||
vsphere | ||
OWNERS | ||
README.md | ||
common.sh | ||
get-kube-local.sh | ||
get-kube.sh | ||
kube-down.sh | ||
kube-push.sh | ||
kube-up.sh | ||
kube-util.sh | ||
kubectl.sh | ||
log-dump.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.