<?xml version='1.0' encoding='utf-8' ?>
<!-- Made with love by pretalx v2024.3.1. -->
<schedule>
    <generator name="pretalx" version="2024.3.1" />
    <version>0.4</version>
    <conference>
        <title>Cloud Native Rejekts NA (Los Angeles + Hybrid) 2021</title>
        <acronym>cloud-native-rejekts-na-los-angeles-hybrid-2021</acronym>
        <start>2021-10-09</start>
        <end>2021-10-09</end>
        <days>1</days>
        <timeslot_duration>00:05</timeslot_duration>
        <base_url>https://cfp.cloud-native.rejekts.io</base_url>
        
        <time_zone_name>US/Pacific</time_zone_name>
        
        
    </conference>
    <day index='1' date='2021-10-09' start='2021-10-09T04:00:00-07:00' end='2021-10-10T03:59:00-07:00'>
        <room name='Main stage' guid='05a796e8-37e9-5eb1-996b-238e4a249071'>
            <event guid='7b05661d-18b4-55a5-8ccb-ec569a0471b4' id='313'>
                <room>Main stage</room>
                <title>depstat: Analyzing a Go Project&#8217;s Dependencies</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2021-10-09T09:35:00-07:00</date>
                <start>09:35</start>
                <duration>00:30</duration>
                <abstract>This talk will be about the importance of tracking dependencies in a large project like Kubernetes and about &quot;depstat&quot; which is a tool created to track dependency updates to the Kubernetes codebase. The Kubernetes repository receives many pull requests each day many of which bring dependency changes with them. Most of the time, the maintainers manually have to spot these changes, determine their effects on the overall dependency tree, and then ping the pull request authors to take action. To avoid this and help better track the dependency updates, depstat was created. depstat is an upstream project which analyzes dependencies for go modules enabled projects. It currently runs as part of a prow job in the Kubernetes code repository and provides four crucial dependency-related metrics. &quot;depstat&quot; also provides the ability to analyze dependencies visually by creating a graph.</abstract>
                <slug>cloud-native-rejekts-na-los-angeles-hybrid-2021-313-depstat-analyzing-a-go-project-s-dependencies</slug>
                <track></track>
                
                <persons>
                    <person id='358'>Arsh Sharma</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/39G7NV/</url>
                <feedback_url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/39G7NV/feedback/</feedback_url>
            </event>
            <event guid='41aadd20-ed1c-5616-ada0-890ca3d42317' id='316'>
                <room>Main stage</room>
                <title>Bringing the power of eBPF tools to your Kubernetes web UI</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2021-10-09T10:15:00-07:00</date>
                <start>10:15</start>
                <duration>00:30</duration>
                <abstract>We built Inspektor Gadget to enable Kubernetes operators to get insights on their clusters, simplifying running bcc tools and using the power of eBPF to build more advanced gadgets. We designed Headlamp to help operators visualize and control their clusters, and we made it extensible so that users could tailor it to their needs. We are now combining them to get a lot more power out of both, by enabling use-cases that are powered by Inspektor Gadget and delivered in a way that is easy to use.</abstract>
                <slug>cloud-native-rejekts-na-los-angeles-hybrid-2021-316-bringing-the-power-of-ebpf-tools-to-your-kubernetes-web-ui</slug>
                <track></track>
                <logo>/media/cloud-native-rejekts-na-los-angeles-hybrid-2021/images/BZC9TQ/tram_night_headlight_hufe3_lSRlMJf.png</logo>
                <persons>
                    <person id='224'>Joaquim Rocha</person><person id='386'>Marga Manterola</person>
                </persons>
                <language>en</language>
                <description>This talk is for anyone who is looking for an easy way to use eBPF tools in their cluster, through a web UI that lowers the learning curve and improves the user experience.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/BZC9TQ/</url>
                <feedback_url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/BZC9TQ/feedback/</feedback_url>
            </event>
            <event guid='26e4a558-dc79-5a6a-a33e-9956d84b01b2' id='314'>
                <room>Main stage</room>
                <title>Hijack a Kubernetes Cluster - a Walkthrough</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2021-10-09T10:55:00-07:00</date>
                <start>10:55</start>
                <duration>00:30</duration>
                <abstract>Nico will show how to hijack a Kubernetes cluster based on common attack vectors. You&apos;ll also learn why it&apos;s important to implement zero-trust to prevent data leaks and malicious workloads from being executed on a hijacked cluster.
