![]() There are two ways of building kubemark: 1) via Dockerfile and 2) via bazel. In CI/CD tests we use the 1) way and use debian:jessie as the base image. But if you build kubemark via bazel it will use the discouraged busybox base image. This PR fixes that by using debian:jessie everywehre and pinning exact sha version to make the kubemark image hermetic. |
||
---|---|---|
.. | ||
addons | ||
gce | ||
images | ||
juju | ||
kubemark | ||
kubernetes-anywhere | ||
log-dump | ||
pre-existing | ||
skeleton | ||
BUILD | ||
clientbin.sh | ||
common.sh | ||
get-kube-binaries.sh | ||
get-kube.sh | ||
kube-down.sh | ||
kube-up.sh | ||
kube-util.sh | ||
kubeadm.sh | ||
kubectl.sh | ||
OWNERS | ||
README.md | ||
restore-from-backup.sh | ||
test-e2e.sh | ||
test-network.sh | ||
test-smoke.sh | ||
validate-cluster.sh |
Cluster Configuration
Deprecation Notice: This directory has entered maintenance mode and will not be accepting new providers. 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 control plane 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.