We have released the 1.5.3 version of the Canonical Distribution of Kubernetes!
Kubernetes 1.5.3 is a patch release comprised of mostly bugfixes, and we encourage you to check out the release notes < https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG.md#changelog-since-v152 >. Getting Started: Here’s the simplest way to get a Kubernetes 1.5.3 cluster up and running on an Ubuntu 16.04 system: sudo snap install conjure-up --classic 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 < https://kubernetes.io/docs/getting-started-guides/ubuntu/local/> for localhost-specific considerations. For production grade deployments and cluster lifecycle management it is recommended to read the full Canonical Distribution of Kubernetes documentation <https://kubernetes.io/docs/getting-started-guides/ubuntu/>. Home page: https://jujucharms.com/canonical-kubernetes/ Source code: https://github.com/kubernetes/kubernetes/tree/master/cluster/juju How to upgrade: With your Kubernetes model selected, you can deploy the new 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 We have documented the upgrade scenarios in the Kubernetes documentation. If your cluster is running pods you should upgrade with a Blue/Green strategy outlined in the Upgrade documentation: < https://kubernetes.io/docs/getting-started-guides/ubuntu/upgrades/> 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 changes to the component names. 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.3 release of the Canonical Distribution of Kubernetes. Changes in this release: - Support for Kubernetes v1.5.3 General Fixes: - Fix some status messages to more accurately reflect the cluster state. <https://github.com/kubernetes/kubernetes/pull/40691> - Clone the appropriate branch to get the right addon templates for a release when building the kubernetes-master charm. <https://github.com/kubernetes/kubernetes/pull/41251> - Make the python code in cluster/juju pass flake8 lint tools cleanly. <https://github.com/kubernetes/kubernetes/pull/41256> - Make the kubernetes master sync with other masters for better HA support. <https://github.com/kubernetes/kubernetes/pull/41351> - Update the actions to run with python3. <https://github.com/kubernetes/kubernetes/pull/42058> - Disable anonymous authorization on kubelet <https://github.com/kubernetes/kubernetes/pull/41919> (Thanks to community member @raesene for pointing this out!) Etcd specific changes: - Add the ability to attach NRPE to etcd for monitoring with an external Nagios server. <https://github.com/juju-solutions/layer-etcd/pull/74> - Add the debug action to the etcd charm that makes it easier to collect debug information in the field. <https://github.com/juju-solutions/layer-etcd/pull/76> Changes to the bundles: - Update conjure-up information the CDK bundle readme. <https://github.com/juju-solutions/bundle-canonical-kubernetes/pull/214> - Update conjure-up information in the Kubernetes core bundle readme. <https://github.com/juju-solutions/bundle-canonical-kubernetes/pull/215> Test results: The Canonical Distribution of Kubernetes is a running daily tests to verify it works with the upstream code. As part of the Kubernetes test infrastructructure we upload daily test runs. The test results are available on the dashboard. Follow along with our progress here: https://k8s-gubernator.appspot.com/builds/canonical-kubernetes-tests/logs/kubernetes-gce-e2e-node/ How to contact us: We're normally found in the Kubernetes Slack channels and attend these Special Interest Group (SIG) meetings regularly: - sig-cluster-lifecycle < https://kubernetes.slack.com/messages/sig-cluster-lifecycle/> - sig-cluster-ops <https://kubernetes.slack.com/messages/sig-cluster-ops/ > Operators are an important part of Kubernetes, we encourage you to participate with other members of the Kubernetes community! We also monitor the Kubernetes mailing lists and other community channels < http://kubernetes.io/community/>, feel free to reach out to us. As always, PRs, recommendations, and bug reports are welcome: https://github.com/juju-solutions/bundle-canonical-kubernetes
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