Furthermore, he will show you how to protect your cluster from being taken over by sharing useful insights, configurations, and toolsets.
This talk is not intended to be an in-depth security talk, but to provide you with best practices and also make you aware of certain attack vectors and how to prevent them.</abstract>
                <slug>cloud-native-rejekts-na-los-angeles-hybrid-2021-314-hijack-a-kubernetes-cluster-a-walkthrough</slug>
                <track></track>
                
                <persons>
                    <person id='359'>Nico Meisenzahl</person>
                </persons>
                <language>en</language>
                <description>Get started with Container &amp; Kubernetes Security!</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/YJDCPC/</url>
                <feedback_url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/YJDCPC/feedback/</feedback_url>
            </event>
            <event guid='d97b8447-88b8-54a0-a505-9983a57da272' id='312'>
                <room>Main stage</room>
                <title>There&#8217;s No Free Lunch, but Can I Have a Free Sandwich With Observability?</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2021-10-09T11:35:00-07:00</date>
                <start>11:35</start>
                <duration>00:30</duration>
                <abstract>This session is going to present a full cloud-native observability stack that can be used to get monitoring data from a non-orchestrated micro-services architecture oriented application.
The application will use HTTP and gRPC for communication, but will not include any code to aid with its monitoring. Then, to get as much data about the application as possible, a set of open source tools like Nginx Ingress Controller, Prometheus, Jaeger, Loki, Linkerd 2, and Grafana will be used. Attendees can see how much telemetry one can get using these tools: metrics, logs and even traces will be presented - all of that without changing a line of code in the application. Obviously, the end result won&#8217;t be as good as an app with orchestrated code - there&#8217;s no free lunch. But let&#8217;s see if one can get a sandwich on-the-house.</abstract>
                <slug>cloud-native-rejekts-na-los-angeles-hybrid-2021-312-there-s-no-free-lunch-but-can-i-have-a-free-sandwich-with-observability-</slug>
                <track></track>
                
                <persons>
                    <person id='357'>&#321;ukasz Pi&#261;tkowski</person>
                </persons>
                <language>en</language>
                <description>The main objective of this talk is to show attendees how far the observability ecosystem built around Kubernetes has taken us. I want to show a simple application, that except for typical old-style logging doesn&#8217;t use any modern observability-supporting tools. Still, by combining it with Open Source platform tools we have at our disposal, we can get a lot of observability for free.
