d79af8cb35
Automatic merge from submit-queue Create a get-kube-binaries script to download client/server tarballs **What this PR does / why we need it**: One step towards removing all server and client binary tarballs from the kubernetes.tar.gz release tarball. If someone uses `cluster/get-kube.sh` (or https://get.k8s.io, which needs to be synced), this will automatically download the necessary client and server tarballs as part of the flow, though as of right now this will largely be a no-op. (When we remove the client/server binaries, it will have more of an effect.) I've opted to put this script inside the release tarball (rather than in get-kube.sh), since each release probably has a better idea which platforms/architectures/etc it supports. Further improvements would probably include omitting downloading the server tarball entirely unless needed, but this seems like a reasonable first step. This also fixes some errors in get-kube.sh, and remove client architectures we don't officially support. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # x-ref #28629 and #28435 **Special notes for your reviewer** Assigning to Tim semi-arbitrarily for now, but please reassign as you feel appropriate. **Release note**: We probably don't need a release note yet. We'll definitely want one when we remove the server and client binaries. cc @jbeda @luxas @david-mcmahon @zmerlynn @gajju26
Cluster Configuration
Deprecation Notice: This directory has entered maintainence 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.