Huawei’s Container and Cloud Native Journey – As A User, Vendor and Contributor

By | Blog

Huawei is one of the largest telecommunications equipment manufacturers in the world. It has eight data centers for its internal I.T. department, which run 800+ applications in 100K+ VMs to serve 180,000 employee users.

Huawei recently turned to containerization and Kubernetes, which the company discovered brings agility, scale-out capability, and DevOps practice to cloud-based applications. To learn more, read the in-depth case study.

In the past, Huawei used virtual machines to encapsulate applications, but every time it would start a VM, it took a lot of time. The rapid increase of new applications and the cost and efficiency of management and deployment of VM-based apps created critical challenges.

Development cycles decreased from a week to minutes using a Kubernetes-based Platform as a Service (PaaS) solution. Operating expenses went down, in some circumstances by 20-30 percent. Both a user and a vendor, the company has built the technologies into FusionStage™, the PaaS solution it offers its customers.

Huawei has also grown to become the No. 3 Kubernetes contributor and is a Platinum CNCF member. Be sure to check out Huawei’s Peixin Hou talking about how cloud and open source facilitate digital transformation from last year’s LinuxCon, ContainerCon China, and Dr. Ying Xiong’s KubeCon Berlin keynote “Cloud Native in the Enterprise: Production, Best Practice and Innovation.”

January 2018: OpenTracing Project Newsletter

By | Blog

Members of OpenTracing made a New Year’s Resolution in 2018 to communicate the progress made by the project regularly and consistently. To that end, this is the first of many posts to come. Read on to learn about what happened in and adjacent to OpenTracing in the month of January 2018.

OpenTracing Project Updates

DataDog, New Relic, Instana, and Skywalking Joined the OpenTracing Specification Council

The following people+projects have recently joined the OTSC:

To learn more about the OTSC and its responsibilities, please check out the project organization document.

Kicking Off Documentation and Language Maintainers Projects

Ted Young is kicking off two working groups in OpenTracing:

  • The Documentation Working Group is codifying the existing knowledge base to create complete documentation, so it can be easily accessed via the OpenTracing website. Start helping now!
  • The Cross-Language Working Group manages the OpenTracing APIs and ecosystem. The goal is to staff each language with two contributors. Join in!

Core API and Official OpenTracing Contributions

Java v0.31 Launched

The latest version of the Java API has been released. This version replaces the experimental context propagation introduced in v0.30.

Though v0.31 “sounds” like a small change from v0.30, in pre-1.0 semver tradition there are major and consequential improvements in this release, and it involved months of cross-organization collaboration and testing.


  • BaseSpan and ActiveSpan are simplified into a single Span class.
  • Scope replaces ActiveSpan, removing Continuations.
  • ScopeManager replaces ActiveSpanSource.
  • Tracer.activeSpan() returns the current value of Tracer.scopeManager().active().span() as a convenience.
  • startManual() deprecated in favor of start().
  • Removed log.(Object) methods.
  • Created new examples directory.

To allow both v0.30 and v0.31 context propagation to work together, a backwards-compatibility layer has been created. Learn more.

Java Spring Messaging

As part of OpenTracing’s growing support for Spring, Spring Messaginginstrumentation has now been added. Please also check out the main Spring Cloud OpenTracing project.

Community Contributions

Spring Cloud Sleuth announced Support for OpenTracing

Spring Cloud offers a simple and accessible programming model to the most common distributed system patterns, helping developers build resilient, reliable, and coordinated applications. Spring Cloud is built on top of Spring Boot, making it easy for developers to get started and become productive quickly. Sleuth is Spring Cloud’s distributed tracing system and they announced support for OpenTracing.

Zipkin Implementation for OpenTracing Tracer in PHP

Built by Typeform engineer, José Carlos Chávez, this library allows OpenTracing API consumers for PHP to use Zipkin as their tracing backend.

Content From the Community:

OpenTracing in Flask Tutorial

“You may have noticed that both OpenTracing and Jaeger’s tagline mention “distributed”. Besides providing a vendor-neutral instrumentation API, OpenTracing also provides a standard way to propagate trace context across microservices. This is crucial for debugging issues if your app is composed of microservices. I like to think of it as distributed backtraces …”

by Derek Haynes, Scout App

Where Did My Messages Go? Tracing Distributed Systems with OpenTracing

“This presentation will show how to instrument your Java applications with OpenTracing to trace messages from web and mobile clients to your services and back to your data systems,by using several OpenTracing-compatible tools (Uber’s Jaeger and Zipkin) to visualize your message flows, transaction per transaction.”

by Jorge E. Q. Otoya

Distributed Tracing Workshop Update

Tracing community leaders organized a Distributed Tracing Workshop last week in Seattle. Here’s a quick recap by an attendee, Ted Young.

  • The Trace-Context specification moved steadily towards consensus, but work continues.
  • Security issues around Correlation Context were discussed. Unless the header contents are encrypted, there is a chance that they could be leaked to a third party.
  • Lots of interest in 100% Tracing, service mesh integration, common data formats.
  • Wu Sheng presented SkyWalking, newly accepted to Apache.
  • OpenTracing and OpenCensus gave project updates.

Ways to Engage

Community Collaboration on CFPs

