mirror of https://github.com/k3s-io/k3s
![]() Automatic merge from submit-queue [Federation][init-11.2] use USE_KUBEFED env var to choose bw old and new federation deployment This is continuation of #35961 USE_KUBEFED variable is used for deploying federation control plane. if not defined, federation will be brought up using old method i.e scripts. Have verified that federation comes up using the old method, using following steps ``` $ export FEDERATION=true $ export E2E_ZONES="asia-east1-c" $ export FEDERATION_PUSH_REPO_BASE=gcr.io/<my-project> $ KUBE_RELEASE_RUN_TESTS=n KUBE_FASTBUILD=true go run hack/e2e.go -v -build $ build-tools/push-federation-images.sh $ go run hack/e2e.go -v --up ``` Should merge #35961 before this PR @madhusudancs |
||
---|---|---|
.. | ||
addons | ||
aws | ||
azure | ||
azure-legacy | ||
centos | ||
gce | ||
gke | ||
images | ||
juju | ||
kubemark | ||
lib | ||
libvirt-coreos | ||
local | ||
openstack-heat | ||
ovirt | ||
photon-controller | ||
rackspace | ||
saltbase | ||
skeleton | ||
ubuntu | ||
vagrant | ||
vsphere | ||
OWNERS | ||
README.md | ||
common.sh | ||
get-kube-binaries.sh | ||
get-kube-local.sh | ||
get-kube.sh | ||
kube-down.sh | ||
kube-push.sh | ||
kube-up.sh | ||
kube-util.sh | ||
kubeadm.sh | ||
kubectl.sh | ||
log-dump.sh | ||
options.md | ||
restore-from-backup.sh | ||
test-e2e.sh | ||
test-network.sh | ||
test-smoke.sh | ||
update-storage-objects.sh | ||
validate-cluster.sh |
README.md
Cluster Configuration
Deprecation Notice: This directory has entered maintenance mode and will not be accepting new providers. Please submit new automation deployments to kube-deploy. Deployments in this directory will continue to be maintained and supported at their current level of support.
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.