It is a truth universally acknowledged that a techie in possession of any production code whatsoever must be in want of a container orchestration platform. What’s up for debate, according to noted thought leader Jane Austen, is how many pizzas the team is going to eat.
Let’s explore how to create and operate a Kubernetes cluster in order to answer this crucial question. If you’re into dev or ops or some portmanteau thereof, this is relevant to your interests. We’ll be following an Azure variant based on the open-source k8s training at http://container.training/, as well as trying out AKS (Azure Container Service); there are takeaways no matter which public or private cloud you use.
As our team grows, we’re going to need to scale our k8s cluster, deploying and configuring our pizza delivery app. We’ll deal with the consequences of state (you know, where your customers and money live) and carry out service discovery between our deliciously independent microservices. We’ll level up on k8s (and pizza) together.
Bridget Kromhout is a Principal Cloud Developer Advocate at Microsoft. Her CS degree emphasis was in theory, but she now deals with the concrete (if ‘cloud’ can be considered tangible). After 15 years as an operations engineer, she traded being on call for being on a plane. A frequent speaker and program committee member for tech conferences, she leads the devopsdays organization globally and the devops community at home in Minneapolis. She podcasts with Arrested DevOps, blogs at bridgetkromhout.com, and is active in a Twitterverse near you.
Help us make this conference the best it can be for you. Have questions you'd like this speaker to address? Suggestions for issues that deserve extra attention? Feedback that you'd like to share with the speaker and other attendees?
Join the conversation here (requires login)
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org