mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-10-22 15:09:39 +00:00
e3ba25714f
Automatic merge from submit-queue (batch tested with PRs 40335, 40320, 40324, 39103, 40315) Splitting master/node services into separate charm layers **What this PR does / why we need it**: This branch includes a roll-up series of commits from a fork of the Kubernetes repository pre 1.5 release because we didn't make the code freeze. This additional effort has been fully tested and has results submit into the gubernator to enhance confidence in this code quality vs. the single layer, posing as both master/node. To reference the gubernator results, please see: https://k8s-gubernator.appspot.com/builds/canonical-kubernetes-tests/logs/kubernetes-gce-e2e-node/ Apologies in advance for the large commit however, we did not want to submit without having successful upstream automated testing results. This commit includes: - Support for CNI networking plugins - Support for durable storage provided by Ceph - Building from upstream templates (read: kubedns - no more template drift!) - An e2e charm-layer to make running validation tests much simpler/repeatable - Changes to support the 1.5.x series of Kubernetes **Special notes for your reviewer**: Additional note: We will be targeting -all- future work against upstream so large pull requests of this magnitude will not occur again. **Release note**: ```release-note - Splits Juju Charm layers into master/worker roles - Adds support for 1.5.x series of Kubernetes - Introduces a tactic for keeping templates in sync with upstream eliminating template drift - Adds CNI support to the Juju Charms - Adds durable storage support to the Juju Charms - Introduces an e2e Charm layer for repeatable testing efforts and validation of clusters ```
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.