In this talk, Paul will demonstrate why TypeScript is a great language of choice for infrastructure management. Pulumi is an open source tool that allows users to write their infrastructure code in TypeScript, Python or Go.

TypeScript allows infrastructure code to have integrated testing, compile time checks as well as being able to create infrastructure APIs. This will show why a real language is more suited to infrastructure management than DSLs, JSON or YAML. In addition, he will cover how to build infrastructure that manages Serverless, PaaS and IaaS systems across multiple cloud providers.

Learn all about Infrastructure as Code: from concepts, to serverless and container technologies, including several hands-on labs to teach you best practices for managing infrastructure in public cloud and Kubernetes.

In this workshop, we will be using a new Infrastructure as Code tool, Pulumi.

You will leave this workshop with a better understanding of modern cloud architectures, the role infrastructure as code has to play in them, and with actionable best practices you can bring back to your teams today.

What You'll Learn:

We will begin with an introduction talk, briefly covering a number of topic, and then transition to hands-on labs to teach you the practicalities of using infrastructure as code to manage public cloud infrastructure on AWS and Kubernetes. You will leave knowing everything you need to be successful with infrastructure as code in your team.

Modern Cloud Architectures: Networking, clustering, containers, Kubernetes, serverless

Modern Infrastructure as Code: immutable infrastructure, automated delivery, policy as code

Infrastructure Patterns: provisioning infrastructure, versioning infrastructure, scaling applications, building and publishing container images, packaging and reusing infrastructure best practices

Most cloud providers now offer "easy to use" managed Kubernetes clusters, allowing us to get up and running in no time. Then our teams can just deploy containerized apps to them and life is good ..... Or is it? The truth is, this apparent simplicity fades quickly. The difficulties of adopting Kubernetes really hit hard on day two and beyond, when you need to integrate with existing infrastructure technologies and techniques. This includes IAM, networking, load balancing, DNS, monitoring, and logging, in addition to practices like continuous delivery, zero-downtime upgrades, and principle of least authority. Most of us underestimate how difficult these production concerns will be — even though it's getting easier by the day, it's still no casual walk in the park. In this talk, we'll discuss common challenges we see with end users and how we have approached addressing them. You will gain a broad awareness of these challenges so you know what to be on the lookout for and, by being proactive and going in with eyes wide open, will significantly increase the odds of success in your own team's journey to containers and Kubernetes.