Cloud Native Computing Foundation KubeCon + CloudNativeCon Europe 2020 - Virtual, 4 Sep 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Sponsored Keynote: The Kubernetes Effect - Igniting Transformation in Your Team - Briana Frank

Description

Don’t miss out! Join us at our upcoming events: EnvoyCon Virtual on October 15 and KubeCon + CloudNativeCon North America 2020 Virtual from November 17-20. Learn more at https://kubecon.io. The conferences feature presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.

Sponsored Keynote: The Kubernetes Effect - Igniting Transformation in Your Team - Briana Frank, Director of Product, IBM Cloud

Kubernetes and Cloud Native architecture has begun to ignite transformation within companies in every industry. Growing from that first container project, team are starting to change how they build, work, collaborate and invent. Briana Frank will share how Kubernetes is the catalyst for this enterprise transformation and how to maximize the impact for your organization.

https://sched.co/Zh36

A

Hi, I'm brianna frank and I'm so excited to be here at kubecon, even though it's virtual and today, I'm going to talk about the kubernetes effect igniting transformation in your team, and so when we talk about transformation, really, the goal of any transformation is to move faster and when we're adopting cloud native uh capabilities and and tactics.

A

Of course, we want to have resiliency and scale and availability, but really it's about pushing as much code as possible every single day, and you know in ibm cloud we're pushing thousands of updates a day to our production cloud and what's interesting, is many of our clients ask as a 100 old tech company? How did you transform to this level of velocity and what are the ways that our organizations can? You know ignite that transformation, and so I I give a couple of examples.

A

I'm sure I don't have it all figured out, but a couple of things that I think that we found that that have really worked. You know one start with a new project and whenever you start with something new, it allows you to reevaluate everything that you're doing chances. Are your teams are have inherited legacy software and systems and processes and they're? You know by starting with something new.

A

You can reevaluate everything that you're doing you know maybe you're improving some things and leaving some an additional processes out, but it gives you a fresh start and the other thing I recommend is a design thinking workshop and you know we're big we're big in design thinking here at ibm.

A

But what design thinking is about is to take two or three days, and I know that sounds like a luxury but take that time to bring all of your stakeholders into one room and hash out what your mvp is going to look like, and if you have a really strong design facilitator, they will work.

A

They will work with you to walk you through some exercises that allows you to exit that workshop with quantifiable hills and when you leave, everyone is very clear on what that mvp is and what they they need to do next to reach that mvp. So there's no confusion and you could just move very quickly.

A

The next thing I recommend is starting that new project on kubernetes and kubernetes is a catalyst for transformation, because um kuberes manages infrastructure in such a consistent way and allows dev and operations to um operate very consistently and it unburdens the team. So the teams aren't having to worry about resiliency and scale so that paves the way for a culture of automation and automation and automation. Culture is, is very addicting and it catches on very quickly, and you know maybe it starts out with something very simple.

A

Perhaps you start answering questions instead of typing them out every time you answer with a doc link, and that becomes a little bit addicting, because you see how much time it saves, and so then it starts to transform into any time.

A

You start to get a repeat question: instead of answering it, you open a github issue and your product or the documentation, begins to change because it's just more efficient and that kind of culture starts to really um permeate in um you know in when you're leveraging a technology like kubernetes, and so one of the examples that we used early on um was chat, ops and chat.

A

Apps was really born out of wanting the ability to operate cube, but still, but using the tool that we use or utilize to collaborate with others, and so we use slack to collaborate with our team, but we were having to exit slack to handle a lot of our operations, and so we have a lot of fun with chat apps. Each of our chat, bots has its own persona and a specific job.

A

In this particular case, we use sir topham hatt and sir topham hatt has a specific job, of course, inspired by thomas the tank engine, but search album hat handles all of our automated gate. Approvals um from for our pipeline from dev all the way to production, and we have other chat bots that help us with things like recommending, run books or giving us additional information about a specific ip address, and what's neat is as we're conversing with our peers, the chat bots, um you know in ads.

A

It add context to those conversations, and sometimes the chat, bots even talk to each other.

A

So another example of how we're using automation is razzy, and so razzie.io is an open source project that we built out of necessity and when you're running tens of thousands of clusters in production there, you need to have an ability to deploy and automate those, and so we needed an ability to view and view all of those deployments all over the world and what data centers and we needed to be able to see what clusters needed to be updated.

A

And so we we used razzie.io as a way to achieve that and because we're able to operate in a consistent way. We were able to keep our small sre team from um that. We started with when we had zero clusters all the way to 24 000 clusters, which is what we're running today, and none of that would be possible without um being able to build on the foundation of kubernetes and because we're managing resources in a consistent way. Kubernetes enables this automation and therefore this transformation that allows us to go so much faster.

A

So that's how we're using kubernetes to ignite transformation in our team. I would love to hear about how you're using kube to ignite transformation in your team, and you know, find me on twitter, I'm frankly brianna, but also you know if you want to know more about you know, if you want to know more about design, thinking or chat, ops or razzie.io, I have a blog um ibm.biz transformed where I go into a lot more detail and have some resources there. Thank you so much thanks for having me.