The presentation will show how any app can be instrumented: how we can analyse logs using Loki, observe traces using Jaeger and how we can dig into metrics provided by Linkerd and Nginx Ingress Controller.
This talk is backed up by my blog series I did for our company blog: https://www.giantswarm.io/blog/part-7-the-observability-finale. It also has full source code available on GitHub: https://github.com/giantswarm/giantswarm-todo-app/.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/HGNJAE/</url>
                <feedback_url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/HGNJAE/feedback/</feedback_url>
            </event>
            <event guid='d37873fe-1e7a-5c2c-bdfa-e2334018eb20' id='350'>
                <room>Main stage</room>
                <title>Ray on Public-Cloud Kubernetes: experiments, lessons learned, and suggested best practices</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2021-10-09T12:15:00-07:00</date>
                <start>12:15</start>
                <duration>00:30</duration>
                <abstract>Ray is an increasingly popular distributed execution framework for scaling applications and leveraging state of the art machine learning libraries. With the availability of GPU compute shapes on public clouds, deploying Ray on the public cloud is an attractive option over deploying it on bespoke on-prem compute resources. This talk explores suitability of Kubernetes on public cloud as a deployment platform for Ray, shares experiments with Ray deployed on Nodeless Kubernetes, lessons learned, and suggested best practices.</abstract>
                <slug>cloud-native-rejekts-na-los-angeles-hybrid-2021-350-ray-on-public-cloud-kubernetes-experiments-lessons-learned-and-suggested-best-practices</slug>
                <track></track>
                
                <persons>
                    <person id='91'>Madhuri Yechuri</person><person id='384'>Chi Su</person><person id='387'>Anne Holler</person>
                </persons>
                <language>en</language>
                <description>Open Source project Ray provides a simple, universal API for building distributed applications which enables end users to parallelize single machine code, with little to zero code changes. One of Ray&#8217;s strengths is the ability to leverage multiple machines in the same program. Although Ray can be run on a single machine, the real power is using Ray on a cluster of machines. For this reason, Kubernetes is a well suited substrate for execution of distributed Ray programs. This talk details experiments running Ray on Kubernetes on public cloud, automating cloud-agnostic cluster compute using Nodeless Kubernetes, lessons learned, and suggests best practices.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/A8LK9W/</url>
                <feedback_url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/A8LK9W/feedback/</feedback_url>
            </event>
            <event guid='4875115e-8194-5a82-8919-ce4be81dba33' id='308'>
                <room>Main stage</room>
                <title>Avoid Spikes: Unexpected Kubernetes Behaviors</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2021-10-09T13:30:00-07:00</date>
                <start>13:30</start>
                <duration>00:30</duration>
                <abstract>We all know that Kubernetes is complex and provides an ever-increasing set of capabilities for managing your workloads, but the basics of it like how pods work, how you expose a service, and so on are pretty simple... or are they?  Even basic operations occasionally have sharp edges that can give you nasty papercuts deploying your apps because what you might intuitively assume to be the case, isn&apos;t how Kubernetes actually works.  Joe Thompson takes you through some of these &quot;you&apos;d think that, but...&quot; cases, details how Kubernetes &quot;thinks&quot; about them, and offers advice on how you can mitigate or change Kubernetes&apos; behavior so that those papercuts don&apos;t become grievous wounds in your workloads or the clusters running them.</abstract>
                <slug>cloud-native-rejekts-na-los-angeles-hybrid-2021-308-avoid-spikes-unexpected-kubernetes-behaviors</slug>
                <track></track>
                
                <persons>
                    <person id='85'>Joe Thompson</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/ABAFUU/</url>
                <feedback_url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/ABAFUU/feedback/</feedback_url>
            </event>
            <event guid='f1c9ffea-c6e3-50aa-8d50-7bfd6d280050' id='345'>
                <room>Main stage</room>
                <title>Growing the Community around CNCF Incubation project Emissary Ingress</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2021-10-09T14:10:00-07:00</date>
                <start>14:10</start>
                <duration>00:30</duration>
                <abstract>More than 4 years ago, the Ambassador Labs team recognized the power of Envoy Proxy and started building the Ambassador API gateway. Back then they thought of Ambassador as the human way to harness the power of Envoy Proxy, which was mostly built for machine configuration. Over the last four years that project has evolved to become what is now known as Emissary Ingress, the CNCF Incubation project, an accomplishment owed largely to the super community that has rallied around the project over the years. 

In this talk Cindy will discuss why community is so important, and explain why they wanted to double down on their community efforts by donating the project to the CNCF. She&#8217;ll share some of the lessons learned in growing the community from zero to thousands of active users and talk about the tactics they use to build an inclusive community that shares knowledge and fosters collaboration across all levels of experience.</abstract>
                <slug>cloud-native-rejekts-na-los-angeles-hybrid-2021-345-growing-the-community-around-cncf-incubation-project-emissary-ingress</slug>
                <track></track>
                
                <persons>
                    <person id='381'>Cindy Mullins</person>
                </persons>
                <language>en</language>
                <description>Building inclusive and active communities is the driving force of the CNCF ecosystem. With Emissary Ingress&#8217; recent acceptance into the Incubation tier of the CNCF, Ambassador Labs wants to share their learnings on community building to help other communities grow and flourish.

As the Emissary Ingress community manager Cindy will explain how they get to know their users, support them when just getting started, and assist them to overcome knowledge gaps or technical hurdles which might otherwise derail their progress.

Keeping up with all the technical questions posed by an active community can be challenging for community builders.  Cindy will share tips for distributing this work among team members efficiently and the benefits of doing this via cross-functional teams.

She&#8217;ll also outline their community recognition program and share how they encourage contributions that strengthen knowledge sharing and help make the experience of more seasoned developers accessible to new learners.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/U8VP9M/</url>
                <feedback_url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/U8VP9M/feedback/</feedback_url>
            </event>
            <event guid='aec4e715-0b84-5ba8-8dc6-a32fc4a99e01' id='309'>
                <room>Main stage</room>
                <title>Don&#8217;t Read the Manual: Automating Helm Provisioning with Terraform</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2021-10-09T14:50:00-07:00</date>
                <start>14:50</start>
                <duration>00:30</duration>
                <abstract>Helm is designed to take the guesswork (and a lot of the YAML) out of deploying a Kubernetes application. If you&#8217;ve ever needed to rapidly deploy a durable application, you&#8217;ve probably taken a long look at a Helm chart. And if you&#8217;re already using Helm, you&#8217;ve probably considered about how Infrastructure as Code (IaC) can simplify your workflow.
 