OpenTracing contributors, users, and enthusiasts from companies including ScoutApp, LightStep, Scytale, DataDog, and Prometheus collaborated on conference calls for papers in January. OpenTracing-related talks were submitted to KubeCon + CloudNativeCon Europe, Monitorama, Velocity, and DockerCon.

If you have suggestions of conferences we should attend or would like to collaborate on a CFP, send a note to

OpenTracing at Testing in Production Meetup

Priyanka Sharma will be speaking about “Testing and Debugging in Production with Distributed Tracing” at the Testing in Production meetup on February 20, 2018 at Heavybit in San Francisco. Please stop by if you’re in the area.

Share Your Experience and Feedback

We’d love to collaborate on any case studies showing OpenTracing usage in production environments. If you’re interested, send us a note at!

Want to share an OpenTracing-related update in the newsletter? Email us at Also, this our first post and we’d love feedback, so don’t hesitate to drop us a line!

Diversity Scholarship Series: KubeCon – Endless Opportunities and The Connections You’ll Make

By | Blog

CNCF offered 103 diversity scholarships to developers and students to attend KubeCon + CloudNativeCon North America 2017. In this post, our scholarship recipient Cheryl Fong, student at University of New Hampshire (UNH) majoring in Computer Science, shares her experience attending sessions and meeting the community. Anyone interested in applying for the CNCF diversity scholarship to attend KubeCon + CloudNativeCon Europe 2018 in Copenhagen May 2-4, can submit an application here. Applications are due March 2nd.

By Cheryl Fong, student at University of New Hampshire (UNH) majoring in Computer Science


As a fairly new member of the Kubernetes community, my interaction with the community has been overwhelmingly welcoming. Usually offering help even before needing to ask. As a word of encouragement and gratitude, please continue to help each other as you have certainly helped me.

Short Intro:

Learning about Kubernetes wasn’t a straight path, it was something I stumbled upon since there was no one around me that has heard of it, and even if they did they wouldn’t know where to begin. It was through learning about operating systems that I found myself in a world all about containers, which lead me to find Kubernetes, i.e. a way to orchestrate containers!

As a college student, it can be challenging to juggle coursework and work on a side project at the same time. Learning about Docker and Kubernetes happened to be just one of those. Finding that balance is tedious but with practice, flexibility and motivation, anyone can do it!

More about who I am

Was I the right person for the Scholarship?

Upon receiving the KubeCon scholarship, it arose ambivalent feelings. Being someone who just got into using Docker and Kubernetes, and probably not having that much practice or good use cases, made it seemed like I won the lottery.

I was indeed happy to be selected but wondered if I was taking someone else’s invaluable spot? Thoughts about whether I was the right person to attend lingered even while I was at the conference.

However, the EmpowerHer event on Day 0 of KubeCon helped me learn to put my self-doubts aside. There were at most 100 women at this event, it was very casual and everyone was deep in conversation when I arrived. No men were to be seen yet.

Meeting a young lady whom I shall call Miss Potential, went on a personal self-growth journey with me that event night. Miss Potential hold a professional composure, though she did not have a college degree, she was employed at WP Engine (a company heavily focused on diversity and equality), felt absurdly insecure. What made it interesting, was that she had the kind of presence that would strike as outwardly confident.

It was through group conversations with the women at the event especially, with the more experienced, high position-holding group of professionals, that a common theme resonated; “Feeling not up to the task happens, it is up to ourselves to improve, keep our emotions in check, know what we don’t know and keep on learning.” I felt a confidence increase after attending this event and relieved as being reassured, and sure as well Miss Potential did too. Many thanks to those who’ve organized this gathering.

Worthy Mentions:

There were a myriad of talented and driven individuals from all over the world that attended this conference. KubeCon, the Kubernetes community and CNCF would be very different from what it is today without them.

In not any particular order or preference, I like to mention a few individuals to show admiration and appreciation for what they do for the community and hope that they continue to do so. This doesn’t exclude those who weren’t mentioned.

Marcos was the very first person I’ve met who was attending KubeCon, on the airport #1 bus traveling downtown. If I hadn’t summon the courage to talk to him at the very last minute before stepping off, I might not have met Justin nor would getting around Austin, TX for the first time be so easy. Turns out he was a scholarship recipient, and impressively, he is a Docker and Kubernetes maintainer and as well as the creator for Docker and Kubernetes tutorials e.g. Play with Kubernetes.

Meeting Justin was by accident (he just happened to walk up to the table where Marcos and I were eating hot wings). He was the kind of professor you could feel relaxed hanging out with and could go bar hop. Which was exactly what we did on Rainey Street, that cold night (Day 2 & 3) with a couple of others we’ve just met. He was brilliant in every way imaginable, great at explaining things he worked on and was simply easy to talk to.

Atoms of Confusion is one of the things that he’s currently leading at NYU along with The Update Framework (TUF):

A framework that provides protection against data tampering, key compromise and many other more esoteric attacks and addresses weak links in today’s software update systems and signing strategies.

Watch this video on What is TUF and How to use it.

A snippet of from Atoms of Confusion I like to share:

A Preprocessor in a Statement:

int V1 = 1
#define M1 1

Actually means:

int V1 = 1+1;
#define M1 1


