mirror of https://github.com/k3s-io/k3s
![]() Automatic merge from submit-queue Parameterize the binary path and host arch for the hyperkube image As the [cluster/images/hyperkube/README.md](https://github.com/kubernetes/kubernetes/tree/master/cluster/images/hyperkube) shows, I run the command: `make build VERSION=test ARCH=ppc64le`, but got the below errors, so this PR will fix it. ``` ARCH=ppc64le cp -r ./* /tmp/hyperkubeTFbYrI mkdir -p /tmp/hyperkubeTFbYrI/cni-bin cp ../../../_output/dockerized/bin/linux/ppc64le/hyperkube /tmp/hyperkubeTFbYrI cp: cannot stat '../../../_output/dockerized/bin/linux/ppc64le/hyperkube': No such file or directory Makefile:62: recipe for target 'build' failed make: *** [build] Error 1 ``` |
||
---|---|---|
.. | ||
addons | ||
aws | ||
centos | ||
gce | ||
gke | ||
images | ||
juju | ||
kubemark | ||
lib | ||
libvirt-coreos | ||
local | ||
openstack-heat | ||
photon-controller | ||
saltbase | ||
skeleton | ||
vagrant | ||
vsphere | ||
windows | ||
BUILD | ||
OWNERS | ||
README.md | ||
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 | ||
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.