mirror of
https://github.com/kubernetes/kubernetes.git
synced 2026-03-02 21:50:39 -05:00
Automatic merge from submit-queue (batch tested with PRs 39169, 40719, 38954, 40808, 40689) Exports KUBE_TEMP for use in Vagrantfile In #40147, the logic for setting `KUBE_TEMP` was refactored into `common.sh`. However, it was overlooked that `KUBE_TEMP` [needs to be exported for vagrant to work properly](https://github.com/kubernetes/kubernetes/pull/40147/files#diff-b19d3d93456020e2168c7f304f722969). This PR restores the `export` so that `Vagrantfile` can use `ENV["KUBE_TEMP"]` properly. 👀 @rthallisey @shyamjvs @timothysc |
||
|---|---|---|
| .. | ||
| 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 | ||
| windows | ||
| BUILD | ||
| clientbin.sh | ||
| 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 | ||
| OWNERS | ||
| README.md | ||
| restore-from-backup.sh | ||
| test-e2e.sh | ||
| test-network.sh | ||
| test-smoke.sh | ||
| update-storage-objects.sh | ||
| validate-cluster.sh | ||
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.