More of these can be found on the Atoms of Confusion data page.

Takuya was among men that came to the EmpowerHer event around the time that it was ending. He traveled all the way from Tokyo, Japan and was also one of the scholarship recipients. Our encounter was interesting as he thought I was some girl from China he met earlier which provided the opportunity for a conversation.

As a contributor to Gitlab, Docker, Kubernetes and Prometheus over his free time, he stretches it further (in addition to having a full time job and a family of four) to organise meetups by providing presentations and inviting guest to speak in Tokyo for these respective technologies as well! In fact, he is also a Cloud Native Ambassador.

His most recent organised meetup:



Here some great people that affected my life positively:

Special thanks to:

Erica Von Buelow from CoreOS

Erica, you have given me more than I can ask for!

Many thanks to:

Amanpreet Singh from Crowdfire and Balakarhikeyan Raja a scholarship recipient and creator of who both traveled all the way from India and made my experience at KubeCon memorable.

Also, Thank you Natasha Woods for helping me put the blog post together and having it live on the Internet!

Final thoughts:

Not only has KubeCon opened my eyes to new technology, taught me new tricks and skills, provided me motivation, gave me new experiences but also exposed me to a network of people that I still talk to today. KubeCon has all-around improved my life someway.

If you haven’t contributed to Kubernetes before, contributing to the documentation is a good way to start. Open source contributioncan be in many forms, it doesn’t have to be code.

Dear reader, if you were interested in applying for the CNCF Diversity Scholarship for KubeCon. I urge you to do so quickly!

I’ll end this blog post with a dynamic photo gallery of what I personally saw at KubeCon.

Walkthrough of my experience at KubeCon from Day 0 to Day 3:

Day 0

Day 1

Day 2 & Day 3

The CNCF takes steps toward serverless computing

By | Blog

By Swapnil Bhartiya

The Cloud Native Computing Foundation (CNCF) Serverless Working Group (WG) has announced a whitepaper and serverless landscape that marks their first output since the working group was created in 2016.

Why it matters

Even though the idea of ‘serverless’ has been around since 2006, it is a relatively new concept. It’s the next step in the ongoing revolution of IT infrastructure that goes back to the days when one server used to run one application.

Many vendors and users who attended KubeCon Austin expressed a growing interest in serverless computing. Platform 9 conducted a survey at the event and Functions as a Service (FaaS) came up as the third most popular use case for communities. In a recent survey conducted by the CNCF, 41% respondents said they are using serverless technology.

Being a new concept, there is a lot of curiosity and confusion around serverless computing. People are asking questions: What is it? Who is it for? Is it a replacement for IaaS, PaaS and containers? Does that mean the days of servers are over? What are the benefits? What are the drawbacks?

The role of CNCF in serverless computing

The CNCF is the cornerstone of the ongoing cloud-native movement. The foundation is home to core cloud-native technologies, including the seed project Kubernetes. The CNCF has played a pivotal role in helping the Kubernetes and container ecosystems grow; it now needs to play the same role in the open source serverless space.

CNCF created the Serverless Working Group to ‘explore the intersection of cloud native and serverless technology.’ The first output of the group was creation of serverless landscape, which is available here. The whitepaper is the second contribution of the Serverless Working Group. The whitepaper goes beyond merely answering the questions facing the serverless community; it defines serverless computing:

“Serverless computing refers to the concept of building and running applications that do not require server management. It describes a finer-grained deployment model where applications, bundled as one or more functions, are uploaded to a platform and then executed, scaled, and billed in response to the exact demand needed at the moment.”

Some highlights of the whitepaper are:

  • What is serverless computing?
  • What are the differences between Functions as a Service (FaaS) and Backend as a Service (BaaS)?
  • What are the benefits of serverless computing?
  • What are the drawbacks?
  • What’s the difference between serverless and other cloud native technologies?
  • Which of the three cloud native technologies you should use?
  • Use cases of serverless computing, providing examples of solutions already in use.

From a technology perspective, the whitepaper also details how the serverless processing model actually works.

Advancing serverless adoption

“Serverless is a natural evolution of cloud-native computing. The CNCF is advancing serverless adoption through collaboration and community-driven initiatives that will enable interoperability,” said Chris Aniszczyk, COO, CNCF.

The whitepaper also explores the role the CNCF should be playing in this space. One thing is quite clear – as a new technology there is a lack of standardization and interoperability between cloud providers that may lead to vendor lock-in. There is a need for quality documentation, best practices, and more importantly, tools and utilities. Mostly, there is a need to bring different players together under the same roof to drive innovation through collaboration.

The good news is that the CNCF is exploring many of these possibilities. The whitepaper lists some of those areas, including:

  • Efforts to encourage more serverless technology vendors and open source developers to join the CNCF.
  • Ways to foster an open ecosystem by establishing interoperable APIs, ensuring interoperable implementations with vendor commitments and open source tools.
  • New interoperability and portability initiatives similar to CSI and CNI with the help of both platform providers and third-party developer library creators.

Being a new technology, the CNCF whitepaper recognizes the importance of education. It suggests the CNCF should provide a set of design patterns, reference architectures, and common vocabulary for new users.

