Why and How We Launched a Kubernetes SIG at Salesforce - The New Stack

thenewstack.io
7 min read
standard
We at Salesforce recently launched an internal Kubernetes SIG with representatives from each of the different groups using Kubernetes.
Laura Lindeman Laura manages blog, social media, and conference content for engineering at Salesforce as part of the Technology, People, Innovation & Learning team. She calls Atlanta, Georgia, her home base.

With the work we're doing at Salesforce to re-imagine our architecture for deployment on the public cloud, we have folks working on Kubernetes across many different teams and product lines. While we're organized in a traditional "org chart" structure, with workers mapping to management chains that tackle certain parts of our problem space (often aligned to products), Kubernetes concerns affect everyone horizontally across teams. We needed a way to provide a consistent body of expertise for enterprise Kubernetes use cases and requirements, all tied to an architecturally consistent vision. The Special Interest Group (SIG) model seemed like a great foundation to build on, so we recently launched an internal Kubernetes SIG with representatives from each of the different groups using Kubernetes.

Many projects in the Kubernetes community are managed by Special Interest Groups (SIGs). These groups make it much easier to manage what has become such a large project. A key point, according to the Kubernetes contributor guide, is that "the developers within each SIG have autonomy and ownership over that SIG's part of Kubernetes." But equally important, since Kubernetes is an open source project, is that "anybody is…
Laura Lindeman, Eran Vanounou, Jessica Kerr
Read full article