Loading…
Attending this event?
Seattle, WA
December 10–13, 2018
Click Here for More Information & Registration
View Venue Map
View analytic
Thursday, December 13 • 1:45pm - 2:20pm
Why Are We Copying and Pasting So Much? - Solly Ross & Philip Wittrock, Google

Sign up or log in to save this to your schedule and see who's attending!

Log in to leave feedback.
If you’ve contributed to the one of the Kubernetes controllers or built a custom controller (such as an operator), you’ve probably had to copy a large amount of boilerplate code. Other bits of the controllers may look similar, but have small variations, making it difficult to separate what is bespoke and what is common logic.

The copy/paste approach makes code harder to refactor, understand, and debug. Additionally, neither bug fixes nor improvements to the original are not propagated to the copies.

So what can we about it? Enter controller-runtime, a new foundation library for the next generation of controllers which replaces the boilerplate code with a few function calls. In this session, we’ll look at common controller patterns across both the Kubernetes codebase broader ecosystem, identifying the common elements, simplifying them with the utilities in controller-runtime.

Speakers
avatar for Solly Ross

Solly Ross

Software Engineer, Google
Solly Ross is the SIG lead for SIG Autoscaling, and works on Kubernetes with a focus on custom controller tooling, autoscaling, and metrics. When not dabbling in other parts of the Kubernetes code base, Solly enjoys a wide range of programming topics, and can be found most places... Read More →
avatar for Phillip Wittrock

Phillip Wittrock

Engineering Manager, Google
Phillip Wittrock is Senior Software Engineer at Google, Kubernetes SIG CLI Lead, and a member of the Kubernetes Steering Committee. Phillip’s hobbies include debating how kubectl is pronounced, talking about Kubernetes at social events, and appreciating code as art.



Thursday December 13, 2018 1:45pm - 2:20pm
Tahoma 3/4 @ TCC The Conference Center (TCC) - Separate from WSCC building