Some of this work has already started. The whitepaper itself is result of those efforts. The CNCF Serverless Working Group worked with Redpoint Ventures to highlight some of the major serverless projects:

Join the serverless movement

The primary goal of the whitepaper is to start an intellectual dialog around serverless computing, to engage stakeholders of this emerging ecosystem as well as gather feedback. The whitepaper creates an opportunity for organizations to get involved in the serverless movement. You can get involved in the discussion in many ways.  

To get involved in CNCF’s work to advance serverless computing, join the CNCF Serverless Working Group or the community project CloudEvents, a draft specification for a common, vendor-neutral format for event data that is aimed to be proposed to the CNCF TOC as an official project later this year.

This Week in Kubernetes: February 5th

By | Blog

Each week, the Kubernetes community shares an enormous amount of interesting and informative content including articles, blog posts, tutorials, videos, and much more. We’re highlighting just a few of our favorites from the week before. This week we’re talking machine learning, scalability, service mesh, and contributing to Kubernetes.

The Full-Time Job of Keeping up With Kubernetes, Gravitational

If you’ve ever wonder what goes into maintaining an open-source project with as much velocity as Kubernetes, this article is a great place to start. Abraham Ingersoll from Gravitational dives into the inner workings of SIGs and working groups, the Kubernetes release cycle, feature development process, and community support.

When to use Serverless? When to use Kubernetes?, Heidloff.Net

As the cloud native landscapes evolve, more and more questions come up as to when to use Kubernetes and when to use Serverless to build an application. In this article, Niklas Heidloff from IBM outlines the pros and cons of each option and how to decide what’s best for your use case.

Scheduling in Kubernetes, Alexandrutopliceanu.Ro

Scheduling in Kubernetes helps ensure that pods are only placed on nodes that have sufficient free resources. In this post, Alexandru Topliceanu from walks you through the implementation of the default scheduler in Kubernetes. Dive into the genericScheduler, volumes, algorithm, predicates, custom scheduler, and more to learn how to support long-running processes.

Kubernetes Autoscaling Based on Custom Metrics Without Using a Host Port, Medium

Autoscaling is one of the most useful features in Kubernetes, but autoscaling based on custom metrics can be complicated to set up since it’s still an alpha feature. In this Medium post, Marko Lukša from Red Hat shows you how to set up horizontal pod autoscaling based on application-provided custom metrics on minikube.

Stay tuned for more exciting content from the Kubernetes community next week, and join the KubeWeekly mailing list for the latest updates delivered directly to your inbox.

Is there a piece of content that you think we should highlight? Tweet at us! We’d love to hear what you’re reading, watching, or listening to.

CNCF to Host Vitess

By | Blog

Today, the Cloud Native Computing Foundation (CNCF) Technical Oversight Committee (TOC) voted to accept Vitess as the 16th hosted project, alongside Kubernetes, Prometheus, OpenTracing, Fluentd, Linkerd, gRPC, CoreDNS, containerd, rkt, CNI, Envoy, Jaeger, Notary, TUF and Rook. Vitess has been accepted as an incubation-level project, under the CNCF Graduation Criteria v1.0.

The TOC’s Graduation Criteria provides every CNCF project an associated maturity level of either inception, incubating or graduated. As an incubating project, Vitess must document it is being used successfully in production by at least three independent end users, have a healthy number of committers and demonstrate a substantial ongoing flow of contributions.

Originally created as an internal solution by YouTube to handle scaling for massive amounts of storage, Vitess is a database orchestration system for horizontal scaling of MySQL through generalized sharding. By encapsulating shard-routing logic, Vitess allows application code and database queries to remain agnostic to the distribution of data onto multiple shards. With Vitess, organizations can even split and merge shards as needs grow, with an atomic cutover step that takes only a few seconds. Companies like BetterCloud, Flipkart, Quiz of Kings, Slack, Square Cash, Stitch Labs and YouTube are using Vitess across various stages of production and deployment. Organizations including, GitHub, HubSpot, Slack, and Square are also active contributors to the project.

“Slack is in the midst of a major migration of the MySQL infrastructure at the core of our service, driven by the need for an architecture that scales to meet the growing demands of our largest customers and features under the pressure to maintain a stable and performant service that executes billions of MySQL transactions per hour, said Michael Demmer, Senior Staff Engineer at Slack. “We needed a solution that would offer a familiar full featured SQL interface, and wanted to continue to use MySQL as the backing store to maintain our operations knowledge and comfort level. Vitess is a natural choice for this purpose and has served us well so far.”

Vitess has been under development since 2010. The earliest version was a connection proxy that helped to buy some headroom, but over time the features evolved, while the tools and servers grew to be more efficient, fault tolerant, and manageable. This iterative journey led to what Vitess has become today: a distributed, cloud-based storage solution that exhibits some of the best properties of a relational database.

“Faced with rapid organic and internal growth at YouTube, we had to come up with something that would leap ahead of the curve instead of just fighting fires. When we finally built the initial feature list for Vitess, it was obvious that we were addressing problems that are common to all growing organizations,” said Sugu Sougoumarane, CTO at PlanetScale Data and Co-creator of Vitess. “Our collaboration with Kubernetes over the last two years means anyone can now run Vitess the way YouTube does: dynamically scaled and scheduled in a container cluster. We’re excited to work with the CNCF to expand the capabilities of Vitess even further.”

