Commit Graph

17 Commits

Author SHA1 Message Date
George Kraft
fed74b7299 juju: Add kubelet-extra-config to kubernetes-worker (#145) 2018-08-27 12:56:25 +00:00
Kevin W Monroe
800d016dd4 new snapd_refresh config to control snapd refresh frequency (#141)
* add snapd_refresh config and handlers to k8s-master and -worker

* lint readmes

* add snapd_refresh doc to the readme; make "max" less specific

* adjust wording to note snapd_refresh only affects store snaps
2018-08-27 12:56:25 +00:00
Konstantinos Tsakalozos
7d96095e68 Preparing for 1.11 release and update ingress image to 0.16.1 2018-06-28 17:51:09 +03:00
Kubernetes Submit Queue
5bde5a5ac8 Merge pull request #63845 from paulgear/master
Automatic merge from submit-queue (batch tested with PRs 65301, 65291, 65307, 63845, 65313). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

Add option to control SSL chain completion

**What this PR does / why we need it**:

This adds templated support to the kubernetes-worker juju charm for the --enable-ssl-chain-completion option on the ingress proxy.  It defaults to false, to ensure that production sites are not reliant on OCSP or DNS in order to function.

**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
Fixes #

**Special notes for your reviewer**:

**Release note**:

```release-note
kubernetes-worker juju charm: Added support for setting the --enable-ssl-chain-completion option on the ingress proxy.  "action required": if your installation relies on supplying incomplete certificate chains and using OCSP to fill them in, you must set "ingress-ssl-chain-completion" to "true" in your juju configuration.
```
2018-06-22 03:08:17 -07:00
calvinh
7322f7f137 fixed branch and changed values to true 2018-06-01 18:03:11 +01:00
calvinhartwell
b232f04b4c changed the default value for allow-privileged for the kubelet (kubernetes-worker) based on new standard for 1.10 release 2018-05-21 17:34:05 +01:00
Paul Gear
31598860e3 Add option to control SSL chain completion 2018-05-15 15:44:08 +10:00
Konstantinos Tsakalozos
ad560291a2 Configure the default channel to 1.10/stable 2018-04-04 16:30:54 +03:00
Mike Wilson
b04a88cc9e Adding support for changing default backend and nginx container images 2018-01-19 16:40:57 -05:00
Konstantinos Tsakalozos
f2da078168 Pointing juju charms to 1.9 2017-12-19 14:48:05 +02:00
George Kraft
ca9076cf0f Add docker-logins config to kubernetes-worker 2017-11-20 12:52:34 -06:00
George Kraft
9036d07cb8 Add extra-args configs to kubernetes-worker charm 2017-11-08 12:49:37 -06:00
George Kraft
80f06ffee7 Bump default snap channel to 1.8/stable in juju charms 2017-10-04 13:26:14 -05:00
Konstantinos Tsakalozos
ca0f042854 Set default snap channel on charms to 1.7 stable 2017-07-13 16:24:48 +03:00
Rye Terrell
ca4afd8773 Update CDK charms to use snaps 2017-04-14 10:43:00 -05:00
Tim Van Steenburgh
c87ac5ef2e Enable gpu mode if gpu hardware detected.
layer-nvidia-cuda does the hardware detection and sets a state that the
worker can react to.

When gpu is available, worker updates config and restarts kubelet to
enable gpu mode. Worker then notifies master that it's in gpu mode via
the kube-control relation.

When master sees that a worker is in gpu mode, it updates to privileged
mode and restarts kube-apiserver.

The kube-control interface has subsumed the kube-dns interface
functionality.

An 'allow-privileged' config option has been added to both worker and
master charms. The gpu enablement respects the value of this option;
i.e., we can't enable gpu mode if the operator has set
allow-privileged="false".
2017-03-23 12:01:23 -04: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