Cloud Foundry Advisory Board Meeting, June 2019: Distributing Sidecars

by Carlo GutierrezJune 20, 2019
Using buildpacks removes the burden of responsibility from application developers to implement sidecars.

The Cloud Foundry Community Advisory Board (CAB) meeting for June 2019 featured a community project related to distributing sidecars with buildpacks. The call, which was moderated by Dr. Max of IBM, also included updates from members of the development teams. At the end of the call, Swarna Podila and Chip Childers provided some updates from the Cloud Foundry Foundation.

 

Distributing sidecars with buildpacks

During last month’s CAB call, the concept of sidecars was introduced by Scott Sisil of Pivotal. He demonstrated how to deploy a Ruby app that talks to a separate Golang binary run as a sidecar process. Scott based his presentation on the sidecar tutorial posted by Tim Downey of Pivotal.

This time, Dr. Nic Williams of Stark & Wayne pushed the idea further by using buildpacks to distribute sidecars.

Dr. Nic Williams

“About a month ago, the CAB call talked about sidecars. I was super excited about that. I did Tim’s walkthrough, made that work, and the first thing that came out of my mind was why would I want to push this without using a buildpack?” —Dr. Nic, Stark & Wayne

According to Dr. Nic, implementing sidecars through buildpacks can address the separation of concerns across organizations, vendors, and developers. He emphasized that application developers shouldn’t worry about uploading the config-server necessary for sidecars.

The etcd proxy sidecar buildpack manifest (Image credit)

During the call, Dr. Nic demonstrated how to create an etcd proxy sidecar buildpack. His tutorial can be found in this GitHub repo.

Sidecars’ GitHub repo

 

Runtime PMC

Eric Malm

Eric Malm of Pivotal provided the following updates:

  • cf-deployment v9.3.0 was released and includes fixes to component metrics.
  • CLI v6.45.0 was released and has better support for client credentials with cf oauth-token.
  • The CAPI team is working on supporting more features for sidecars, such as buildpack integration and more independent resource limits.
  • The Loggregator team is improving agent-based syslog drains.
  • The Eirini team is making improvements to support reliability of route registrations.
  • Bbl v8 was released, moving back to elastic load balancers instead of application ones.

Runtime PMC’s GitHub repo

 

Kubernetes Deep Dive SV

BOSH

Mukesh Gadiya

Mukesh Gadiya of Pivotal delivered a couple of updates:

  • The BOSH v1 manifest support was removed.
  • The BOSH team is working to improve the behavior of bosh start, bosh stop, and bosh recreate, following feedback that they behaved in unexpected ways.

BOSH’s GitHub repo

 

CF Extensions

Dr. Max

Michael Maximilien (aka Dr. Max) of IBM noted the following developments:

  • Cloud-Native Buildpacks graduated from incubation and are now available at Buildpacks.io.
  • Stratos
    • The Stratos team is requesting graduation.
    • Support for Kubernetes is being integrated.
  • Abacus is moving to the attic.

CF Extension’s GitHub repo

 

Foundation updates

Swarna Podila

Swarna Podila posted two new updates from the Cloud Foundry Foundation. First, Abby Kearns will be participating in a series of ask-me-anything (AMA) calls. Interested CFF members should get in contact with the foundation’s digital marketing manager, Brie Rogers.

Second, the foundation is looking for contributors to the Cloud Foundry YouTube channel. Anyone interested in becoming a contributor can check out this publishing guide.

Chip Childers

Chip Childers noted that the Contributor Summit on September 10 is tentatively scheduled for 9 a.m. to 3 p.m. He also reminded callers that the schedule for the next Cloud Foundry Summit in Europe goes live on June 20.

 

The next CAB call is scheduled for Wednesday, July 17. The call will start at 8 a.m. Pacific Time. Anyone interested can join the Cloud Foundry’s CAB Slack channel.

 

Want details? Watch the video!

Get an ultimate architect's guide to understand what you need for a successful Cloud Foundry implementation
  •  
  • 11
  •