Main features:

  • Combines important MySQL features with the scalability of a NoSQL database
  • Enables MySQL to run in the cloud
  • Cloud-native functionality such as support for automatic failover/recovery, replication and rolling upgrades
  • Vertical and horizontal sharding support, and virtually seamless dynamic re-sharding
  • Multiple sharding schemes, with the ability to plug-in custom ones
  • Query routing, rewriting and sanitization, blacklisting, streaming, and de-duping
  • Master management tools (handles reparenting)
  • Performance analysis tools

Technical Specs:

  • Backend components implemented in Go
  • Continuously tested against Ubuntu 14.04 (Trusty) and Debian 8 (Jessie). Other Linux distributions should work as well
  • Supports MySQL 5.6, MariaDB 10.0, and any newer versions
  • VTGate server is the main entry point applications use to connect to Vitess
  • Supports data backups to either a network mount (e.g. NFS) or to a blob store

“To build successful cloud native applications, developers have to consider new ways of managing storage,” said Chris Aniszczyk, COO of Cloud Native Computing Foundation and Vice President of Developer Relations at The Linux Foundation. “Vitess is a fantastic example of bridging the existing popular MySQL database and scaling it in a cloud native fashion.”

The open source Vitess project runs best in a containerized environment. With Kubernetes and Google Kubernetes Engine as the container cluster manager, it’s now a lot easier to get started. In this environment, Vitess provides a MySQL storage layer with improved reliability, scalability, and manageability. Kubernetes handles scheduling onto nodes in a compute cluster, actively manages workloads on those nodes, and groups containers comprising an application for easy management and discovery. Also with Kubernetes, Vitess even becomes agnostic to the underlying choice of cloud platform, providing cloud portability with no vendor lock-in.

Notable Milestones:

  • 105 contributors
  • 5,413 GitHub stars
  • 15 releases
  • 13,733 commits
  • 707 forks

“A big advantage of cloud solutions is easy horizontal scalability, but when it comes to stateful systems such as databases, the problem is that application complexity and operational overhead tend to scale up along with the number of instances,” said Brian Grant, TOC representative and project sponsor. “A cloud-native solution like Vitess abstracts the complexity of horizontal scalability from both application developers and database operators. We’re thrilled to welcome Vitess as a CNCF project as we continue to enable more classes of workloads in cloud-native environments.”

As a CNCF hosted project, Vitess is part of a neutral cloud native foundation aligned with its technical interests, as well as the larger Linux Foundation, which provide the project with project governance, marketing support and community outreach.

For more on Vitess, read DZone’s Launching Vitess: How to Run Youtube’s MySQL Sharding Engine, or watch the the recording of the Vitess beyond YouTube session from Percona Live Open Source Database Conference 2017. You can also read Vitess’ guide to getting started on Kubernetes.

This Week in Kubernetes: January 29th

By | Blog

Each week, the Kubernetes community shares an enormous amount of interesting and informative content including articles, blog posts, tutorials, videos, and much more. We’re highlighting just a few of our favorites from the week before. This week we’re talking machine learning, scalability, service mesh, and contributing to Kubernetes.

Q&A on Machine Learning and Kubernetes with David Aronchick of Google

Machine learning has been gaining a lot of attention, especially at KubeCon in Austin, TX this past December. Rags Srinivas of InfoQ sat down with David Aronchick, product manager at Google and contributor to Kubeflow, to discuss Kubernetes and machine learning. Take a look at how machine learning is changing businesses today, and how Kubernetes offers a common platform for deploying and running ML platforms at scale.

Scaling Kubernetes to 2,500 Nodes

OpenAI, has been running Kubernetes for deep learning research for the past two years. Kubernetes allows for fast iteration cycle, reasonable scalability, and lack of boilerplate making experimentation at OpenAI quick and easy. Learn how OpenAI scaled its Kubernetes clusters to more than 2,500 nodes on both the cloud and physical hardware, while remaining incident free for 90 days.

Kubernetes Service Mesh

Hearing a lot about service mesh recently and wondering what your options are? On his personal blog, Alen Komljen of Semantext Group explains why service mesh is a critical component of cloud-native. From load balancing and service discovery to service monitoring and tracing, this is a great introductory post to check out if you’re interested in service mesh. Alen also dives into Conduit and Istio to showcase how these tools work.

Riding the Unicorn: A Newbie Contributor’s Guide to Kubernetes

Arun Gupta wrote this great guide on the AWS Open Source Blog for anyone who is interested in contributing to Kubernetes. The Kubernetes community is growing fast, with increasing opportunities for new contributors. Check out this guide for some ideas of where to start, from joining the conversation on Slack and community meetings to getting involved in a Special Interest Group (SIG) and much more.

Stay tuned for more exciting content from the Kubernetes community next week, and join the KubeWeekly mailing list for the latest updates delivered directly to your inbox.

Is there a piece of content that you think we should highlight? Tweet at us! We’d love to hear what you’re reading, watching, or listening to.

New Stack Makers podcast re: ebook “Kubernetes Deployment and Security Patterns”

By | Blog

Ihor Dvoretskyi’s New Stack Makers Podcast: “Making Kubernetes Core As Awesome As Possible”

