Cloud Native Computing Foundation KubeCon + CloudNativeCon Europe 2021, 14 May 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Sponsored Keynote: Smoothing the onramp to Kubernetes with Knative - Brenda Chan, Director

Description

Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.

Sponsored Keynote: Smoothing the onramp to Kubernetes with Knative - Brenda Chan, Director of Engineering, VMware Tanzu Developer Experience, VMware

A

Hi everyone I'm here today to talk about spooning, the on-ramp to kubernetes, with k-native.

A

So just a quick introduction for everyone here. My name is brenda chan, I'm located in toronto, canada. uh My current role at vmware is the engineering director for vmware tons of developer experience.

A

However, within the k-native community, I've been on the steering committee since the bootstrap phase in 2019.

A

During my time on, steering we've worked towards a completely community elected technical oversight committee or toc in steering committee in october 2020, we formed the trademark committee and one really neat thing: we're focusing on right now is actually defining k-native conformance and working towards a set of conformance test suites for when we plan to 1.0 this year.

A

So kubernetes is awesome. I probably don't need to say more than that, since we are at kubecon. After all,.

A

But really kubernetes has allowed us to normalize our infrastructure abstractions.

A

We have a thriving ecosystem in large community. Thank you for all of those who are actually here today and honestly. Kubernetes extensibility has proven to be extremely valuable and powerful.

A

The thing is, is that kubernetes can actually be pretty hard in the cncf survey report in 2020 to the question. What are your challenges in using in deploying containers?

A

The main challenge that the respondents actually replied with was that it was complex and I'd really like to spend some time today to explore that, because it really doesn't need to be that hard. So let's actually try this out. Let's run a stateless web server.

A

So you have me there on the left, the the kubernetes engineer with 20 years of experience.

A

So first you'll want to create a deployment object. You open up them. You create some yaml, make sure your indentation looks good great youtube, cut I'll, apply the deployment so far, so good, all right! So now you create a kubernetes service. uh You specify the port, ensure you're targeting the right app and again you could apply that.

A

So now you need to make sure you can route traffic to your service. So let's create an ingress, uh ensure you have the right service, name and port. You could all apply that awesome.

A

And you're happy- and this is awesome because it just works, but let's do this again, you may need to update something. Maybe the image change the port changed. Who knows.

A

So again you go through the same thing. You update your deployment, animal keep, it will apply. You may update the service. Coupe codon apply, update the ingress. Keep it'll apply, you're pretty used to this by now- and this might be you not the worst but gosh, the maintenance of the sprawling yml files are really annoying and then before you know it we're updating, yaml or cube kettle applying, and at this point you probably have an intimate understanding of kubernetes pods.

A

You know everything about labels and horizontal pod, auto scaling, and at this point you might have checked in your yaml to share with your team you're doing code reviews for all of this yaml, and at this point you really take a step back and wonder. Am I just a yaml engineer the thing is it really doesn't have to be this way with k-native serving we've simplified? A lot of that.

A

So you as a person, writing and deploying the app can focus on what matters to you with k-native serving you get auto scaling deployment, ingress automatic, dns all created and managed for you.

A

You can easily handle traffic splitting and, after all, that's what you probably do care about with k-native eventing. It allows you to move towards an event-driven architecture and decouple event: delivery from your application code by using k-native event, things source broker and trigger and standardizing your cloud events application. You simplify that process. For you.

A

The point I really want to get across here is that it really doesn't have to be that hard. You don't need to have this exploding brain feeling, modifying yaml learning all of these concepts code reviewing yaml when it could be this focus on what matters to you.

A

If you'd like to learn more, feel free to visit the k native site, join the slack channel or follow the twitter account, everyone in the community is extremely welcoming, and everyone is welcome to join. I'm also happy to chat more. If you have any questions, feel free to reach out to me on twitter, and that's it thanks. Everyone.