ad63ad7d40
Verified with k/k and k/test-infra. - restore-from-backup.sh Performs restoration of etcd snapshots and the logic seems valid on a quick look, but doesn't seem to be used anywhere in our infra. I suspect this is used on demand for local testing, but /cluster root doesn't seem like the right place for it at this point. - test-*.sh Gikgo related calls but these bash scripts seem unused in the infra. |
||
|---|---|---|
| .. | ||
| 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 | ||
| kubectl.sh | ||
| OWNERS | ||
| README.md | ||
| 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.