<?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 Eryn Muetzel on Medium]]></title>
        <description><![CDATA[Stories by Eryn Muetzel on Medium]]></description>
        <link>https://medium.com/@eryn_muetzel?source=rss-311685319c12------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8LiQ70_rf4VsMorZCOb9Ow.jpeg</url>
            <title>Stories by Eryn Muetzel on Medium</title>
            <link>https://medium.com/@eryn_muetzel?source=rss-311685319c12------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 16:31:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eryn_muetzel/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[Moving the needle on kubeadm in Kubernetes 1.11]]></title>
            <link>https://medium.com/heptio-blog/moving-the-needle-on-kubeadm-in-kubernetes-1-11-90a87ddb9d0f?source=rss-311685319c12------2</link>
            <guid isPermaLink="false">https://medium.com/p/90a87ddb9d0f</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[kubeadm]]></category>
            <dc:creator><![CDATA[Eryn Muetzel]]></dc:creator>
            <pubDate>Mon, 09 Jul 2018 18:46:30 GMT</pubDate>
            <atom:updated>2018-07-13T16:07:46.521Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fvJi_r9TsEBGh7l1alAH1w.jpeg" /></figure><p>Kubernetes 1.11 was released last week — it was a huge accomplishment for everyone involved and the release includes a swath of new functionality. A key focus area for Heptio is making Kubernetes easier to deploy and upgrade, and part of that work includes making improvements to Heptio’s preferred tool for bootstrapping a Kubernetes cluster, kubeadm.</p><p><a href="https://github.com/kubernetes/community/tree/master/sig-cluster-lifecycle">SIG-Cluster-Lifecycle</a> leads the development on kubeadm, and Heptio was heavily involved in this group (which includes contributors such as <a href="https://github.com/luxas">Lucas Käldström</a>, <a href="https://github.com/stealthybox">Leigh Schrandt</a>, <a href="https://github.com/neolit123">Lubomir Ivanov</a>, <a href="https://github.com/xiangpengzhao">Peter (XiangPeng) Zhao</a>, <a href="https://github.com/rosti">Rostislav Georgiev</a>, and <a href="https://github.com/dixudx">Di Xu</a>) to bring about some important improvements in 1.11.</p><p>In this post, we cover what kubeadm is, why Heptio recommends kubeadm, and how we are working with the Kubernetes community to move kubeadm forward.</p><p><strong>What is kubeadm and when should I use it?</strong></p><p>kubeadm is a tool included in every Kubernetes release that helps users set up a best-practice Kubernetes cluster. kubeadm provides support along the entire lifecycle of a Kubernetes cluster including creation, upgrade, and teardown.</p><p>Due to the variety of ways in which machines can be provisioned, the scope of kubeadm is intentionally limited to bootstrapping rather than provisioning — it is intended to be a building block, and higher level tools take advantage of kubeadm. kubeadm allows these higher level tools to ensure clusters are conformant and look as much alike as possible. Setting up add-ons such as CNI, the Kubernetes dashboard, and monitoring tools is outside the scope of kubeadm.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gc_Jf_hRtmss-6HPcrhRoA.png" /></figure><p>Check out the kubeadm <a href="https://github.com/kubernetes/kubeadm">repository</a> and <a href="https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm/">docs</a> for more information.</p><p><strong>Why does Heptio recommend kubeadm?</strong></p><p>kubeadm is the primary deployment tool Heptio recommends for bootstrapping a Kubernetes cluster, based on some key advantages:</p><ul><li><strong>Ease of use. </strong>kubeadm supports creation, upgrade, and teardown, and is a relatively easy tool for new users to adopt.</li><li><strong>Use on any infrastructure.</strong> Heptio customers need to deploy Kubernetes across a wide variety of infrastructure — including bare metal, VMware, AWS, Azure, GCE, and more. It’s important that a cluster created on one platform looks like another created somewhere else. We even created <a href="https://github.com/heptio/sonobuoy">Heptio Sonobuoy</a> to test conformance so you can be sure that clusters were set up correctly and will behave as expected on any infrastructure.</li><li><strong>Extendable. </strong>Heptio customers have unique enterprise requirements. kubeadm provides a phases command that allows you to execute steps individually, so you can customize actions as needed.</li><li><strong>Production ready. </strong>kubeadm rolls out secure Kubernetes clusters — adopting best practices such as enforcing RBAC, using secure communication between the control plane components and between the API server and kubelets, locking down the kubelet API, and more.</li><li><strong>Community contributions. </strong>kubeadm has become one of the most common ways to deploy Kubernetes, and as a result the community has rallied to harden kubeadm and make inroads on every release.</li></ul><p>So where does kubeadm fit into a complete deployment solution for Heptio customers? kubeadm is not a one-click-install solution. As stated above, kubeadm is intended to be a building block and part of a larger solution. Heptio is investing significantly in this area to bring a declarative, API-driven model to cluster creation and operations, where clusters are treated as immutable (i.e. upgrades equate to a new deployment versus an in-place upgrade). Heptio plans to leverage and contribute to the upstream work on the <a href="https://github.com/kubernetes-sigs/cluster-api/">Cluster API</a> to make this real. More will be shared in the future.</p><p><strong>What’s new in kubeadm in 1.11?</strong></p><p>SIG-Cluster-Lifecycle leads the development on kubeadm and is focused on making Kubernetes easier to deploy and operate. Some key improvements the community brought to kubeadm in 1.11 include:</p><ul><li>A step-by-step <a href="https://kubernetes.io/docs/setup/independent/high-availability/">guide</a> to build an HA Kubernetes deployment with stacked masters (e.g. etcd members and control plane nodes are co-located). An external etcd cluster is also available as an option.</li><li>An upgraded API version for the configuration file, v1alpha2. kubeadm will still be able to read v1alpha1 configuration, and will automatically convert the configuration to v1alpha2. This is a necessary step for kubeadm to align with the Cluster API work mentioned above.</li><li>The first step towards a fully dynamic kubelet configuration — kubelet config allows overrides via config-map for a host of features for a kubelet, but includes a set of defaults that remove manual steps involved when initializing or joining across different host OSs and CRI implementations.</li><li>Replacement of kube-dns by CoreDNS as the default DNS provider, which is valuable for users that have scaled out deployments. Existing deployments will automatically upgrade to CoreDNS via kubeadm.</li><li>Better CRI integration (including auto detection for other CRI runtimes than Docker) and support for air-gapped environments.</li><li>New CLI commands that are helpful for people setting up clusters, including: kubeadm config print-default, kubeadm config migrate, kubeadm config images list, kubeadm config images pull, and kubeadm upgrade node config.</li><li>Several bug fixes, most notably: a fix for a security issue for etcd by closing the peer port that was previously left insecure, and additional security in the kubelet configuration.</li></ul><p>A team of amazing Heptio engineers (including <a href="https://github.com/timothysc">Tim St. Clair</a>, <a href="https://github.com/detiber">Jason DeTiberus</a>, <a href="https://github.com/chuckha">Chuck Ha</a>, <a href="https://github.com/liztio">Liz Frost</a>, <a href="https://github.com/rdodev">Ruben Orduz</a>, and <a href="https://github.com/Bradamant3">Jennifer Rondeau</a>) were key contributors to SIG-Cluster-Lifecycle in bringing out these important additions to kubeadm in 1.11. In particular, Tim St. Clair does an incredible amount of work for this group by grooming and triaging issues and reviewing pull requests. It is important for Heptio to do this work upstream, so everyone in the community can rally around a common Kubernetes bootstrapping method which can provide for semantic consistency across environments.</p><p>See a full list of 1.11 kubeadm changes <a href="https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.11.md#sig-cluster-lifecycle-1">here</a>.</p><p><strong>What’s next for kubeadm?</strong></p><p>The key focus areas for development moving forward are high availability and general availability (GA) of kubeadm. While users can achieve high availability with kubeadm manually today, the community is focused on bringing native support for things like replicated etcd and multiple, redundant API servers and other control plane components. GA will require some key additions such as getting the config API to v1beta1 (to ensure supported migrations and deprecation guarantees), support for reading multiple YAML documents, HA capabilities (both etcd and masters), and alignment with the Cluster API spec.</p><p>Heptio is fully committed to making Kubernetes easier to deploy and operate, and we will make continued investments in kubeadm and other tooling to bring those capabilities to everyone.</p><p>Interested in learning how Heptio can help you deploy and operate Kubernetes more efficiently, and take advantage of the innovation in kubeadm and other tools? Check out our <a href="https://heptio.com/products/kubernetes-subscription/">Heptio Kubernetes Subscription (HKS)</a> and <a href="https://heptio.com/services/consulting/">consulting</a> offerings, or <a href="https://heptio.com/about/contact/">reach out to us</a> directly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90a87ddb9d0f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/heptio-blog/moving-the-needle-on-kubeadm-in-kubernetes-1-11-90a87ddb9d0f">Moving the needle on kubeadm in Kubernetes 1.11</a> was originally published in <a href="https://medium.com/heptio-blog">Heptio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Heptio Kubernetes® Subscription (HKS): “The Undistribution”]]></title>
            <link>https://medium.com/heptio-blog/introducing-heptio-kubernetes-subscription-5415052ef374?source=rss-311685319c12------2</link>
            <guid isPermaLink="false">https://medium.com/p/5415052ef374</guid>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[hybrid-cloud]]></category>
            <category><![CDATA[heptio]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Eryn Muetzel]]></dc:creator>
            <pubDate>Tue, 30 Jan 2018 17:59:53 GMT</pubDate>
            <atom:updated>2018-02-02T19:10:15.773Z</atom:updated>
            <content:encoded><![CDATA[<p>Kubernetes and the broader ecosystem of cloud native technologies have taken the IT world by storm. Just as container technology took off in large part to organizations’ move to the cloud, Kubernetes’ continued proliferation can be attributed to the growing importance of <em>multi</em>-cloud.</p><p>Beyond the threat of lock-in to a single cloud provider — which is real — organizations need the flexibility to deploy applications in the environment where they are best suited. Kubernetes provides the right level of abstraction to deploy applications on a cloud solution and to an environment that looks and behaves the same on-premises.</p><h4><strong>Kubernetes Distributions…Everywhere</strong></h4><p>In the early days, deploying and operating an open source Kubernetes environment without vendor involvement was difficult, to say the least. As a result, many organizations turned to a supported distribution from a single vendor. Distribution-based offerings — which include a version of Kubernetes, often with additional capabilities such as security, monitoring, and build and deploy automation — provide a production-ready solution, and a single point of contact for issues as they occur.</p><p>But distributions mostly ignore a key capability Kubernetes was created to address in the first place: cloud independence. Most distributions do not run on cloud hosted container-as-a-service solutions such as Google Kubernetes Engine (GKE) and Azure Container Service (AKS). While your organization may not be using these services now, you shouldn’t have to make technology decisions today that preclude their use down the road.</p><h4><strong>Heptio Kubernetes Subscription: “The Undistribution”</strong></h4><p>The Kubernetes project has come a long way. Today, there is little reason to be intermediated by a vendor charging enterprise software rates to deliver a technology where the real value is being delivered by an open source community.</p><p>Today we are introducing <a href="http://www.heptio.com/products/kubernetes-subscription">Heptio Kubernetes Subscription (HKS)</a>, “the undistribution”. HKS is a new alternative to this distribution-based approach; it is centered around a true open source version of Kubernetes, and allows organizations to build a multi-cloud strategy that provides the option to run on hosted solutions such as Amazon EKS, GKE, and AKS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xcId3u0mQhMCGAbU5GsVtg.png" /></figure><p>HKS provides a production-grade deployment of Kubernetes, supported 24x7 by Heptio, and includes hot fixes plus additional Heptio tools to optimize supportability. HKS delivers the assurance that comes with a distribution, but with the added benefits of control, portability, flexibility, and cost effectiveness.</p><h4><strong>Why You Shouldn’t Bet Your Business on a Distribution</strong></h4><p>Heptio Kubernetes Subscription aims to solve the following problems with distribution-based deployments:</p><ul><li><strong>Limited choice:</strong> As noted above, many distributions limit your flexibility to run on a hosted solution (GKE, AKS, EKS). Distributions also work with a limited set of technologies for networking, host OS, and more. And distributions often involve an opinionated install mechanism that is unlikely to be flexible enough for enterprise deployments.</li><li><strong>Lock-in:</strong> Distributions can be based on a deep fork of Kubernetes, where vendors build proprietary capabilities that aren’t necessarily compatible with the current upstream Kubernetes version. Customers can get locked in when applications then rely on closed source extended capabilities. Understanding where community provided technology ends and vendor proprietary capabilities begin also becomes difficult.</li><li><strong>Delayed access to the latest features:</strong> The Kubernetes community moves quickly, and important capabilities are introduced in every new release. Because vendors need to integrate and vet every new Kubernetes release with their proprietary code, distribution-based offerings often lag behind open source Kubernetes by two to three versions.</li><li><strong>Cost:</strong> Distributions are often priced based on environment size and scale linearly; licensing costs can run up to $15K annually per server.</li></ul><h4><strong>Heptio Kubernetes Subscription: The Details</strong></h4><p>HKS is based on a customized production-ready reference architecture centered on upstream Kubernetes, bolstered by Heptio open source tools that fill key gaps in the Kubernetes ecosystem. Heptio supports deployments on any of the major cloud providers or on-premises, so even if you don’t intend to use multiple clouds today, you have the choice later on. Heptio is committed to working with the cloud providers to create a solution that is well aligned with their offerings and delivers legitimate portability should a managed distribution be right for you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wtub4O5ULA2yc9vg." /></figure><p>Our open source project <a href="https://github.com/heptio/sonobuoy">Sonobuoy</a> is the underpinning of the Kubernetes certification program, and allows you to be certain that each of your clusters, no matter where they are hosted, will behave as expected. Sonobuoy is also used to prequalify clusters for support and to improve supportability by providing current information about your deployment to Heptio.</p><p>We handle installation with a framework that’s consistent with upstream Kubernetes, and has been battle tested in complex enterprise deployments. Our goal is to help companies moving from ‘Kubernetes the Hard Way’ (if you follow Kelsey Hightower) to ‘Kubernetes the Easy Way’. We recognize that enterprises have unique requirements, so we focus on extensibility and modularity to accommodate their needs. Wherever possible we work directly with the Kubernetes community to improve the overall experience of installing Kubernetes. Where gaps exist we create open source tools that we donate back to the community when they are ready.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/493/1*6jXzLEaNMKlA_BSr1IwN6A.png" /></figure><p>One potential risk of using upstream Kubernetes is when you face an issue and need an immediate fix. To address this challenge, we deliver hot patches to make sure your Kubernetes cluster is production hardened, and work with the community to ensure fixes are included in the next Kubernetes release. So rather than lag behind the upstream Kubernetes version by six to 12 months, Heptio empowers you to contribute back to the upstream software that powers your business.</p><p>We are excited to bring upstream Kubernetes to the enterprise and enable a compelling multi-cloud strategy for our customers. The days of vendor lock-in are over — Kubernetes has evolved, and with the right guardrails in place, a truly open source platform will bring the most power to any organization.</p><p><strong>Learn more about Heptio Kubernetes Subscription </strong><a href="http://www.heptio.com/products/kubernetes-subscription"><strong>here</strong></a><strong>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/843/1*bzQEvEQbjzb6uWofu7HcWg.png" /></figure><p>Thanks to <a href="https://medium.com/@jennifer.rondeau">Jennifer Rondeau</a> and <a href="https://medium.com/@cmcluck">Craig McLuckie</a>.</p><p><em>Kubernetes® is a registered trademark of The Linux Foundation in the United States and other countries, and is used pursuant to a license from The Linux Foundation.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5415052ef374" width="1" height="1" alt=""><hr><p><a href="https://medium.com/heptio-blog/introducing-heptio-kubernetes-subscription-5415052ef374">Introducing Heptio Kubernetes® Subscription (HKS): “The Undistribution”</a> was originally published in <a href="https://medium.com/heptio-blog">Heptio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Heptio Guide to KubeCon + CloudNativeCon 2017]]></title>
            <link>https://medium.com/heptio-blog/https-blog-heptio-com-heptio-guide-to-kubecon-cloudnativecon-2017-91e4d12330b5?source=rss-311685319c12------2</link>
            <guid isPermaLink="false">https://medium.com/p/91e4d12330b5</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[heptio]]></category>
            <category><![CDATA[company]]></category>
            <dc:creator><![CDATA[Eryn Muetzel]]></dc:creator>
            <pubDate>Fri, 01 Dec 2017 17:10:41 GMT</pubDate>
            <atom:updated>2017-12-01T17:14:02.251Z</atom:updated>
            <content:encoded><![CDATA[<p>Heptio is excited to share that we will be at KubeCon + CloudNativeCon in Austin next week. Will you be there?</p><p>It has been humbling to watch KubeCon grow from its first event in 2015 with roughly 500 attendees to where it is today, with organizers expecting ~4000 attendees. KubeCon is clearly an important event for Heptio — it is an amazing opportunity for us to meet with customers and partners, learn about the challenges you are facing, and chart our course together for making Kubernetes easier to use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/492/1*HTcHtO6MYJGh671IWribvg.png" /></figure><p>We have a lot going on next week, and want to make sure you know about all of the opportunities to engage with us. If you are interested in meeting 1:1 with someone on our team, please email inquiries@heptio.com.</p><p><strong>Booth in the Expo Hall</strong></p><p>Come stop by Heptio’s booth to learn how Heptio is making Kubernetes easier to use with training, services, support, and open source tools. Ask any questions you may have, and get a demo of Heptio Sonobuoy Scanner, our free tool that helps ensure your Kubernetes cluster is set up correctly.</p><p><strong>Training</strong></p><p>We will be offering Kubernetes training on Monday and Tuesday prior to the event, for both registered conference attendees and anyone else who wants to join. You will have the opportunity to meet Kubernetes co-creators and Heptio founders Craig McLuckie and Joe Beda, get a signed copy of O’Reilly’s “Kubernetes Up and Running”, co-authored and signed by Joe, and join us for happy hour. A few seats remain, so sign up now!</p><p><a href="http://sched.co/CUkp">Introduction to Kubernetes and Containers</a> — Monday, December 4th</p><p><a href="http://sched.co/CUlx">Kubernetes Hands-On Workshop</a> — Tuesday, December 5th</p><p>Can’t join us for training at KubeCon? Check out our other scheduled courses at <a href="https://heptio.com/services/training/">heptio.com/services/training</a>.</p><p><strong>Conference sessions</strong></p><p>This year we have seven conference sessions where you will get the opportunity to learn about specific topics from Heptio team members. Come check these out and get your questions answered.</p><p>Thursday</p><ul><li>10:20 am: <a href="http://sched.co/CUET">Keynote: The Road Ahead on the Kubernetes Journey</a> — Craig McLuckie, CEO</li><li>11:10 am: <a href="http://sched.co/CU8L">The Road to More Usable Kubernetes</a> — Joe Beda, CTO</li><li>11:10 am: <a href="http://sched.co/CU67">Building a Cluster Management API using Kubicorn </a>— Kris Nova, Senior Developer Advocate at Heptio, and Robert Bailey, Google</li><li>11:55 am: <a href="http://sched.co/CU6D">Building Helm Charts From the Ground Up: An Introduction to Kubernetes </a>— Amy Chen, Software Engineer</li><li>2:00 pm: <a href="http://sched.co/CU77">Hybrid-Cloud, HIPAA Compliant Enterprise with Kubernetes</a> — Steve Sloka, Senior Systems Software Engineer</li></ul><p>Friday</p><ul><li>2:00 pm: <a href="http://sched.co/CU6b">Disaster Recovery for your Kubernetes Clusters</a> — Andy Goldstein, Staff Software Engineer, &amp; Steve Kriss, Senior Systems Engineer</li></ul><p><strong>A few other activities</strong></p><ul><li>Wednesday 7:45 am: <a href="http://sched.co/D4DQ">The NewStack Pancake Breakfast &amp; Podcast: What is service mesh technology, why are we hearing about it and why should we care?</a> Kris Nova, Senior Developer Advocate at Heptio (along with William Morgan — CEO, Buoyant)</li><li>Wednesday 3:00–4:15 pm: Kris Nova will be signing copies of her book “Cloud Native Infrastructure” from O’Reilly, in Meeting Room 1, Level 1.</li></ul><p>Looking forward to seeing everyone in Austin!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91e4d12330b5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/heptio-blog/https-blog-heptio-com-heptio-guide-to-kubecon-cloudnativecon-2017-91e4d12330b5">Heptio Guide to KubeCon + CloudNativeCon 2017</a> was originally published in <a href="https://medium.com/heptio-blog">Heptio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Kubernetes Up and Running”, a Free eBook Excerpt from O’Reilly and Heptio]]></title>
            <link>https://medium.com/heptio-blog/kubernetes-up-and-running-a-free-ebook-excerpt-from-oreilly-and-heptio-44778c906610?source=rss-311685319c12------2</link>
            <guid isPermaLink="false">https://medium.com/p/44778c906610</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[heptio]]></category>
            <category><![CDATA[company]]></category>
            <dc:creator><![CDATA[Eryn Muetzel]]></dc:creator>
            <pubDate>Tue, 07 Nov 2017 15:32:03 GMT</pubDate>
            <atom:updated>2017-11-07T15:32:03.568Z</atom:updated>
            <content:encoded><![CDATA[<p>We are excited to announce the availability of a new eBook, <a href="http://go.heptio.com/kubernetes-up-and-running">“Kubernetes Up and Running”</a>, co-authored by our CTO, Joe Beda. Heptio has teamed up with O’Reilly to offer this excerpt as a free download.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/402/1*9c9Z3lfPyJpqR24YSEyw4Q.png" /></figure><p>Joe, Craig McLuckie (Heptio CEO), and Brendan Burns originally created Kubernetes with the goal of radically simplifying the task of building, deploying, and maintaining distributed systems. Kubernetes was developed based on a decade of experience deploying scalable, reliable systems in containers at Google; but the power of Kubernetes lies in its applicability for organizations of all sizes, including individual developers.</p><p>This book is a practical guide to the core concepts of Kubernetes. It also delves into the reasoning behind choosing those concepts and and how they can be used to improve the development, delivery, and maintenance of distributed applications. The excerpt begins with more introductory topics including how to take advantage of common commands for the kubectl command-line tool and how to deploy an application using pods, labels, and annotations, and follows with more advanced topics such as service discovery, ConfigMaps, secrets, and the deployment object.</p><p>Joe and Craig started Heptio to bring the power of cloud native systems and Kubernetes to every organization. We are proud to sponsor this excerpt to help developers and operators get started with Kubernetes.</p><p><a href="http://go.heptio.com/kubernetes-up-and-running">Get your free excerpt of “Kubernetes Up &amp; Running” today</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44778c906610" width="1" height="1" alt=""><hr><p><a href="https://medium.com/heptio-blog/kubernetes-up-and-running-a-free-ebook-excerpt-from-oreilly-and-heptio-44778c906610">“Kubernetes Up and Running”, a Free eBook Excerpt from O’Reilly and Heptio</a> was originally published in <a href="https://medium.com/heptio-blog">Heptio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making Kubernetes easier to use: Sonobuoy, ksonnet, and Ark…oh my!]]></title>
            <link>https://medium.com/heptio-blog/making-kubernetes-easier-to-use-ksonnet-sonobuoy-and-ark-oh-my-689b6a0ee1e2?source=rss-311685319c12------2</link>
            <guid isPermaLink="false">https://medium.com/p/689b6a0ee1e2</guid>
            <category><![CDATA[ksonnet]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[sonobuoy]]></category>
            <category><![CDATA[heptio-ark]]></category>
            <category><![CDATA[heptio]]></category>
            <dc:creator><![CDATA[Eryn Muetzel]]></dc:creator>
            <pubDate>Thu, 19 Oct 2017 16:08:12 GMT</pubDate>
            <atom:updated>2017-10-19T17:12:14.135Z</atom:updated>
            <content:encoded><![CDATA[<p>The adoption of Kubernetes has been truly astounding, but at Heptio we speak to many organizations that still face considerable challenges in deploying and operating Kubernetes clusters and the applications that run on top. In a recent <a href="https://thenewstack.io/week-numbers-kubernetes-implementations-good-bad-ugly/">New Stack survey</a>, 75% of respondents <em>not</em> using Kubernetes in production stated that complexity of implementation and maintenance impacted their decision “to a great extent” or “somewhat”. This outweighed other factors including competing projects and alternative solutions, and precluded them from using Kubernetes.</p><p>Over the past year, Heptio has led the development of <a href="http://heptio.com/open-source">three open source tools</a> that fill operational gaps in Kubernetes that we’ve seen our customers experience. These tools enable developers and operators to easily determine whether a Kubernetes cluster is properly set up, define Kubernetes configurations, and back up and recover cluster resources.</p><p>But when should each tool be used? And how do they fit together?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HGf85tRCH21gZWr04bIbwA.png" /><figcaption><strong>Overview of Heptio open source tools</strong></figcaption></figure><h3><strong>Heptio Sonobuoy: Ensure your cluster is conformant</strong></h3><p><em>My cluster has just been set up. Before I deploy any applications, how do I know that it is actually “correct” and will behave as intended?</em></p><p>One result of the wide-scale adoption of Kubernetes by a diverse community is a plethora of ways to set up a Kubernetes cluster — on bare metal with kubeadm or a homegrown solution, on AWS with kops or kubeadm, or on GKE or ACS. Things can get complex fast, and oftentimes it’s difficult to decipher whether a given Kubernetes cluster is properly configured (i.e. conformant). When a developer goes to deploy an application on Kubernetes, how do they know that the required APIs for their application deployment are supported by the cluster?</p><blockquote><em>Without conformance, the key goals of Kubernetes, including portability and automated deployment, cannot be achieved.</em></blockquote><p>We created the open source tool <a href="https://github.com/heptio/sonobuoy">Sonobuoy</a> to provide operators and developers a way to test a local deployment of Kubernetes and make sure that it works properly. Sonobuoy makes it easier to understand the state of a Kubernetes cluster by running a set of Kubernetes conformance tests in an accessible and non-destructive manner. Its diagnostics provide a customizable, extendable, and cluster-agnostic way to generate clear, informative reports about your cluster, regardless of your deployment details.</p><p>A few weeks back, we introduced <a href="http://scanner.heptio.com/">Sonobuoy Scanner</a>, a free web-based tool that helps you install and run Sonobuoy. The tool provides a user interface to view conformance test results and drill down into the specific tests that failed.</p><h3><strong>ksonnet: Simplify the work of writing your Kubernetes configurations</strong></h3><p><em>My cluster is properly set up, and now I’m ready to deploy my application. How do I define Kubernetes configurations so that my app is deployed the way I intend?</em></p><p>While containers and Kubernetes have in many ways made life exponentially easier for developers, the task of writing Kubernetes configurations to deploy applications remains complex. We introduced <a href="https://github.com/ksonnet/ksonnet">ksonnet</a> with Box, Microsoft and Bitnami to make it easier for developers to configure applications in Kubernetes. ksonnet is based on the jsonnet templating library, and works as an abstraction layer to Kubernetes YAML. You can leverage community-provided templates, or build your own — ksonnet is designed to be easy to use, yet extensible and powerful enough to cover as many scenarios as possible.</p><p>ksonnet is particularly useful in a few additional scenarios. First, say a developer wants to deploy the same application to an AWS cluster and an on-premise bare metal cluster. With ksonnet, the Kubernetes configuration for one environment can easily be reused for the other, while still providing the flexibility to make environment-specific customizations. Second, say an application is deployed to a production environment and a change is made in the production stack (e.g. a networking configuration). Rather than rewriting the entire Kubernetes configuration, just that one variable in ksonnet needs to be updated.</p><h3><strong>Heptio Ark: Recover your Kubernetes clusters in the case of disaster</strong></h3><p><em>My cluster is conformant, and my application is deployed and running…but what happens in the case of disaster?</em></p><p>In production use of Kubernetes, managing cluster backups and restorations is time-consuming and error-prone. This is particularly true when stateful workloads are involved — figuring out the exact association between a volume snapshot and its pod(s) at a specific moment in time can be tricky.</p><p><a href="https://github.com/heptio/ark">Heptio Ark</a> solves this problem by providing a simple, configurable, and operationally robust way to back up and restore your applications and persistent volumes from a series of checkpoints. Ark is also a useful tool for migrating Kubernetes resources from one environment to another, and replicating your production environment to create development and testing environments.</p><p>We are excited by the traction of these open source tools, and invite you to <a href="https://heptio.com/open-source/">check them out for yourself</a>. And as always, we welcome your contributions and <a href="https://heptio.com/about/contact/">feedback</a>. Kubernetes still has a long way to go before we can truly automate away the pain of deploying and operating distributed systems — and we are excited to work together with the community on this journey.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=689b6a0ee1e2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/heptio-blog/making-kubernetes-easier-to-use-ksonnet-sonobuoy-and-ark-oh-my-689b6a0ee1e2">Making Kubernetes easier to use: Sonobuoy, ksonnet, and Ark…oh my!</a> was originally published in <a href="https://medium.com/heptio-blog">Heptio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Becoming a Cloud Native Organization”, a Free eBook from Heptio and the Linux Journal]]></title>
            <link>https://medium.com/heptio-blog/becoming-cloud-native-a8b82be02d27?source=rss-311685319c12------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8b82be02d27</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[heptio]]></category>
            <dc:creator><![CDATA[Eryn Muetzel]]></dc:creator>
            <pubDate>Thu, 12 Oct 2017 17:04:51 GMT</pubDate>
            <atom:updated>2017-10-13T18:58:18.153Z</atom:updated>
            <content:encoded><![CDATA[<p>We are excited to announce the availability of a new eBook, <a href="http://go.heptio.com/becoming-cloud-native">“Becoming a Cloud Native Organization”</a> written by our very own Joe Beda. Heptio has teamed up with the Linux Journal to offer this eBook as a free download.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/319/1*d7WZ4rogQsn8CR5008dNnQ.png" /></figure><p>The tech world is abuzz with the promises of “cloud native computing”, based on the architecture and culture defined by internet giants such as Google. But what does “cloud native” really mean, and more importantly, how can your organization benefit?</p><p>Automation and new architectures are important cloud native technologies; they can help you develop and deploy your products faster and manage product complexity more efficiently. But at its root, cloud native thinking is as much about teams, people, and culture as it is about technology.</p><p>Download this free eBook to learn new ways to think about cloud native computing, and how best to transition your organization to become truly cloud native.</p><p>The eBook explains the benefits of moving to a cloud native architecture, discusses how to apply cloud native in practice including the required cultural shift, provides key considerations for running containers and microservices, and covers at a high level the security best practices for the cloud-native world.</p><p>Heptio is proud to offer this eBook, as we are incredibly excited to help bring the benefits of cloud native to the wider IT industry. Our company’s training, professional services, and support speed integration of Kubernetes and related technologies into the fabric of enterprise IT, while our products reduce the cost and complexity of running these systems in production environments.</p><p><a href="http://go.heptio.com/becoming-cloud-native">Get your free copy of “Becoming a Cloud Native Organization” today.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8b82be02d27" width="1" height="1" alt=""><hr><p><a href="https://medium.com/heptio-blog/becoming-cloud-native-a8b82be02d27">“Becoming a Cloud Native Organization”, a Free eBook from Heptio and the Linux Journal</a> was originally published in <a href="https://medium.com/heptio-blog">Heptio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>