Re: [ANNOUNCE] Canonical Distribution of Kubernetes - Release 1.5.2

2017-01-20 Thread Samuel Cozannet 
Awesome, thanks Chuck!!

Can't wait to try this out :)

++
Sam

On Fri, Jan 20, 2017 at 1:01 AM, Charles Butler <
charles.but...@canonical.com> wrote:

> other members of the Kubernetes community





--
Samuel Cozannet
Cloud, Big Data and IoT Strategy Team
Business Development - Cloud and ISV Ecosystem
Changing the Future of Cloud
Ubuntu   / Canonical UK LTD  / Juju

samuel.cozan...@canonical.com
mob: +33 616 702 389
skype: samnco
Twitter: @SaMnCo_23
[image: View Samuel Cozannet's profile on LinkedIn]

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

[ANNOUNCE] Canonical Distribution of Kubernetes - Release 1.5.2

2017-01-19 Thread Charles Butler 
We’re proud to announce support for Kubernetes 1.5.2 in the Canonical
Distribution of Kubernetes. This is a pure upstream distribution of
Kubernetes, designed to be easily deployable to public clouds, on-premise
(ie vsphere, openstack), bare metal, and developer laptops. Kubernetes
1.5.2 is a patch release comprised of mostly bugfixes, and we encourage you
to check out the release notes

.

Getting Started:

Here’s the simplest way to get a Kubernetes 1.5.2 cluster up and running on
an Ubuntu 16.04 system:

sudo apt-add-repository ppa:juju/stable
sudo apt-add-repository ppa:conjure-up/next
sudo apt update
sudo apt install conjure-up
conjure-up kubernetes

During the installation conjure-up will ask you what cloud you want to
deploy on and prompt you for the proper credentials. If you’re deploying to
local containers (LXD) see these instructions
 for
localhost-specific considerations.

For production grade deployments and cluster lifecycle management it is
recommended to read the full Canonical Distribution of Kubernetes
documentation .

Home page: https://jujucharms.com/canonical-kubernetes/

Source code: https://github.com/juju-solutions/bundle-canonical-kubernetes

How to upgrade

With your kubernetes model selected, you can deploy the bundle to upgrade
your cluster if on the 1.5.x series of kubernetes. At this time releases
before 1.5.x have not been tested. Depending on which bundle you have
previously deployed, run:

juju deploy canonical-kubernetes

or

juju deploy kubernetes-core

If you have made tweaks to your deployment bundle, such as deploying
additional worker nodes as a different label, you will need to manually
upgrade the components. The following command list assumes you have made no
tweaks, but can be modified to work for your deployment.

juju upgrade-charm kubernetes-master

juju upgrade-charm kubernetes-worker

juju upgrade-charm etcd

juju upgrade-charm flannel

juju upgrade-charm easyrsa

juju upgrade-charm kubeapi-load-balancer


This will upgrade the charm code, and the resources to kubernetes 1.5.2
release of the Canonical Distribution of Kubernetes.
New features:

   -

   Full support for Kubernetes v1.5.2.


General Fixes

   -

   #151
   
   #187
   

   It wasn’t very transparent to users that they should be using conjure-up
   when locally developing, conjure-up is now the defacto default mechanism
   for deploying CDK.
   -

   #173
   
   Resolved permissions on ~/.kube on kubernetes-worker units
   -

   #169
   
   Tuned the verbosity of the AddonTacticManager class during charm layer
   build process
   -

   #162
   
   Added NO_PROXY configuration to prevent routing all requests through
   configured proxy [by @axinojolais ]
   -

   #160
   
   Resolved an error by flannel sometimes encountered during
   cni-relation-changed [by @spikebike ]
   -

   #172
   
   Resolved sporadic timeout issues between worker and apiserver due to nginx
   connection buffering [by @axinojolais ]
   -

   #101  Work-around
   for offline installs attempting to contact pypi to install docker-compose
   -

   #95 Tuned
   verbosity of copy operations in the debug script for debugging the debug
   script.


Etcd layer-specific changes

   -

   #72  #70
    Resolved a
   certificate-relation error where etcdctl would attempt to contact the
   cluster master before services were ready [by @javacruft
   ]


Unfiled/un-scheduled fixes:

   -

   #190
   
   Removal of assembled bundles from the repository. See bundle
   author/contributors notice below


Additional Feature(s):

   -

   We’ve open sourced our release management process scripts we’re using in
   a juju deployed jenkins model. These scripts contain the logic we’ve been
   running by hand, and give users a clear view into how we build, package,
   test, and release the CDK. You can see t