This New Stack Makers podcast features highlights from the new ebook “Kubernetes Deployment and Security Patterns” due out Feb. 6. As part of CNCF’s ebook sponsorship, The New Stack Founder and Editor-in-Chief Alex Williams recently spoke to Ihor Dvoretskyi, CNCF Developer Advocate and co-lead of Product Management SIG at Kubernetes Community, about existing and emerging Kubernetes deployment patterns and the 2018 Kubernetes roadmap.

Do you also want to know about emerging patterns like serverless, machine learning, edge computing and stream analytics? Will this be the year Kubernetes is ready to support hybrid clouds and Linux and Windows environments? Will there be any drawbacks to the community’s focus on core Kubernetes this year?

Ihor answers these questions and shares more about the community’s plans to make Kubernetes core as rock solid and awesome as possible.

In the podcast, Ihor explains that many improvements today are driven by customer requirements. For example, expect to see the community deliver a set of new features that will get us closer to calling Kubernetes a multi-tenant solution. This milestone achievement will resonate with enterprise users in the market, according to Ihor. The focus on core Kubernetes will also deliver stability enhancements that will give end users the confidence they need to turn their attention to serverless and machine learning applications.

Follow CNCF’s blog and check back next week to download the full ebook for FREE.

Diversity Scholarship Series: Unity in Diversity in Kubernetes

By | Blog

CNCF offered 103 diversity scholarships to developers and students to attend KubeCon + CloudNativeCon North America 2017. In this post, our scholarship recipient Radhika Puthiyetath, Technical Writer at AppDynamics (part of Cisco Systems), shares her experience attending sessions and meeting the community. Anyone interested in applying for the CNCF diversity scholarship to attend KubeCon + CloudNativeCon Europe 2018 in Copenhagen May 2-4, can submit an application here. Applications are due March 2nd.

By Radhika Puthiyetath, Senior Information Developer at AppDynamics (part of Cisco Systems)


Radhika Puthiyetath is crafting information experience for the Business IQ product lines at AppDynamics (part of Cisco). Radhika was the Release Notes Lead for the Kubernetes 1.8 Release. Prior to Kubernetes, she had actively been involved in Apache Software Foundation, GNOME, and OpenSUSE.

The term “Unity in Diversity” refers to the state of oneness despite the presence of Diversity of all kinds. The oneness ensures the presence of, participation by, and respect for people of different interests, backgrounds, and experience. An empathetic and diverse community fosters inclusiveness. Open Source (OS) communities in general uphold their commitment to this philosophy. Talking of OS communities, Kubernetes is probably the second largest of all times, in terms of code contribution and participation. Contributors belong to different organizations with diverse interests, dabbling in different languages, focusing on different components, coexisting in harmony and contributing to a common goal–Kubernetes. Reflecting its sheer size and impact, the Kubernetes community went many steps further at championing Diversity and Inclusion in almost all aspects of community ecosystem.

The apotheosis of all OS communities, Kubernetes, under the aegis of CNCF, outshined its peer communities in its commitment to “Unity in Diversity.” CNCF granted Diversity Scholarship to all 103 applicants to attend KubeCon + CloudNativeCon 2017 in Austin, Texas. In partnership with CNCF, major cloud infrastructure incumbents, namely AWS, Google and Microsoft, as well as Twistlock jointly extended a combined $250,0000 grant to support the Diversity Scholarships. The grant helped Kubernetes enthusiasts belonging to underrepresented groups attend the most anticipated conference of the year. As such, KubeCon + CloudNativeCon 2017 emerged as an unprecedented representation of “Unity in Diversity.” More than 4,100 people from across the globe, representing 100 plus organizations, flocked to the Austin Convention center in drove, for the love of the technology that powers the infrastructure of organizations of all size. I was one of those fortunate attendees–thanks to the Diversity Scholarship. Having been through the wringer in the recent past, I was badly in need of a morale boost. Finding my name among the 30 applicants who were awarded the Scholarship in the first round gave my sagging morale a boost.

A Little About Me and My Open Source Journey

I identify myself as a woman in tech. I also represent technical writers who are as passionate as their engineering peers about technology and customer success, and yet are given the least preference when it comes to technical conferences and customer interaction. Diversity Scholarship enabled me to meet the team I closely collaborate with, whom I otherwise meet only on virtual forums. In a tech conference of this magnitude, sadly, I met only a handful of technical writers, all of them representing SIG-Doc. I sincerely hope my participation inspire my peers to utilize similar opportunities. I also hope organizations acknowledge the significant contributions of technical writers towards customer success and give them equal opportunities as their engineering peers to attend technical conferences. I am grateful that the Diversity committee recognized my identity, as a woman in tech as well as a technical writer, both under-represented groups in technical conferences. Talking about my OS journey, I embarked on this exciting jaunt at Novell dabbling in GNU Texinfo. The gratifying ride continued with GNOME (Evolution), OpenSUSE (iFolder), Apache Software Foundation (CloudStack), and CNCF (Kubernetes), every bit of which I cherish. I have participated ebulliently in GNOME Evolution and ASF CloudStack efforts for almost five years in various capacities, whereas in Kubernetes only for about five months at the time of attending Kubecon. I started contributing as the Kubernetes 1.8 Release Team member leading the effort of Kubernetes Release Notes. I also assisted the SIG-Doc team with organizing the Documentation Sprint at Kubecon and have a handful of PRs merged. The most delightful experience of all was hosting a Kubernetes community meeting.

