 Good morning everybody. So hi, I'm Chen and I'm an engineering director at Google and I'm leading the development of some of the open source Technologies you already heard about kubernetes and also Istio and also responsible for some of our products like Google kubernetes engine I'm really excited to be here. This is already my favorite event of the year by choosing this amazing location and the weather and And I'm really looking forward to meet many of you and speak about the thing that we are all very passionate about Today is a very very special day for the kubernetes community and also for the cloud native compute foundation Today we announced that kubernetes is being graduation and graduating from incubation as the first project out of cncf Graduation is a signal of maturity of a project From the early days when the Google engineering team started to work on kubernetes They collaborated with people from companies like red hat and coro s and and also customers like box and everybody worked together and Bringing different perspective ideas skills experience and really building this technology With the goal to solve right speaking to what James before really solve problems for users wherever they are And what was amazing that not only we got many contribution But because of the nature of the community and and the openness We were also able to build a really rich ecosystem around that filling the gap and where it's needed So some metrics of how success looks like I just added this morning with the github stars And probably we need to do it again after this after today and Luckily users are recognizing it the success of kubernetes the stability of this project And this is really if you will look on the cncf of what graduation means it means a Governance model it talks about more than one contributor, but on top of everything it's about users using it in production and This is definitely and not the entire list and new users using kubernetes every day And what I love about it and it's not shown here that all of us contributing to kubernetes are also using kubernetes as an example for Google Itself we are building Google kubernetes engine using upstream kubernetes We have products like cloud the mail running on GKE internally And that's what makes it better because we all benefit from that technology and Benefits include of course agility That's what drives everything. This is what drives adoption Today and agility is measured with how quickly you can deploy to production How quickly you can set up environments with the complexity of multiple workloads and infrastructure Leveraging cloud native technologies. This is something that's really kubernetes is putting a goal for and definitely cncf Making it easy to adopt those two connect those technology without the need to modernize everything already And the pace of adoption also keeps us on the edge as a community really trying to innovate and meet the demand of our customers So, how did we get here? Right? This is why we're here This is the intention of this entire week to talk about how can you build a successful project like kubernetes? So when Dan sent me an email to like hey, can can you come and speak in the open source leadership summon? Like yes, what do you want me to talk about and he said like if you can just tell everybody how you made it work? And that will be great like Well, I wish I could The truth is that the world is changing very fast Okay, and the days kubernetes was started four years ago So maybe for some of you it seemed like it was overnight It wasn't overnight it has been four years of working and adopting to the pace of technology and the industry So there is no playbook But definitely there are some really great memories and like every graduation. I want to walk you some to some of them and talk about some of the learnings So, how do you balance between open source and non open source investment? If only I had a dollar every time someone asked me that I would probably not be standing here And I would be vacationing maybe in Hawaii or something somewhere else and This comes up from everybody from customers from engineers that want to join the team from product management executives There is real tension because it's really hard to rationalize So you are taking all this IP and making it available to everybody And I'm sure all of you are familiar with this challenge In mind in my mind one of the choices that we did in Google within my team Is the side that open source is part of the strategy It's not a side gig. It's not something we just take outside It was part of the strategy from the beginning right if you will read the origin story of kubernetes It was about getting at option. It was about getting feedback. It was about building an ecosystem We have made a decision that kubernetes upstream is the core technology that we are building our products on So if you are investing in kubernetes, you're literally also investing in GKE at the same time and What I found is that if you explain? Developers in particular that our users are benefiting from open source Okay, they are benefiting from the fact that kubernetes runs everywhere. It helps them solve problem that helps solve their tension, okay, because we are not doing it just for the sake of the tech or just To make something cool open source. We are really helping our users and this is a journey right and that journey to moving to cloud will be a long one and For many of the customers there will always be that hybrid environment Another point I want to talk specifically about for all the engineering managers here One thing that was important for me is also to build one team There is no open source team and a product team. There is one team. There is one strategy one backlog one team And I believe that throughout the years GKE has benefited so benefited so much with working with the kubernetes users But also the other way around I know that kubernetes the project benefited from the experience that we have gathered with our GKE customers So This is my first community meeting It was Almost two years ago. So community meeting in kubernetes every Thursday at 10 a.m Pacific time and we are meeting. We're inviting everybody from the community Everything is recorded Available on YouTube, of course And and we talk we talk about things we talked about the project ecosystem demos And you can imagine so this is like probably my second month in Google and It can be very intimidating Okay, going up and speaking about something and this was you know, I can still remember you at that I'm able speaking for the first time and I had the O'Brien cheering for me and saying gonna be okay And this was in the in the middle of 1.3 Kubernetes release and in this particular example, we were debating whether to reduce the amount of development in favor of stabilization and the reason we did it is because At least I in particular we wanted to increase our release cadence and make it stable And get to the point that if you miss the train You can always catch the next one and really build that release train and today kubernetes is releasing every three months or 100 days and Really can improve than that And I think from this example there are two things that everybody can learn on engineering and management practices We saw some questions before how do you manage open source? How do you prioritize? I really believe That there is actually shouldn't be any difference From the way you manage an open source product and an engineering team to the way you and manage your own Commercial product or your own product itself those engineering practices Agile release cadence defining the quality bar testing documentation Stabilization period marketing all of those things They are all needed for an open source project if you wanted to be successful And this is definitely something that we had in our mind doing kubernetes and it feels like one engineering team the other point Yes, is transparency while it might be intimidating to be recorded all the time and everything is Visible to everybody But it also empowers people to speak and join the conversation Because you can go and look on what was before and what decisions were made and what alternatives were considered so for me while it was a Bit hard I also felt in that it was encouraging To have new people join the conversation and really it helps to build trust and trust Like any other team whether if it's engineering product marketing or in any other industry trust is key To build a team that works together This was another exciting moment So I'm pretty sure that I don't need to introduce Pokemon girl. So it was a around July 2016 and the entire world was working like that and All the kids were working like that. How many here played Pokemon go? So I didn't because it was it is running on GKE and I was afraid to add more load, but other than that Now I'm like telling the team like don't play don't play And but this was exciting times. Okay, so the entire world There was this crazy excitement about Pokemon go and we couldn't tell anyone that it runs on GKE that it runs on kubernetes And you can see here This is one of the graph that they published about how the traffic that they had was 50 times what they expected 50 times you can see the graph and and that could have become a successful disaster but instead Because of cloud native technologies because of technologies like kubernetes, they were able to scale the cluster as the demand grew without Interrupting the way they're still the users And in my mind, this is Something that is also very important in any open source project in any open source product focus on the user What problems are you solving? What is the pain that you need to solve? And something that I love about the kubernetes community is that we are very pragmatic We're not trying to look for the perfect solution We're trying to solve problems for users and make sure that it's practical and they can use it And one concrete example would be when kubernetes 1.0 Was announced it supported 100 node clusters. This is not a Google scale cluster, right? It's only 100 nodes but for that time that was the right size for people that wants to kick the tire and Try that technology if we would have tried to do Google scale like kubernetes We would probably be blocked forever But this time went by and we got more things in we improved on that and today We have 5,000 node a cluster and to be honest with you that 100 node Cluster is still a good fit for many of the users of kubernetes today And that's what makes it relevant for many customers and users and celebrate success The success of Pokemon Go was not just my team or just Google's Everybody that worked on kubernetes to build that Contributed to Pokemon Go and that was a celebration for the entire community just to show some of that success But not everything in open source is rainbow and butterfly. I wish but no and So when we started to talk about kubernetes and talk about the culture we talked about the values and transparency and respect And it was easy when the community was 600 people But then it became 1200 and then 1500 and then 2000 and then 3000 and From three companies contributing to 10 to 20 and more and it becomes more complex And in particular like again like any other Organization when you scale you need to react and you need to think about what do you change in order to meet the new skill? One specific problem we had was with processes when everybody knew everybody it was easy to make decisions So we had this idea was hey, we we have those six We have special interest groups they meet and they make decisions and it's all great But then we have some new people that are joining and they don't know who's that person Who is the seed lead and why that person get to make the decision or I am and now if I want to contribute How can I engage and how can I improve my leadership and become a leader of this community? And this is again another signal of the graduation today is working on about on our governance model in October 2017 we elected our steering committee and the steering committee is not about making all the decisions It's about ensuring there is a way to make decision. There is a way to escalate. There is a way to challenge and Just the other day Sarah Navadny published the values of The Kubernetes community before we all knew the values, but this is not good enough anymore We have to document it so people that wants to join our community. No, what are the things that we work by? Scaling is not just about processes. You also need to scale the technology. It was around a Also the end of 2016 when we felt that we there is a velocity Heat it was harder to innovate you would change something here and something broke there You needed there was how to get reviewers for everything and really nobody was able to Understand the entire complexity of the system. So if you look on this slide Brian Grant created this diagram to capture the scope of Kubernetes the complexity of it It's almost the same of an entire cloud provider So about that time what we decided to do and I wish by the way that we have done more at the beginning of it It's really investing in what are the extension points to Kubernetes and anyone that is now thinking about a new open-source project Talking about interoperability and like you mentioned before it is critical So while it might seem for people that it's not that important and we can wait with that extension points are critical and are key for Sustainable success. So as you're looking on those levels are over a dozen extension points today and Naming few our webhooks CRI container runtime interface a client libraries cloud providers and what's amazing about it that it helps us to innovate and build new things for example open service broker is still and There are some really awesome Silverness framework that are already using those extension and that allows them to innovate even faster conformance just a three months ago we announced the certification conformance program for Kubernetes Because having those extension points is not enough We wanted to make sure that we reduce the risk of fragmentation Okay, we are planning for success. So how can customers partners make sure that this is upstream Kubernetes that the entire API interface is usable and available for you to use and And that was amazing Because this was a community effort and that really represents one of the values of the Kubernetes community, which is community before product Community before company because for a single company that might not be the most important thing But as a community we want to make sure that Kubernetes will stay for a very long time And we'll keep hearing about it in many years to come So right now. I think there are about 20 something today. There are over 50 Companies that are compliant with the conformance program. So what can you learn about everything that we have done with Kubernetes? The first thing is intentional leadership You have to plan to plan nothing happens Just by doing stuff or not being thoughtful about what is our goal What's your open-source strategy? What is your expectation from the community? What is the release process? How do you ensure quality? invest time and think about it and make sure That your actions are aligned with your intentions and if there are not change your actions We all make mistakes and we make experiments, but definitely Be intentional about everything. What are the culture values that you want to have in the community? Sustainable success what got us here won't get us there Plan for success plan for the future. What needs to be changed? in order to be a successful to update a To react to the amount of adoption that took us by surprise But we adopted and we changed and we were open-minded about what needs to change and how we move forward And and I know for sure that everything we are planning for the next year Will again have to change assuming will be successful in two years and three years And that's how product is how software is how technology is everything changes also around us The last point is diversity. I didn't talk about it Before within my slide being a female leader in tech. It's not easy to talk about diversity But I think that as leaders we all must talk about diversity So my ask from all of you is to be intentional about that build communities with openness that are welcoming people so my Personal belief that every project every team every product will benefit from a diverse team The unique thing about open source that it is in the reach of everybody No matter your age where which country you live in or your gender you can all be part of something amazing It's really a platform of opportunities for everybody and I think for all of us It's really an opportunity to make this a better world. So thank you