Monthly Newsletter – May 2017

CNI Joins The Family!

Container-based applications are rapidly moving into production. Just as Kubernetes allows enterprise developers to run containers en masse across thousands of machines, containers at scale also need to be networked.

The CNI project contains three main components: specification, plugins, and library. CNI specification and libraries exist to write plugins to configure network interfaces in Linux containers. The plugins support the addition and removal of container network interfaces to and from networks. Defined by a JSON schema, its templated code makes it straight-forward to create a CNI plugin for an existing container networking project or a good framework for creating a new container networking project from scratch. See the current list of 3rd party plugins and container runtimes in the linked blog post.

Developing Cloud Native Applications

Software engineering and developer communities are driving the market for cloud consumption and leading each industry into a new era of software-defined disruption. “There are no longer questions about elastic and flexible agile development as the way to innovate and reduce time to market for businesses,” says Ken Owens, CTO of Cloud Native Platforms at Cisco and CNCF Technical Oversight Committee representative. He continues discussing how open source software plays a key role in the digital transformation to cloud native and understanding how your business strategy needs to address this next disruption in software development is crucial to the success of your business.

The existing patterns are software automation (infrastructure and systems), API integrations, and services oriented architectures. The new cloud native pattern consists of microservices architecture, containerized services, and distributed management and orchestration. The journey towards cloud native has started and many organizations are already testing with this new pattern.

Release Updates

Linkerd 1.0: Last month, we looked at Co-founder, William Morgan’s post describing why we need a service mesh. William, Oliver, and team have since hit a meaningful milestone with this 1.0 release. They’ve added the capabilities of per-service configuration and per-client configuration to their most stable release yet.
Read More »

CoreDNS-007: ServeDNS is extended to take a context. This allows (for instance) tracing to start at an earlier entrypoint. Additionally gRPC and TLS are made first-class citizens, and Zipkin tracing can be enabled for all middleware.
Read More »

Fluentd v0.14.16: New features allows for null byte in double-quoted string. Bug fixes include out_forward: call proper method for each connection type, and in_monitor_agent: check variable buffer is a Buffer instance.
Read More »

User Profile: ShuttleCloud Explains Why Prometheus Helps Small Startups

ShuttleCloud is a small startup specialized in email and contacts migrations. For example, Gmail alone has imported data for 3 million users with their API and they process hundreds of terabytes every month.

Before transitioning to Prometheus, ShuttleCloud had near-zero monitoring. Now they have all of their infrastructure monitored with the necessary metrics and alerts. They chose Prometheus due to the flexible, as-you-go metric configuration, label usage for abstraction, and its simple install. Find out which additional capabilities surprised them in the full article link below.

To hear more stories about Prometheus’ production use, participate in technical sessions on the monitoring tool, and learn how it integrates with Kubernetes and other open source technologies, attend PromCon 2017, August 17-18 at Google Munich. Speaking submissions close May 31st.

Calling Cloud Native End Users

Does your company use cloud native technologies internally (like Ticketmaster and Box) but not offer cloud native services to your customers (like IBM and Google do)? Then we want you to join the CNCF End User Board! You’ll get to meet monthly with other end users to share (positive and negative) experiences, hear from current and prospective CNCF projects, and appoint one member to the crucial Technical Oversight Committee. The investment is just $4,500 per year and includes 5 tickets to CloudNativeCon/KubeCon, or only $1,700 and 2 tickets for startups.