Automatic merge from submit-queue Juju automated charm testing shouldn't bootstrap **What this PR does / why we need it**: **Special notes for your reviewer**: This controls the tooling around our test automation. This is a low impact change to the k8s codebase, that will have a big impact on our CI infrastructure. **Release note**: ```release-note release-note-none ``` Juju bootstrapping is an act of cost. This should be an explicit action by the tooling surrounding bundle-tester when testing a charm. Setting bootstrap:false will allow us to get faster feedback at lower cost when running the kubernetes charm under ci.
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.