The Kubernetes Community

Empathetic–that’s the most meaningful adjective I can think of. Though I had no solid credentials in Kubernetes, the community leads extended to me the opportunity to host a community meeting and to attend the Contributor Summit at Kubecon. My experience alone bespeaks the emphasis the community has placed on Openness, Diversity, and Inclusion. The community is indeed an embodiment of the philosophy of “Unity in Diversity”, where contributors representing competing organizations support each other despite their professional association.

Contributor Summit

The Kubernetes Contributor Summit, serving as a curtain raiser to the most anticipated conference of the year, was held on December 5. At the helm of the summit was Paris and Jorge, who opened the day with a detailed agenda to highlight what the audience could expect from the day ahead. Their friendly, indefatigable efforts set the tone for a high-energy, well-run summit. After the serious discussions around Kubernetes roadmap, the group broke for Unconferencing sessions.

Here are some bites from the “Onboarding developers through better documentation” track led by the SIG-Doc lead Jared Bhatti. One common theme resonated across attendees was “Good documentation put a stop to people repeating the same question” and “Identifying the ‘big nouns’ and related ‘big verbs’ for documenting”. The attendees united to raise voice to find ways to avoid content that no longer work. Jared kicked the discussion up a notch by elaborating how Andrew’s project on Crafting User Journeys and other projects solve many of these issues. The session wrapped up by calling participation in ongoing discussion to improve information experience. The session was astoundingly energizing time – I am really glad that we’ve had such a lively, engaging discussion. Personally, summit presented an incredible opportunity to me to meet the Governance body members and the Executive Director of CNCF, Dan Kohn himself. Dan was kind enough to share the success story of a Diversity Scholarship recipient, Kris Nova, and provide me with a mini-mentoring session. I’d also received a mini-mentoring session from the CEO of Rancher Labs, Sheng Liang on the last day of the conference. The co-creator of Kubernetes, Joe Beda, was kind enough to give me a signed copy of his book. Though I’d served the length and breadth of other OS projects such an opportunity was my first. I realized how accessible, approachable, and humble the leadership is.

Documentation Sprint

With Kubernetes Doc Maintainers

The Special Interest Group (SIG) for Kubernetes Documentation pulled together a Docs Sprint at KubeCon+CloudNativeCon. Ideas are worthless without execution by a team able to execute well. When Jared Bhatti asked us for ideas for Kubecon I’d never thought one of my suggestions, running a doc hackathon, would be considered for execution. Many thanks to the team for leading the effort and pulling off such a memorable event. The sprint included two tracks, improving user journeys and expanding the existing Kubernetes glossary to cover a broader range of terms. However, participants, though from diverse backgrounds, unanimously decided to focus on expanding the Kubernetes glossary. More than 30 terms have been added to the glossary in the event. 

EMPOWHER Evening Event

On Tuesday night of the Kubecon, ladies at the conference shed our nerdy duds and transformed ourselves into glamorous red-carpet stars. The EMPOWHER Evening Event, sponsored by Nutanix, was all about dine and shine. Personal highlight of the event was meeting with Ria Bhatia, whose YouTube channel, devops & socks, I enjoy watching.  

Takeaways from Kubecon Sessions

I took invaluable insights from several sessions. I’ll describe my personal highlights that resonated with me. Of all the talks, my favorite one is Brian Grant’s session, What is Kubernetes, An Architectural View, and I rank it among the top 3 I’ve seen at Kubecon. The session was a dense whirlwind tour on defining Kubernetes in ten different ways–from the familiar ‘container orchestrator’ to unfamiliar terms, such as Portable Cloud Abstraction. I found it fascinating that Kubernetes has been used as a toolkit for machine learning platforms. I also learned how Kubernetes is similar to and different from IAAS platforms Distributed Networking is my favorite domain. Because I’ve had a chance to document Network Policies and to play around with Calico a bit, I’ve been following  Ahmet Alp Balkan’s work and his blog series on the same topic. I can’t emphasize how meticulous Ahmet is about explaining the concepts and giving a superior information experience with carefully chosen fonts and elaborately created illustrations. The same watchful attention to details is reflected on the slides of his talk, Kubernetes Network Policies. I thoroughly enjoyed Brendan Burns talk on Metaparticle–A standard library for cloud-native development, which aids developers design, develop, and deploy their application from a single, easy to use environment. I did not miss to go over the tutorial page post Kubecon. It’s also intriguing to learn that Kubernetes landscape has expanded further with Intel’s Kata Containers and Amazon’s Elastic Container Service for Kubernetes (EKS).

Austin Downtown

The Austin Convention Center is not far from the north banks of the Colorado River. On the first day of reaching Austin, I grabbed Nikitha and headed over to Zilker Park, a few blocks of the Convention Center. Taking a winter evening stroll around Downtown and along the banks got me into the vibe of the city and soaked me up the riparian environment. After witnessing a gorgeous sunset and spectacular cityscape vistas, we returned. The beautiful city lights unfolded around us as we walked back to our respective hotels. Most attendees roomed at hotels in close proximity to the Convention Center and I bumped into a lot of folks flaunting their Kubernetes Jacket.

