mirror of https://github.com/k3s-io/k3s
![]() Automatic merge from submit-queue
Do not cache hyperkube package installation
**What this PR does / why we need it**:
The hyperkube build process could use a cached layer containing out of date packages. For example, the v1.4.0 image contains packages with security vulnerabilities, which should have been available as of the release build date.
This was surfaced from quay.io/clair scanning the hyperkube images:
|
||
---|---|---|
.. | ||
addons | ||
aws | ||
azure | ||
azure-legacy | ||
centos | ||
gce | ||
gke | ||
images | ||
juju | ||
kubemark | ||
lib | ||
libvirt-coreos | ||
local | ||
mesos/docker | ||
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 | ||
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
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.