But how does Helm&#8217;s configuration interact with IaC state? What configuration is really authoritative&#8212;and with what scope? If you update an application that you Terraformed from a Helm chart, is your persistent data safe? And what about existing Helm-deployed applications&#8212;is it safe to import them into Terraform?
 
Clearly, Helm is incredibly powerful, but it&#8217;s also an abstraction, and no one has written the manual on how to integrate it with IaC. This talk will explain how Helm and Terraform work together under the hood, as well as exploring patterns to help Terraform practitioners safely engage with Helm charts and adopt Helm resources.</abstract>
                <slug>cloud-native-rejekts-na-los-angeles-hybrid-2021-309-don-t-read-the-manual-automating-helm-provisioning-with-terraform</slug>
                <track></track>
                
                <persons>
                    <person id='354'>Scott Reu</person>
                </persons>
                <language>en</language>
                <description>IaC has transformed the Kubernetes landscape, and Helm promises to further streamline application deployment. Even so, Helm&#8217;s role in the IaC ecosystem remains relatively obscure and sparsely documented; its potential remains out of reach for those who could benefit most from it.
 
There is a surprising lack of best practices for managing Helm deployments with IaC, and so teams that simply require durable, rapidly-deployed applications may be discouraged from exploring a Helm/IaC solution. This talk will seek to provide some foundational knowledge to remedy this.
 
In this talk, I will explain the models used by Terraform and Helm, and demystify their interaction. I will also examine some strategies for managing Helm with Terraform, and some patterns for engaging with Helm charts. I hope that this discussion will encourage IaC practitioners to embrace Helm (and vice versa), and that it will shed some light on the technology that makes Helm and IaC such a powerful combination.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/LZ8Z9A/</url>
                <feedback_url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/LZ8Z9A/feedback/</feedback_url>
            </event>
            <event guid='e6e08c98-a4df-5798-82dd-897a27d557b4' id='306'>
                <room>Main stage</room>
                <title>Say goodbye to PSP! Migrate your PSP rules to OPA with no hassle</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2021-10-09T15:30:00-07:00</date>
                <start>15:30</start>
                <duration>00:30</duration>
                <abstract>Pod Security Policies are cluster-wide resources that control security sensitive aspects of pod specification, defining a set of conditions that a pod must run with in order to be accepted into the system. 
Due to its limitations, recently the Kubernetes Auth Special Interest Group (AKA sig-auth) announced to deprecate the pod security policy (PSP) in Kubernetes next versions. This decision could leave many Kubernetes users at risk of being exposed to various exploits. Adversaries may utilise the lack of such policy to run privileged pods, create pods on host namespaces or networks and much more. One of the best alternatives for Kubernetes users to mitigate PSP deprecation through the built-in admission controller is utilising Open Policy Agent (OPA) rules. 

OPA is a CNCF Incubating project and supports enforcing policies in a variety of areas, including microservices, Kubernetes, CI/CD pipeline, service mesh and API gateways. Relying on a declarative policy language called Rego, security operators can concisely express policy-rules and implement them in your environment. Moving from PSP to OPA, users need an easy way to translate their policy or automatically generate new OPA rules based on the rules already deployed in the environment. With this need in mind, we integrated the existing project kube-psp-advisor, already capable of creating K8s Pod Security Policies (PSPs) from either a live environment or from a single .yaml file containing a pod specification, adding a new feature to automatically generate OPA Rules, scanning an existing security context from Kubernetes resources in live environments or directly from a .yaml file.

In this talk we go through the main limitation in PSP to explain how OPA is a better overall solution, capable of providing security controls to all the components in your Kubernetes environment. We show how the kube-policy-advisor tool works and how it&#8217;s possible to generate an OPA Rule from a live environment. We proceed then to enforce the rule using Kubernetes Admission Controller in the environment and see how OPA with the new rule in place works when we try to deploy a non compliant pod inside the existing environment.</abstract>
                <slug>cloud-native-rejekts-na-los-angeles-hybrid-2021-306-say-goodbye-to-psp-migrate-your-psp-rules-to-opa-with-no-hassle</slug>
                <track></track>
                
                <persons>
                    <person id='353'>Stefano Chierici</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/YQJ7R9/</url>
                <feedback_url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/YQJ7R9/feedback/</feedback_url>
            </event>
            <event guid='e3899057-eeb7-5f90-8714-2f42d19b1823' id='341'>
                <room>Main stage</room>
                <title>Troubleshooting Kubernetes CRDs is too damn hard</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2021-10-09T16:30:00-07:00</date>
                <start>16:30</start>
                <duration>00:30</duration>
                <abstract>When something to do with your CRDs breaks, how many kubectl commands do you need to understand what&#8217;s happened?

