<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nebraska on Flatcar Container Linux</title>
    <link>/tags/nebraska/</link>
    <description>Recent content in Nebraska on Flatcar Container Linux</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>Copyright © The Flatcar Project Contributors.

Copyright © Flatcar a Series of LF Projects, LLC.

For website terms of use, trademark policy and other project policies please see &lt;a href=&#34;https://lfprojects.org/policies/&#34;&gt;lfprojects.org/policies&lt;/a&gt;.
</copyright>
    <lastBuildDate>Thu, 07 Nov 2019 16:25:00 +0100</lastBuildDate>
    <atom:link href="/tags/nebraska/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Announcing the Kinvolk Update Service and Nebraska Project</title>
      <link>/blog/2019/11/announcing-the-kinvolk-update-service-and-nebraska-project/</link>
      <pubDate>Thu, 07 Nov 2019 16:25:00 +0100</pubDate>
      <guid>/blog/2019/11/announcing-the-kinvolk-update-service-and-nebraska-project/</guid>
      <description>&lt;p&gt;In this post, we’ll dive into the details of Kinvolk Update Service and share more about the heritage, functionality, and implementation. Of course, Kinvolk Update Service is built on 100% Open Source Software, which we are also making available today &#xA;&#xA;&#xA;&lt;a href=&#34;https://github.com/kinvolk/nebraska&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;on github&lt;/a&gt;&#xA; as the Nebraska project.&lt;/p&gt;&#xA;&lt;h2 id=&#34;motivation&#34;&gt;Motivation&lt;/h2&gt;&#xA;&lt;p&gt;When having a number of Flatcar Container Linux instances that compose a cluster, it is useful to have a tool to roll out updates, and to monitor the status of the instances and the updates progress. i.e. How many instances are currently downloading version X.Y.Z in our cluster? And how many should be updated to the new beta version?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
