<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tim Van Steenburgh on Medium]]></title>
        <description><![CDATA[Stories by Tim Van Steenburgh on Medium]]></description>
        <link>https://medium.com/@tvansteenburgh?source=rss-cdcb4bf6c2f3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*S8GGJXp-J5ON6rTuwHFcYw.jpeg</url>
            <title>Stories by Tim Van Steenburgh on Medium</title>
            <link>https://medium.com/@tvansteenburgh?source=rss-cdcb4bf6c2f3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 23:37:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tvansteenburgh/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Private Docker Registries and the Canonical Distribution of Kubernetes]]></title>
            <link>https://medium.com/@tvansteenburgh/private-docker-registries-and-the-canonical-distribution-of-kubernetes-31cb05a9b61c?source=rss-cdcb4bf6c2f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/31cb05a9b61c</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Tim Van Steenburgh]]></dc:creator>
            <pubDate>Wed, 04 Oct 2017 16:24:13 GMT</pubDate>
            <atom:updated>2018-01-09T22:45:48.532Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BVPGrHaOJEyVTSLcUqDZyw.png" /></figure><p>How do I use a private image registry with my Kubernetes cluster? How do I set up my own registry? Let’s look at how to perform these tasks on the <a href="https://www.ubuntu.com/kubernetes">Canonical Distribution of Kubernetes</a> (CDK).</p><h3>Using an Existing Insecure Registry</h3><p>In order to connect to an insecure registry, the Docker daemon must be reconfigured and an--insecure-registry option<em> </em>must be added.</p><p>This can be done directly via Juju, using the command:</p><pre>juju config kubernetes-worker docker-opts=”--insecure-registry registry.domain.com:5000&quot;</pre><h3>Creating a Secure CDK Registry</h3><p>CDK provides an option to deploy a secure Docker registry within the cluster, and expose it via an ingress.</p><p><strong>Note</strong>: The registry provided is <strong>not</strong> a production grade registry, and should not be used in a production context.</p><h4>Requirements</h4><p>To deploy and use the provided registry, you will need:</p><ul><li>A DNS entry (registry.acme.com) pointing at the ingress of the cluster (directly, via DNS round robin or with a load balancer)</li><li>A valid TLS certificate and key for registry.acme.com (registry.crt and registry.key)</li><li>A set of usernames and passwords stored in a file for htpasswd authentication (format: username:password, one user per line)</li></ul><p>Considering a htpasswd.cleartxt file filled with users, the following loop will generate an encoded version of it:</p><pre>while read line<br>do<br>  USER=$(echo ${line} | cut -f1 -d&#39;:&#39;)<br>  PASS=$(echo ${line} | cut -f2 -d&#39;:&#39;)<br>  docker run \<br>    --rm \<br>    xmartlabs/htpasswd \<br>    ${USER} ${PASS} \<br>    | tee -a htpasswd.enc<br>done &lt; htpasswd.cleartxt</pre><pre>sed -i &quot;/^$/d&quot; htpasswd.enc</pre><h4>Deployment</h4><p>To deploy the registry, run:</p><pre>juju run-action kubernetes-worker/0 registry \<br>  domain=registry.acme.com \<br>  htpasswd=”$(base64 -w0 htpasswd.enc)” \<br>  htpasswd-plain=”$(base64 -w0 htpasswd.cleartxt)” \<br>  tlscert=”$(base64 -w0 registry.crt)” \<br>  tlskey=”$(base64 -w0 registry.key)” \<br>  ingress=true</pre><h4>Tear down</h4><p>To tear down the registry, run</p><pre>juju run-action kubernetes-worker/0 registry \<br>  delete=true \<br>  ingress=true</pre><h4>Storage</h4><p>The registry provided by CDK will use a /srv/registry hostPath to store the images. This means that in case of a rescheduling of the registry (failure, overload…), if the new pod is scheduled on a different host, you will lose your images.</p><p>Alternatively, you can use a network mount such as NFS on all workers to benefit from a single point of storage for the images.</p><h4>Ingress Configuration</h4><p>The CDK registry action makes the assumption that the ingress running is nginx and will enforce a change of the configuration to increase the client_max_body_size from 1MB to 1GB. This is done via a patch, hence will not overwrite other configuration keys.</p><p>If you are using another ingress, deploy with ingress=false and make sure your ingress will support image upload (typical images are ~300MB, and typical CUDA images are 1 to 4GB)</p><h3>Alternatives</h3><p>If you want a similar setup but with flexibility on the storage and management via native Kubernetes tools you will find a derived work delivered via a Helm chart on <a href="https://github.com/madeden/charts">https://github.com/madeden/charts</a></p><p>If you’d like to follow along more closely with CDK development, you can do so in the following places:</p><ul><li><a href="https://github.com/kubernetes/kubernetes">https://github.com/kubernetes/kubernetes</a> (cluster/juju directory)</li><li><a href="https://github.com/juju-solutions/bundle-canonical-kubernetes">https://github.com/juju-solutions/bundle-canonical-kubernetes</a></li><li>Kubernetes <a href="http://slack.k8s.io/">Slack channels</a> and <a href="https://kubernetes.io/community/">SIG meetings</a></li><li>#juju on Freenode IRC</li><li><a href="/service/mailto:juju@lists.ubuntu.com">juju@lists.ubuntu.com</a> mailing list</li></ul><p>Until next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31cb05a9b61c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Canonical Distribution of Kubernetes: Development Summary 2017.38]]></title>
            <link>https://medium.com/@tvansteenburgh/canonical-distribution-of-kubernetes-development-summary-2017-38-8417b0c88283?source=rss-cdcb4bf6c2f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/8417b0c88283</guid>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Tim Van Steenburgh]]></dc:creator>
            <pubDate>Fri, 22 Sep 2017 19:30:23 GMT</pubDate>
            <atom:updated>2017-09-22T19:30:23.039Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wg_Kcr5Dv8byXWWc4XgslQ.png" /></figure><p>September 15th concluded our most recent development sprint on the <a href="https://www.ubuntu.com/containers/kubernetes">Canonical Distribution of Kubernetes</a> (CDK). Here are some highlights:</p><h3>Canal Bundle</h3><p>Our new <a href="https://github.com/projectcalico/canal">Canal</a> bundle is published! If you need network policy support in your cluster, try it out:</p><pre>juju deploy canonical-kubernetes-canal</pre><p>In the future you’ll be able to choose between Flannel and Calico when deploying Kubernetes via <a href="https://conjure-up.io/">conjure-up</a>.</p><h3>Blogs and Demos</h3><p>In case you missed them, check out some new blog posts and demos of CDK from members of the CDK engineering team:</p><ul><li><a href="https://medium.com/@ktsakalozos/patch-cdk-1-build-release-1780152f5533">Building CDK: Part #1</a> by <a href="https://medium.com/u/c78445e119bc">Konstantinos Tsakalozos</a></li><li><a href="https://medium.com/@george.kraft/kubernetes-snaps-the-quick-version-ded80eda9425">Kubernetes Snaps: The Quick Version</a> by <a href="https://medium.com/u/f105a357072a">George Kraft</a></li><li><a href="https://www.youtube.com/watch?v=ON_EpEM-HFg">Introduction to the Canonical Distribution of Kubernete</a>s (<a href="https://www.youtube.com/watch?v=ON_EpEM-HFg">part 1</a>, <a href="https://www.youtube.com/watch?v=1b-lPq5PCUU">part 2</a>, <a href="https://goo.gl/yAafUD">slides</a>). Many thanks to <a href="https://medium.com/u/d6c3d29f67f8">Arash Kaffamanesh</a> and the <a href="https://twitter.com/kubernauts">@kubernauts</a> for hosting and recording this talk!</li></ul><h3>RBAC</h3><p>We added more tests for RBAC and updated CI to start testing an RBAC-enabled cluster. Our remaining task for RBAC is to plan and test the upgrade path for old clusters once we make RBAC on-by-default.</p><h3>s390x</h3><p>We built and published an s390x nginx-ingress-controller image and an e2e snap, and started testing a lxd CDK cluster on s390x. Since then we’ve gotten access to more hardware and are now testing on s390x vms using the Juju manual provider.</p><h3>1.8.0</h3><p>In our current sprint we’ve started testing 1.8.0 in anticipation of the upstream release at the end of this month. We’re also testing with docker 1.13.1, which will soon become the default in CDK.</p><p>If you’d like to follow along more closely with CDK development, you can do so in the following places:</p><ul><li><a href="https://github.com/kubernetes/kubernetes">https://github.com/kubernetes/kubernetes</a> (cluster/juju directory)</li><li><a href="https://github.com/juju-solutions/bundle-canonical-kubernetes">https://github.com/juju-solutions/bundle-canonical-kubernetes</a></li><li>Kubernetes <a href="http://slack.k8s.io/">Slack channels</a> and <a href="https://kubernetes.io/community/">SIG meetings</a></li><li>#juju on Freenode IRC</li><li><a href="/service/mailto:juju@lists.ubuntu.com">juju@lists.ubuntu.com</a> mailing list</li></ul><p>Until next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8417b0c88283" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Canonical Distribution of Kubernetes: Development Summary 2017.36]]></title>
            <link>https://medium.com/@tvansteenburgh/canonical-distribution-of-kubernetes-development-summary-2017-36-36d40106a68a?source=rss-cdcb4bf6c2f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/36d40106a68a</guid>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Tim Van Steenburgh]]></dc:creator>
            <pubDate>Wed, 06 Sep 2017 19:22:27 GMT</pubDate>
            <atom:updated>2017-09-06T19:22:27.240Z</atom:updated>
            <content:encoded><![CDATA[<p>September 1st concluded our most recent development sprint on the <a href="https://www.ubuntu.com/containers/kubernetes">Canonical Distribution of Kubernetes</a> (CDK). Here are some highlights:</p><h3>Canal Bundle</h3><p>Our new <a href="https://github.com/projectcalico/canal">Canal</a> bundle is available for testing. We’ve been fixing a few <a href="https://github.com/juju-solutions/bundle-canonical-kubernetes/issues?utf8=%E2%9C%93&amp;q=is%3Aissue%20label%3Aarea%2Fcanal%20">issues</a> and expect to release the Canal bundle to the stable channel tomorrow.</p><p>If you need network policy support in your cluster, take it for a test drive on AWS with:</p><pre>juju deploy cs:~containers/canonical-kubernetes-canal --channel edge</pre><p>Once deployed, you can test network policy support by following the <a href="https://docs.projectcalico.org/v2.5/getting-started/kubernetes/tutorials/simple-policy">instructions</a> on the <a href="https://www.projectcalico.org//">Calico</a> website.</p><h3>RBAC and s390x</h3><p>Our main focus was on finishing the Calico/Canal support, but progress continues on RBAC and s390x. We added a bunch of new tests for RBAC, and are working on building/publishing the last few pieces we need for an s390x cluster (nginx-ingress-controller image and an e2e snap).</p><h3>1.7.4</h3><p>We tested and released our latest round of charm bug fixes along with snaps for the 1.7.4 upstream binaries. If you were already on 1.7.0, you got upgraded automatically, and 1.7.4 is the new default for new clusters.</p><p>If you’d like to follow along more closely with CDK development, you can do so in the following places:</p><ul><li><a href="https://github.com/kubernetes/kubernetes">https://github.com/kubernetes/kubernetes</a> (cluster/juju directory)</li><li><a href="https://github.com/juju-solutions/bundle-canonical-kubernetes">https://github.com/juju-solutions/bundle-canonical-kubernetes</a></li><li>Kubernetes <a href="http://slack.k8s.io/">Slack channels</a> and <a href="https://kubernetes.io/community/">SIG meetings</a></li><li>#juju on Freenode IRC</li><li><a href="/service/mailto:juju@lists.ubuntu.com">juju@lists.ubuntu.com</a> mailing list</li></ul><p>If you’re interested in hacking on CDK, be sure to check out the <a href="https://medium.com/@ktsakalozos/patch-cdk-1-build-release-1780152f5533">latest blog</a> by our friend <a href="https://twitter.com/ktsakalozos">Kos</a>!</p><p>Until next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36d40106a68a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Canonical Distribution of Kubernetes: Development Summary 2017.34]]></title>
            <link>https://medium.com/@tvansteenburgh/canonical-distribution-of-kubernetes-development-summary-2017-34-760b51846b1f?source=rss-cdcb4bf6c2f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/760b51846b1f</guid>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Tim Van Steenburgh]]></dc:creator>
            <pubDate>Thu, 24 Aug 2017 18:41:08 GMT</pubDate>
            <atom:updated>2017-08-24T18:41:08.917Z</atom:updated>
            <content:encoded><![CDATA[<p>August 18th concluded our most recent development sprint on the <a href="https://www.ubuntu.com/containers/kubernetes">Canonical Distribution of Kubernetes</a> (CDK). Here are some highlights:</p><ul><li>CI failures fixed. We spent some time fixing a handful of CI failures that had crept in recently. We’re back to green now and looking good for a patch release of CDK in the near future.</li><li><a href="https://github.com/juju-solutions/layer-canal">Canal charm</a> implemented. Canal provides an alternative to Flannel for those who need network policy support on CDK. We have more testing to do on Canal in this and the next sprint, but for those wishing to kick the tires, you can take Canal for a test drive with: juju deploy cs:~cynerva/canonical-kubernetes-canal-0 (NB: doesn’t work on LXD). In the current sprint we’ll be adding the Canal charm and bundle to CI for more thorough and regular testing.</li><li>RBAC support. We updated our default cluster add-ons and microbot example to work with RBAC, completing our RBAC proof-of-concept work. In the current sprint we’re getting CI updated with more tests for RBAC.</li><li>s390x support. We looked into getting upstream s390x builds for <a href="https://github.com/kubernetes/heapster/issues/1759">heapster</a> (success!) and <a href="https://github.com/kubernetes/ingress/issues/1108">ingress</a> (no success). For ingress we hit an impasse with a QEMU bug, so in the interest of continuing to make forward progress, we plan to build this image on actual s390x hardware for now. In the current sprint we’ll be building that image and then running e2e tests on s390x to see where we’re at!</li></ul><p>Finally, in case you missed it, be sure to check out <a href="https://insights.ubuntu.com/2017/08/19/conjure-up-dev-summary-aws-native-integration-vsphere-3-and-addons/">the new features coming to conjure-up</a> — a tool for deploying CDK on any public cloud, private cloud, or developer laptop. The latest edge build of conjure-up includes automatic native-cloud integration for CDK on AWS, and the introduction of Add-ons, which can deploy software (like Deis, for example) onto your new Kubernetes cluster in a repeatable and automated way.</p><p>If you’d like to follow along more closely with CDK development, you can do so in the following places:</p><ul><li><a href="https://github.com/kubernetes/kubernetes">https://github.com/kubernetes/kubernetes</a> (cluster/juju directory)</li><li><a href="https://github.com/juju-solutions/bundle-canonical-kubernetes">https://github.com/juju-solutions/bundle-canonical-kubernetes</a></li><li>Kubernetes <a href="http://slack.k8s.io/">Slack channels</a> and <a href="https://kubernetes.io/community/">SIG meetings</a></li><li>#juju on Freenode IRC</li><li><a href="/service/mailto:juju@lists.ubuntu.com">juju@lists.ubuntu.com</a> mailing list</li></ul><p>Until next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=760b51846b1f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Canonical Distribution of Kubernetes: Development Summary 2017.32]]></title>
            <link>https://medium.com/@tvansteenburgh/canonical-distribution-of-kubernetes-development-summary-2017-32-4522b5f43173?source=rss-cdcb4bf6c2f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/4522b5f43173</guid>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Tim Van Steenburgh]]></dc:creator>
            <pubDate>Wed, 09 Aug 2017 18:15:23 GMT</pubDate>
            <atom:updated>2017-08-09T18:15:23.950Z</atom:updated>
            <content:encoded><![CDATA[<p>August 4th concluded our most recent development sprint on the <a href="https://www.ubuntu.com/containers/kubernetes">Canonical Distribution of Kubernetes</a> (CDK). Here are some highlights:</p><h3>Testing &amp; Planning</h3><ul><li>CDK offline testing plan. We wrote up a plan for testing CDK in an environment where there is no (or severely limited) egress internet access. The end goal is to ensure that CDK can be deployed in this scenario, and create docs describing how to do it. Initial testing begins in the current sprint.</li><li>etcd2-to-etcd3 migration plan. We wrote up a plan for upgrading existing CDK clusters from etcd2 to etcd3 if desired, and making etcd3 the new default. While the plan is in place, we don’t have any implementation work planned in the current sprint.</li><li>Canal. We wrote up a design doc for implementing Canal (Calico-on-Flannel) for CDK. Implementation of the Canal charm was scheduled for the current sprint and is currently in code review.</li><li>We added a Jenkins job to test our stable charms against the latest upstream patch release. A passing build here tells us that we can release the latest binaries for CDK without breaking currently-deployed clusters.</li></ul><h3>Features</h3><ul><li>Completed RBAC proof-of-concept work. At this point we know how to turn RBAC on/off via charm config, and what changes are needed in CDK to make this work. In the coming weeks we’ll be working on moving from proof-of-concept to production-ready.</li><li>s390x support. We started by snapping the major cluster components. There are some docker images that don’t have s390x builds, namely nginx-ingress-controller, heapster-grafana, and addon-resizer. We’ll be following up on these in the current sprint.</li><li>Calico. We updated the Calico CNI charm to use the latest Calico binaries, and added the Calico charm and bundles to CI.</li></ul><p>If you’d like to follow along more closely with CDK development, you can do so in the following places:</p><ul><li><a href="https://github.com/kubernetes/kubernetes">https://github.com/kubernetes/kubernetes</a> (cluster/juju directory)</li><li><a href="https://github.com/juju-solutions/bundle-canonical-kubernetes">https://github.com/juju-solutions/bundle-canonical-kubernetes</a></li><li>Kubernetes <a href="http://slack.k8s.io/">Slack channels</a> and <a href="https://kubernetes.io/community/">SIG meetings</a></li><li>#juju on Freenode IRC</li><li><a href="/service/mailto:juju@lists.ubuntu.com">juju@lists.ubuntu.com</a> mailing list</li></ul><p>Until next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4522b5f43173" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Canonical Distribution of Kubernetes: Development Summary #4]]></title>
            <link>https://medium.com/@tvansteenburgh/the-canonical-distribution-of-kubernetes-development-summary-4-fec7f5151d91?source=rss-cdcb4bf6c2f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/fec7f5151d91</guid>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Tim Van Steenburgh]]></dc:creator>
            <pubDate>Thu, 27 Jul 2017 16:45:03 GMT</pubDate>
            <atom:updated>2017-07-27T16:45:03.981Z</atom:updated>
            <content:encoded><![CDATA[<p>July 21st concluded our most recent development sprint on the <a href="https://www.ubuntu.com/containers/kubernetes">Canonical Distribution of Kubernetes</a> (CDK). Here’s a look at what we did.</p><h3>Fixes and Improvements</h3><p>Check out the <a href="https://github.com/juju-solutions/bundle-canonical-kubernetes/milestone/10?closed=1">full list</a> on GitHub. Here are some notables:</p><ul><li>Made load balancer port configurable</li><li>Changed default --service-cluster-ip-range to a /16 CIDR to allow more NodePort IP addresses</li><li>Fixed etcd snapshot action</li><li>Increased default worker node constraints to 4 cpu, 4GB RAM</li></ul><h3>Testing</h3><ul><li>Added a test to ensure dashboard is operational after deploy</li><li>Added a test for the built-in microbot example</li><li>Added a Jenkins job to test master charms with stable snaps. When this is green it means we can release whatever new fixes/features we have queued up in the charms, giving us the confidence to do <strong>more frequent releases.</strong></li></ul><h3>Features</h3><ul><li><a href="https://www.projectcalico.org/">Calico</a> spike. We want to provide a CDK + Calico deployment option that works on any cloud, just like our CDK + Flannel option. We’ve decided to go with a Calico-on-Flannel (<a href="https://github.com/projectcalico/canal">Canal</a>) approach initially. Canal combines the network policy enforcement of Calico with the ease-of-deployment of Flannel. Work begins in the current sprint!</li><li><a href="https://kubernetes.io/docs/admin/authorization/rbac/">RBAC</a> spike. We mapped out the work necessary for enabling RBAC via charm config. Work begins in the current sprint!</li><li>Updated the <a href="https://jujucharms.com/canonical-kubernetes-elastic/">canonical-kubernetes-elastic</a> bundle. This bundle has been added to our Jenkins build process and updated with the latest 1.7 charms.</li></ul><p>If you’d like to follow along more closely with CDK development, you can do so in the following places:</p><ul><li><a href="https://github.com/kubernetes/kubernetes">https://github.com/kubernetes/kubernetes</a> (cluster/juju directory)</li><li><a href="https://github.com/juju-solutions/bundle-canonical-kubernetes">https://github.com/juju-solutions/bundle-canonical-kubernetes</a></li><li>Kubernetes <a href="http://slack.k8s.io/">Slack channels</a> and <a href="https://kubernetes.io/community/">SIG meetings</a></li><li>#juju on Freenode IRC</li><li><a href="/service/mailto:juju@lists.ubuntu.com">juju@lists.ubuntu.com</a> mailing list</li></ul><p>Until next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fec7f5151d91" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Canonical Distribution of Kubernetes: Development Summary #3]]></title>
            <link>https://medium.com/@tvansteenburgh/the-canonical-distribution-of-kubernetes-development-summary-3-e8e99a8a37e1?source=rss-cdcb4bf6c2f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8e99a8a37e1</guid>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Tim Van Steenburgh]]></dc:creator>
            <pubDate>Wed, 12 Jul 2017 19:43:13 GMT</pubDate>
            <atom:updated>2017-07-12T19:43:13.138Z</atom:updated>
            <content:encoded><![CDATA[<figure><a href="https://www.ubuntu.com/containers/kubernetes"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nz19IJ3NQZucmmPVblTfKg.png" /></a></figure><p>Last Friday, one week after the Kubernetes 1.7 release, we <a href="https://insights.ubuntu.com/2017/07/07/kubernetes-1-7-on-ubuntu/">released</a> version 1.7 of the <a href="https://www.ubuntu.com/containers/kubernetes">Canonical Distribution of Kubernetes</a> (CDK). That release coincided with the end of our latest two-week development sprint.</p><p>Everything we did in that sprint contributed to the release in some way. We fixed some <a href="https://github.com/juju-solutions/bundle-canonical-kubernetes/issues?q=is%3Aissue+milestone%3A2017.07.07+label%3Akind%2Fbug+is%3Aclosed">bugs</a>. Merged a final <a href="https://github.com/kubernetes/kubernetes/pull/47835">feature</a>. Updated some <a href="https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/206">docs</a>. But mostly, we tested. We wrote new <a href="https://github.com/juju-solutions/bundle-canonical-kubernetes/pull/317">test</a> <a href="https://github.com/juju-solutions/bundle-canonical-kubernetes/pull/304">cases</a>. We ran 1.7 deployments on multiple clouds. We ran upgrades from 1.6 to 1.7 on those clouds. We ran scaling tests. We ran the upstream end-to-end tests.</p><p>The team is putting tons of effort into our testing setup right now, and it’s paying off. With version 1.7, CDK is more rock-solid than ever! Dependability, pure upstream binaries, <a href="https://medium.com/@tvansteenburgh/kubernetes-1-7-on-ubuntu-the-easy-way-bcd851d4ed35">incredible ease-of-deployment on any cloud</a>, and <a href="https://pages.ubuntu.com/03.UpgradingK8sclusters_LPOn-demandwebinar.html?utm_source=ubuntu.com&amp;utm_medium=website&amp;utm_campaign=On-demand%20webinar%20--%20Painless%20Kubernetes%20upgrades&amp;_ga=2.128133388.1021014164.1499878929-1486973742.1493731597">quick, painless upgrades</a>…what’s not to love? :-)</p><p>We’re really excited about test automation for CDK right now, but it’s not <em>just</em> for the sake of dependability. It’s for the freedom to move fast. To deliver more of the features that make CDK the easiest-to-deploy-and-operate Kubernetes distribution out there, and to deliver them quickly and with high confidence.</p><p>If you’d like to follow along more closely with CDK development, you can do so in the following places:</p><ul><li><a href="https://github.com/kubernetes/kubernetes">https://github.com/kubernetes/kubernetes</a> (cluster/juju directory)</li><li><a href="https://github.com/juju-solutions/bundle-canonical-kubernetes">https://github.com/juju-solutions/bundle-canonical-kubernetes</a></li><li>Kubernetes <a href="http://slack.k8s.io/">Slack channels</a> and <a href="https://kubernetes.io/community/">SIG meetings</a></li><li>#juju on Freenode IRC</li><li><a href="/service/mailto:juju@lists.ubuntu.com">juju@lists.ubuntu.com</a> mailing list</li></ul><p>Until next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8e99a8a37e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kubernetes 1.7 on Ubuntu, the Easy Way]]></title>
            <link>https://medium.com/hackernoon/kubernetes-1-7-on-ubuntu-the-easy-way-bcd851d4ed35?source=rss-cdcb4bf6c2f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcd851d4ed35</guid>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Tim Van Steenburgh]]></dc:creator>
            <pubDate>Fri, 07 Jul 2017 20:42:47 GMT</pubDate>
            <atom:updated>2019-05-22T06:03:50.605Z</atom:updated>
            <content:encoded><![CDATA[<p>I spotted <a href="http://www.techrepublic.com/article/how-to-install-the-necessary-components-for-a-kubernetes-cluster-on-ubuntu-linux/">this article</a> yesterday, demonstrating how to set up a <a href="https://hackernoon.com/tagged/kubernetes">Kubernetes</a> cluster on <a href="https://hackernoon.com/tagged/ubuntu">Ubuntu</a>. While the article is well-meaning, I feel obligated to raise my hand and shout, “Wait, it’s actually much easier than that!”</p><p>Whether you’re new to Kubernetes and just want to get up-and-running, or you’re a Kubernetes admin looking for an easier way to deploy and manage a cluster, I’ll show you the quickest way to do it on Ubuntu.</p><h3>Spoiler Alert</h3><p>On a fresh install of Ubuntu Xenial, it only takes two (!) commands to get a complete Kubernetes cluster up-and-running:</p><pre>sudo snap install conjure-up --classic<br>conjure-up kubernetes</pre><p>The conjure-up command will launch an installer to walk you through installing Kubernetes on the cloud of your choice. You can choose from AWS, Azure, Google, Joyent, Oracle, Rackspace, and…localhost!</p><p>Deploying to localhost will create a Kubernetes cluster that is fully contained on the host machine, but with all of the cluster components neatly separated into individual <a href="https://www.ubuntu.com/containers/lxd">LXD</a> containers.</p><h3>Demo</h3><p>Here’s a demo where I demonstrate these steps on a fresh Ubuntu Xenial machine. In the demo I run conjure-up in headless mode, without the terminal-based GUI. The entire install is just two commands!</p><p>After the install completes, I run a couple of extra commands to show that we do indeed have a fully functional Kubernetes cluster.</p><figure><a href="https://asciinema.org/a/tQrIV2xAUwJ3RM56a7zuAa340?speed=4"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gRaB9CF8WMz_2m2TS26s6w.png" /></a><figcaption>Deploying a Kubernetes 1.7 cluster with two commands!</figcaption></figure><p>Enjoy!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcd851d4ed35" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/kubernetes-1-7-on-ubuntu-the-easy-way-bcd851d4ed35">Kubernetes 1.7 on Ubuntu, the Easy Way</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Canonical Distribution of Kubernetes: June 13 Development Summary]]></title>
            <link>https://medium.com/@tvansteenburgh/the-canonical-distribution-of-kubernetes-june-13-development-summary-ea9675cae8b6?source=rss-cdcb4bf6c2f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea9675cae8b6</guid>
            <category><![CDATA[cdk]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Tim Van Steenburgh]]></dc:creator>
            <pubDate>Tue, 13 Jun 2017 19:07:26 GMT</pubDate>
            <atom:updated>2017-06-13T19:07:26.511Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RPTkX9eVKzGCKIsuL9ilbw.png" /></figure><p>This is the development blog for the <a href="https://www.ubuntu.com/containers/kubernetes">Canonical Distribution of Kubernetes</a> (CDK). Here’s what we’ve been up to since the last installment…</p><h3>Federation</h3><p>We’ve been following along with upstream work on cluster federation. In case you missed it, our own <a href="https://medium.com/u/bc927dac4b68">K.Tsakalozos</a> published <a href="https://medium.com/@ktsakalozos/federated-k8s-with-on-prem-clusters-and-juju-wip-5d2022379818">Federated Kubernetes with on-prem Clusters and Juju</a>, demonstrating a proof-of-concept federated cluster on AWS, using CDK.</p><h3>Testing/CI/CD</h3><p>We’re putting a lot of effort into testing and CI right now. Here’s some of what we have in the works:</p><ol><li>Nightly snap builds of upstream Kubernetes binaries.</li><li>Nightly builds of CDK charms.</li><li>Nightly test runs of both upstream e2e tests and our own charm integration tests.</li><li><a href="https://github.com/juju-solutions/kubernetes-jenkins/commit/fe06dcd5eab69d3a234a835f744770ee71f9b34a">Automated upgrade tests</a> using <a href="https://github.com/juju/python-libjuju/">libjuju</a>. These will help ensure that the upgrade path for CDK remains reliable and robust. More to come!</li></ol><p>In other news, Kubernetes <a href="https://github.com/kubernetes/kubernetes/releases/tag/v1.7.0-beta.1">v1.7.0-beta.1</a> is out, and we’re testing it with CDK.</p><h3>Authentication, Authorization, and RBAC</h3><p>We’re working on improving user management and access control in CDK. Our plan is to enable <a href="https://kubernetes.io/docs/admin/authorization/rbac/">RBAC authorization</a> by default in a future version of CDK, and provide user-management actions for creating and managing users and groups. We’re still planning this out, lots more info to come showing exactly what this will look like — stay tuned!</p><h3>Bug Fixes</h3><ul><li>Fixed a bug that could unnecessarily increase initial cluster deployment time by up to 10 minutes. <a href="https://github.com/kubernetes/kubernetes/issues/47182">#47182</a></li><li>Fixed a bug that attempted to enable the new “Initializers” admission controller (1.7+ only) on an unsupported cluster. <a href="https://github.com/kubernetes/kubernetes/issues/47062">#47062</a></li></ul><p>If you’d like to follow along more closely with CDK development, you can do so in the following places:</p><ul><li><a href="https://github.com/kubernetes/kubernetes">https://github.com/kubernetes/kubernetes</a> (cluster/juju directory)</li><li><a href="https://github.com/juju-solutions/bundle-canonical-kubernetes">https://github.com/juju-solutions/bundle-canonical-kubernetes</a></li><li>Kubernetes <a href="http://slack.k8s.io/">Slack channels</a> and <a href="https://kubernetes.io/community/">SIG meetings</a></li><li>#juju on Freenode IRC</li><li><a href="/service/mailto:juju@lists.ubuntu.com">juju@lists.ubuntu.com</a> mailing list</li></ul><p>Until next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea9675cae8b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Canonical Distribution of Kubernetes: Weekly Development Summary]]></title>
            <link>https://medium.com/@tvansteenburgh/the-canonical-distribution-of-kubernetes-weekly-development-summary-49274b78b5c2?source=rss-cdcb4bf6c2f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/49274b78b5c2</guid>
            <category><![CDATA[cdk]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Tim Van Steenburgh]]></dc:creator>
            <pubDate>Fri, 26 May 2017 20:02:45 GMT</pubDate>
            <atom:updated>2017-05-26T20:02:45.736Z</atom:updated>
            <content:encoded><![CDATA[<p>This post is the first in a weekly series summarizing development activity on CDK (the <a href="https://www.ubuntu.com/containers/kubernetes">Canonical Distribution of Kubernetes</a>).</p><p>So without further adieu, here’s what we’ve been up to this week:</p><ul><li>Foundational work to enable RBAC support by swapping auth-z mechanisms from x509 cert validation to Basic Auth / Token — in-place migration is being worked on presently. The feature is in early alpha state, but early trials are promising.</li><li>Built a kube-oidc interface to enable openid connect authentication providers. This paves the way for middle-man proxies like dex, keycloak, UAA, OpenUnison which allows administrators to connect their cluster to an external auth source and define roles for the incoming users based on group policy management.</li><li>Moved all system components to the kube-system namespace and have started refactoring to least privilege security models including: heapster, fluentd, kubedns, nginx-ingress-controller and the default-http-backend</li><li>Updated kubernetes-worker to detect added GPU hardware on-the-fly, instead of just checking once at charm install time.</li><li>Ongoing collaboration with the Linux Foundation to build CDK-based clusters for their Kubernetes certification exam.</li><li>Work on cluster federation: Patch kubefed upstream to allow setting the port of federation-apiservice when services are exposed through nodeport.</li><li>Allow for configuring the cluster and context names in the kubeconfig files of the CDK clusters.</li><li>Making progress on our build infrastructure in our march toward continuous integration. Fixed up a few flaky test failures, some problems with the test reporting, and some gaps in our coverage. Optimistic that we can get nightly builds and test runs of the whole CDK stack going within the next week.</li></ul><p>If you’d like to follow more closely, you can do so in the following places:</p><ul><li><a href="https://github.com/kubernetes/kubernetes">https://github.com/kubernetes/kubernetes</a> (cluster/juju directory)</li><li><a href="https://github.com/juju-solutions/bundle-canonical-kubernetes">https://github.com/juju-solutions/bundle-canonical-kubernetes</a></li><li>Kubernetes Slack channels and SIG meetings</li><li>#juju on Freenode IRC</li></ul><p>Until next week!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49274b78b5c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>