This talk argues that &#8220;how many kubectls?&#8221; is a key metric that codifies the usability of any set of CRDs, and suggests some guidelines for CRD authors to manage this metric and improve the UX of their CRDs.</abstract>
                <slug>cloud-native-rejekts-na-los-angeles-hybrid-2021-341-troubleshooting-kubernetes-crds-is-too-damn-hard</slug>
                <track></track>
                
                <persons>
                    <person id='376'>Nick Young</person>
                </persons>
                <language>en</language>
                <description>Here&#8217;s the situation. You&#8217;ve installed the latest piece of awesome Kubernetes tech, which comes with a set of CRDs. You set up everything you want, and then&#8230; nothing. What do you do? How do you figure out what&#8217;s gone wrong?

How many kubectl commands do you need to understand what&#8217;s happened? A lot of the time, this number is surprisingly large.

CRD designers can help by carefully designing the &#8220;status&#8221; section of CRDs with this metric in mind. Hear from a builder of CRDs about what they&#8217;ve learned about what to do and what not to do. From solving the murder mystery of troubleshooting Ingress, to the far better experience that comes from following the API conventions and making good use of Conditions, there&#8217;s a lot to be learned from prior art in this area.

The talk will finish up with some guidelines you can use for building your own CRDs, or reviewing others for ease of use.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/9SWLKZ/</url>
                <feedback_url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/9SWLKZ/feedback/</feedback_url>
            </event>
            <event guid='b30fd9bf-8775-5437-8439-4b3020484119' id='325'>
                <room>Main stage</room>
                <title>National Association of W Lovers: How We Can Create a Thriving Wasm Ecosystem</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2021-10-09T17:10:00-07:00</date>
                <start>17:10</start>
                <duration>00:30</duration>
                <abstract>Just as Java beget a litany of J-titled projects and Kubernetes gave us everything from KOPS to K3S, the emerging Wasm landscape is littered with W names. Wasm Fever has officially begun! And we at DeisLabs are releasing many Wasm-related projects.

While it might seem like we&apos;re peppering the landscape with arbitrary tools and projects, we have a bigger vision in mind--one focused on building a community and an ecosystem that enables a new generation of portable and secure applications.

In this talk, we articulate our ambitions for the WebAssembly community as a whole, and show how our open source projects fit in.</abstract>
                <slug>cloud-native-rejekts-na-los-angeles-hybrid-2021-325-national-association-of-w-lovers-how-we-can-create-a-thriving-wasm-ecosystem</slug>
                <track></track>
                
                <persons>
                    <person id='369'>Taylor Thomas</person><person id='390'>Matt Butcher</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/NAJNKG/</url>
                <feedback_url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/NAJNKG/feedback/</feedback_url>
            </event>
            <event guid='d6d6e937-159b-5b19-a1c2-34cf1806d74c' id='302'>
                <room>Main stage</room>
                <title>Tinkerbell, a deep dive into the magic of cloud native bare metal</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2021-10-09T17:50:00-07:00</date>
                <start>17:50</start>
                <duration>00:30</duration>
                <abstract>Servers are everywhere, your VMs, containers, functions and even &quot;serverless&quot; code lives, breathes and runs on servers. Unfortunately even today managing the lifecycle of a bare metal server still requires antiquated tooling, scripts and is largely difficult to manage and operate. The tinkerbell project was born out of the Bare Metal as a service company Packet (now Equinix Metal) with the simple goal of modernising the task of maintaining the bare metal lifecycle. This talk will go under the hood of tinkerbell to detail the technologies that power it, some of the functionality that enables bare metal servers to now deploy in seconds and finally how we&apos;re extending tinkerbell in the cloud native space through Cluster-API.</abstract>
                <slug>cloud-native-rejekts-na-los-angeles-hybrid-2021-302-tinkerbell-a-deep-dive-into-the-magic-of-cloud-native-bare-metal</slug>
                <track></track>
                
                <persons>
                    <person id='151'>Daniel Finneran</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/HLFTPP/</url>
                <feedback_url>https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-los-angeles-hybrid-2021/talk/HLFTPP/feedback/</feedback_url>
            </event>
            
        </room>
        
    </day>
    
</schedule>