Final Thoughts

The mantra of KubeCon + CloudNativeCon 2017 was “Keep Cloud Native Weird.” Flooded with energizing air, the motto reverberated throughout the length and breadth of the conference, keeping it unconventional and outré in every sense. The most unconventional and “weird” fact about KubeCon + CloudNativeCon 2017 was that the community was United in Diversity.

CNCF to Host the Rook Project to Further Cloud-Native Storage Capabilities

By | Blog

Today, the Cloud Native Computing Foundation (CNCF) Technical Oversight Committee (TOC) voted to accept Rook as the 15th hosted project alongside Kubernetes, Prometheus, OpenTracing, Fluentd, Linkerd, gRPC, CoreDNS, containerd, rkt, CNI, Envoy, Jaeger, Notary and TUF.

Rook has been accepted as an inception-level project, under the CNCF Graduation Criteria v1.0An inception-level project is an early-stage project that adds value to cloud-native computing as per the CNCF charter, but may not be ready to be used in production. The CNCF supports such early-stage projects in order to foster the development of promising cloud-native technologies. The CNCF provides every project an associated maturity level of either inception, incubating or graduated.

Rook brings File, Block and Object storage systems into the Kubernetes cluster, running them seamlessly alongside other applications and services that are consuming the storage. By doing so, the cloud-native cluster becomes self-sufficient and portable across public cloud and on-premise deployments. The project has been developed to enable organizations to modernize their data centers with dynamic application orchestration for distributed storage systems running in on-premise and public cloud environments.

“Storage is one of the most important components of cloud native computing, yet persistent storage systems typically run outside the cloud native environments today,” said Chris Aniszczyk, COO of Cloud Native Computing Foundation. “Rook was one of the early adopters of the Kubernetes operator pattern and we’re excited to bring in Rook as an inception level project to advance the state of cloud native storage.”

Instead of building an entirely new storage system which requires many years to mature, Rook focuses on turning existing battle-tested storage systems like Ceph into a set of cloud-native services that run seamlessly on-top of Kubernetes. Rook integrates deeply into Kubernetes providing a seamless experience for security, policies, quotas, lifecycle management, and resource management.

In this Software Engineering Daily podcast, Bassam Tabbara, CEO of Upbound and creator of Rook, said: “Rook is essentially using the operator pattern to extend Kubernetes to support storage systems. We’ve added a concept of a storage cluster, a storage pool, an object store and a file system. Those are all new abstractions that we’ve used to extend Kubernetes”

An alpha version of Rook (release 0.6) is available now, followed by a beta and production ready versions in the first half of 2018.

Main features:

  • Software-defined storage running on commodity hardware
  • File, block and object storage presentations integrated with Ceph
  • Hyper-scale or hyper-converged storage options
  • Elastic storage that can easily scale up or down
  • Zero-touch management
  • Integrated data protection with snapshot, cloning and versioning
  • Deployable on Kubernetes.

The latest release of Kubernetes 1.9 introduced a CSI alpha implementation that makes installing new volume plugins as easy as deploying a pod, and enables third-party storage providers to develop their solutions without adding to the core Kubernetes codebase. Rook will expose storage through CSI to Kubernetes.

“It’s a natural fit to run a storage cluster on Kubernetes. It makes perfect sense to bring it into the fold and keep the unified management interface,” said Dan Kerns, Senior Director at Quantum, the initial sponsor of the Rook project. “With Rook, we wanted to create a software-defined storage cluster that could run really well in modern cloud-native environments, and the storage cluster becomes even more resilient with an orchestrator like Kubernetes.”

Community support for Rook is growing rapidly as companies and users deploy Rook in their cloud-native environments (on-premise and public cloud). Companies and organizations like HBO, UCSD Nautilus Project, Norwegian Welfare, Verne Global, FlexShopper, and Acaleph have implemented Rook as part of their storage platforms.

Notable Milestones:

  • 47 contributors
  • 1,935 GitHub stars
  • 13 releases
  • 1,463 commits
  • 1.25M+ container downloads

“We used Rook underneath our Prometheus servers at HBO, running on Kubernetes and deployed on AWS,” said Illya Chekrygin, former senior staff engineer at HBO and founding member of Upbound. “Rook made a significant improvement on the Prometheus pod restart time, virtually eliminating downtime and metrics scrape gaps. We are looking forward to Rook being in a production ready state.”

As a CNCF hosted project, Rook will be part of a neutral foundation aligned with technical interests, receive help with project governance and be provided marketing support to reach a wider audience.

“Operating storage in cloud-native environments is a significantly more difficult task than stateless containers,” said Benjamin Hindman, co-founder of Mesosphere and CNCF TOC representative and project sponsor. “We’re thrilled to have Rook as the first CNCF inception project that begins to address the difficult problem of storage orchestration.”

For more read the Rook blog, Quantum’s recent announcement on the momentum of the project, Upbound’s blog, and listen to The New Stack’s Makers Podcast or Software Engineering Daily featuring Bassam Tabbara discussing Rook and Storage on Kubernetes.