Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

29 lines
91 KiB
Markdown
Raw Permalink Normal View History

---
preview_image:
hero:
image: /icons/containers.svg
title: "Advanced Infrastructure as Code - Workshop with Luke Hoban"
title: "Advanced Infrastructure as Code - Workshop with Luke Hoban"
meta_desc: |
In this workshop, Pulumi experts cover advanced infrastructure as code topics including authoring components, multi-stack architectures, and testing
url_slug: advanced-infrastructure-as-code-workshop-with-luke-hoban
featured: false
pre_recorded: true
pulumi_tv: false
unlisted: false
gated: false
type: webinars
external: false
no_getting_started: true
block_external_search_index: false
main:
title: "Advanced Infrastructure as Code - Workshop with Luke Hoban"
description: |
In this workshop, Pulumi experts cover advanced infrastructure as code topics including authoring components, multi-stack architectures, and testing. You'll also learn how to apply infrastructure as code to Kubernetes - both for provisioning managed Kubernetes clusters and deploying Kubernetes applications and services on top of existing clusters. Get started: https://pulumi.com/start
sortable_date: 2020-04-17T02:45:22Z
youtube_url: https://www.youtube.com/embed/YHol6Vb2rD4
transcript: |
All right. Hi, everyone and welcome to part two of our infrastructures code workshop. Uh This one on advanced infrastructures code. Uh My name is Luke Hoban. I'm gonna be walking us through the workshop today. Um We're gonna give folks a few minutes uh to stream in here. Uh So we'll probably start in about three minutes. So first, uh just to make this a little bit interactive off the off the gun, uh wanna just sort of ask folks to uh fill out this poll so you can respond up here at poly V dot com slash lu co 275. Uh and just want to know how many people here attended uh part one of the workshop last week or checked it out on youtube uh or have generally uh already uh you know, used Pulumi a fair bit. All right. And wait for a few more to come in, see, see how much uh input we can get here. We'll have a few more of these polls throughout as well. So, um we'll try to make sure that uh for folks who do get this set up, it'll be easier to go and answer kind of some of the next polls as well. All right, great. Uh So a decent split. So a lot of folks did attend. Uh So that's good. Um uh I'll give a really quick recap of uh part one, but I am gonna dive into some uh some meaningfully more kind of advanced concepts and material throughout this. Um So definitely hope that that folks uh um have had a chance to check out Pulumi uh prior to this. Um And if not uh feel free to ask questions as we go and then we'll try and address any, any topics that uh that you guys want to cover his background. OK. So just as a recap for last time, I think we talked about a few key things. Thanks. Get rid of this. So presentation bar down here. That's right. OK. So as a recap, um we talked about a few key things. So one is we talked about modern infrastructures code and kind of Pulumi enabling us to do uh infrastructures code for the modern cloud and that being things like containers and servers and, and not just for the compute parts of that, but for all of the infrastructure we need to develop. So that could be the compute uh you know, compute containers, whether it's the B MS or the serverless functions or the container uh or it could be the core infrastructure layers, the networking and security uh that we need to set up or it could be the data stores, the um the object stores with S3 that we demoed uh and walked through in the workshop last time, uh or you know R DS databases or what have you. Um And then finally kind of the application layer and how do we deploy the application components themselves into that computer? And so Pulumi really, uh you know, we looked at kind of what that modern infrastructures code looks like, how that shift into uh into kind of the cloud infrastructure world is impacting the way that we think about uh needing to uh use more expressive ways to describe our cloud infrastructure instead of just pointing and clicking or, or uh scripting uh are our infrastructure deployments. And, and part of that was really the idea of kind of enabling developers and infrastructure engineers to collaborate. And so one of the key things with Pulumi uh is trying to bring those two worlds a bit more together um as we move quicker with our infrastructure, we need to uh have the development and ops teams kind of be working in unison and often actually uh collaborating together closely. Uh And so, one of the things that Pulumi really enables both with modern infrastructures and with uh using real programing languages uh is a closer uh ability for development and infrastructure engineers to work together. And then we talked about kind of uh the, the sort of key thing that makes ploy different than some of the other infrastructure code code tools that that folks may have worked with in the past, whether it's cloud formation or terraform or he uh in the space. And that is that plume kind of lets you use real programming languages. So it lets you use Python or javascript or go or dot net. Uh And this brings some sort of basic things that are just nice to have like loops and conditionals and functions and classes. And we saw some of these
---