Commit Graph

9 Commits

Author SHA1 Message Date
Konstantinos Tsakalozos
86a036feb1 Adding old juju maintainers 2017-07-27 15:42:36 +03:00
Konstantinos Tsakalozos
68b42c3b88 Update maintainers for Juju charm layers 2017-07-25 13:09:09 +03:00
Rye Terrell
7c06da5b0e prevent unsetting of nonexistent previous port in kubeapi-load-balancer charm 2017-07-17 12:22:54 -05:00
Rye Terrell
ece0461cce use port configuration 2017-07-14 13:31:47 -05:00
Konstantinos Tsakalozos
0b01cd743b Improve security of Juju deployed clusters 2017-06-27 12:19:21 +03:00
Marco Ceppi
d3428ef3a4 Add metric collection to charms for autoscalling 2017-04-13 16:02:13 -05:00
Matt Bruzek
71f583ebe4 Adding more proxy options and header to nginx load-balancer. 2017-03-23 16:14:02 -05:00
axino
83766d2894 add nrpe-external-master relation to kubernetes-master and kubernetes-worker
For now, the checks are very basic and only check if the systemd
services are running properly.
2017-02-26 10:37:34 -06:00
Matt Bruzek
3fcf279cfb Splitting master/node services into separate charm layers
This branch includes a rollup 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

Additional note: We will be targeting -all- future work against upstream
so large pull requests of this magnitude will not occur again.
2017-01-24 09:42:25 -06:00