Podcast appearances and mentions of justin garrison

Container-based Linux distributions are gaining traction, especially for edge deployments that demand lightweight and secure operating systems. Talos Linux, developed by Sidero Labs, is purpose-built for Kubernetes with security-first features like a fully immutable file system and disabled SSH access. In a demo, Sidero CTO Andrew Rynhard and Head of Product Justin Garrison explained Talos's design philosophy, highlighting its minimalism and focus on automation. Inspired by CoreOS, Talos removes traditional tools like systemd and Bash, replacing them with machineD, a custom process manager written in Go.Talos emphasizes API-driven management rather than SSH, making Kubernetes cluster operations more scalable and consistent. Its design supports cloud, bare metal, Docker, and edge devices like Raspberry Pi. Kernel immutability is reinforced by ephemeral signing keys. Through Sidero's Omni SaaS, Talos nodes connect securely via WireGuard. The operating system handles all certificates and network connectivity internally, streamlining security and deployment. As Garrison notes, Talos delivers a portable API for “big iron, small iron—no matter what.”Learn more from The New Stack about Sidero Labs:  Is Cluster API Really the Future of Kubernetes Deployment? Choosing a Linux Distribution Join our community of newsletter subscribers to stay on top of the news and at the top of your game. https://thenewstack.io/newsletter/ 

Justin serves as Head of Product at Sidero Labs. His career includes contributions to Oscar-winning films, the Disney+ streaming platform, and Amazon EKS. In his free time, Justin enjoys building modern-retro computers and watching Moana. He is the co-host of the FAFO.FM podcast with Autumn Nash. In this Episode he talks to Scott about his love for Linux and the Linux Desktop

Justin & Autumn get together one last time for a retro: favorite episodes, lessons learned, biggest surprises & what's next.

Phillip Carter, Principal PM at Honeycomb, joins Justin & Autumn to discuss his work at Microsoft & Honeycomb, building AI infrastructure & more.

Gerhard Lazu joins the show to discuss how Ship It! started and why you might want a general purpose language for your CI/CD.

Marc Boorshtein from Tremolo Security joins Justin & Autumn to talk all about running Kubernetes in the public sector.

Hazel Weakly joins Justin and Autumn to talk about when to build abstractions and how to implement them. They also share experiences from tech conferences, and delve into the importance of building community and psychological safety in tech environments.

Preston Doster joins the show to tell us what it takes to run a Mastodon server with 55,000 accounts and 11,000 monthly active users.

No interview this week! Instead, Justin & Autumn sit down to talk about what they've been learning recently.

Maybe Jira for your kids' chores is a good idea... Probably not.

From switching ISPs to migrating Amazon off Oracle, Pete Naylor knows which database to use.

Adam Jacob remains optimistic about the future for infrastructure and is building new ideas to make it better.

Lili Cosic's experience at different companies & communities has given her insights into what's important & when to adapt to learn new (or old) things.

Dave Eddy has learned systems programming the traditional way with books and man pages. Now he's sharing what he's learned, starting with bash.

The ability to learn on the job has been a critical skill for David Beale throughout his career. Is the job market not allowing that anymore?

uBlue is trying to build the world's best Linux experience for developers and gamers. Jorge Castro joins Justin & Autumn to tell us how it's going.

David Flanagan created a successful YouTube channel but knew to take things to the next level he'd need to own more of the stack.

Emily Freeman joins the show alongside our Ship It co-host, Justin Garrison! We hear Emily's burnout story & learn how she and Forrest Brazeal are putting tech-focused influencers on tap. But first: area code turf wars, bad movie reboots & buying used DVDs... at Starbucks?!

Du'An Lightfoot, dev advocate at AWS, joins Justin & Autumn to discuss networking, a knowledge gap people many people have. You can ignore the things you don't understand or you can invest time to learn it.

Emily Freeman joins the show alongside our Ship It co-host, Justin Garrison! We hear Emily's burnout story & learn how she and Forrest Brazeal are putting tech-focused influencers on tap. But first: area code turf wars, bad movie reboots & buying used DVDs... at Starbucks?!

What if your infrastructure diagram was responsible for the actual infrastructure?! John Watson & Scott Prutton from System Initiative join Justin & Autumn to discuss.

Silvia Botros joins Justin & Autumn for a phenomenal conversation about databases, her career path & the ins/outs of writing _High Performance MySQL_.

Flavors of Ship It on The Changelog — if you're not subscribed to Ship It yet, do so at shipit.show or by searching for "Ship it" wherever you listen to podcasts. Every week Justin Garrison and Autumn Nash explore everything that happens after `git push` — and today's flavors include running infrastructure in space, managing millions of machines at Meta, and what it takes to control your 3D printer with OctoPrint.

Flavors of Ship It on The Changelog — if you're not subscribed to Ship It yet, do so at shipit.show or by searching for "Ship it" wherever you listen to podcasts. Every week Justin Garrison and Autumn Nash explore everything that happens after `git push` — and today's flavors include running infrastructure in space, managing millions of machines at Meta, and what it takes to control your 3D printer with OctoPrint.

Justin & Autumn are joined by Steven Wu from Scanner. Scanner built logging infrastructure focused on security teams and occasional querying. We dive deep into how architectural decisions affect your business.

Tim Banks joins Justin and Autumn — there's nothing quite like being punched in the face by Zookeeper or being taken down by a "hot" shard.

Deploying new applications can be tough. Deploying configuration management safely at scale with stores around the world is different. Martin Jackson joins us to discuss.

Michael Gat joins us for a look back on mainframes & why sometimes deploying on a Friday IS the right thing to do.

Nick Janetakis is back and this time we're talking about TUIs (text-based user interfaces) — some we've tried and some we plan to try. All are collected from Justin Garrison's Awesome TUIs repo on GitHub. This episode is "AI free."

GitLab has changed a lot over the past 8 years and so has Abubakar. Starting in the help desk he's seen a lot and takes us through GitLab's and his progression.

Nick Janetakis is back and this time we're talking about TUIs (text-based user interfaces) — some we've tried and some we plan to try. All are collected from Justin Garrison's Awesome TUIs repo on GitHub. This episode is "AI free."

Git was designed to be distributed but there is a lot of gravity around GitHub. What does the model look like for a business that encourages you to run your own git server and what does the backend for gitea.com look like?

Gareth Greenaway from the Salt project joins us for a trip down memory lane with configuration management and why open source projects have changed over the past decade.

Bailey Hayes & Taylor Thomas from Cosmonic join the show for a look at WebAssembly Standard Interfaces (WASI) and trade-offs for portable interfaces.

Devyn Cairns & Jakub Žádník join Justin & Autumn to talk about building a new kind of cross-platform shell that provides easy extensions with traditional command compatibility. That's no easy feat!

Render founder/CEO Anurag Goel joins us for a look behind their platform. An application native hosting option that hides the lower levels still requires a LOT of infrastructure.

Gina Häußge is here to tell us about the infra behind the OctoPrint project, which tests and releases new versions that work on multiple different printers and gets deployed hundreds of thousands of times.

Justin Garrison, Director of Developer Relations at Sidero, joins Corey to discuss Justin's experience transitioning from large companies like AWS and Disney to a more agile company like Sidero, the benefits of using simplified Linux distributions like Talos OS for running Kubernetes, and the pros of on-premises setups for certain workloads. The conversation touches upon challenges with cloud provider limitations, the impacts of computing power on both an economic and environmental scale and Corey and Justin's frustration with businesses touting their use of AI when they've already abandoned those projects. Show Highlights: (00:00) - Introduction(01:09) - Justin's Background and Career Journey(02:39) - Transition to Sidero(03:51) - Using Personal Devices for Work(08:09) - Talos Linux and Kubernetes(15:19) - Kubernetes Upgrades and On-Prem Challenges(19:21) - Building Your Own Cloud Platform(21:52) - Multi-Cloud vs. Hybrid Cloud(25:15) - Scaling and Resource Management(28:02) - Gaming and Cloud Bursting(32:46) - AI and GPU Challenges(34:54) - Balancing On-Prem and Cloud Solutions(40:49) - Final Thoughts and ContactAbout Justin:Justin is a historian living in the future. Lucky enough to play with cool technologies and hopeful enough to bring others along for the ride.Links Referenced:Justin's Website: http://justingarrison.comJustin on Bluesky: https://bsky.app/profile/justingarrison.comJustin Garrison on LinkedIn: https://www.linkedin.com/in/justingarrison/*SponsorPanoptica: https://www.panoptica.app/

Danielle Lancashire is here to tell us how Fermyon cloud is built on top of nomad and EC2 and how they put it in a box with Kubernetes and WebAssembly.

Jon “gzip enthusiast” Johnson joins us for a history lesson on compression & how it impacts everything from containers to Alpine.

Andrew Atkinson joins Autumn & Justin to tell them why folks should (and are) picking PostgreSQL as their database in 2024 and how to scale it.

All of the health anxiety of early internet adopters traced back to WebMD's self diagnosis. Some sysadmin's on-call nightmares came from a different part of the site.

Anita Zhang is here to tell us how Meta manages millions of bare metal Linux hosts and containers. We also discuss the Twine white paper and how AI is changing their requirements.

In this episode Justin and Autumn are joined by Mandi Walls to take you back to a time before the cloud. Before Kubernetes. When a/s/l was common and servers were made of metal. Back to the days of AOL to discuss how chat rooms worked.

Paul Frazee joins the show to tell us all about how Bluesky builds, tests, and deploys mobile and web applications from the same code base.

Why would you want to switch your developer environments from containers to nix? Ádám from LastPass has a few reasons.

Verónica López, Kubernetes SIG Release tech lead & distributed systems engineer, joins Justin & Autumn to share her experiences deploying services at scale.

Justin & Autumn take you with them to the 2024 SoCal Linux Expo where they asked six fellow attendees about their favorite open source projects and their least favorite commands.

What's the difference between productivity engineering and platform engineering? How can you continue to re-platform with a moving target? On this episode, we're joined by Andy Glover, who spent ten years productivity engineering at Netflix, to discuss.

Kyle Quest joins the show to tell Autumn & Justin all about the evolution of DockerSlim & minimal container images. Why are small container images important? What are different strategies to make containers smaller? Let's find out!

Autumn and Justin are joined by Chris Swan to discuss tech industry trends like AI and sustainability, gamifying the software development process and motivating devs to write more secure code, OpenSSF Scorecards and how they offer a way to measure and improve the security and compliance of GitHub repos, the scoring system, and the security posture of a repository.

Justin is a developer who's helped create Oscar winning movies at Disney Animation, built infrastructure for Disney+, and worked on EKS at AWS. He is now the Director of Developer Relations at Sidero Labs and host of the Ship it! podcast You can find Justin on the following sites: Twitter Website PLEASE SUBSCRIBE TO THE PODCAST Spotify Apple Podcasts Google Podcasts Amazon Music RSS Feed You can check out more episodes of Coffee and Open Source on https://www.coffeeandopensource.com Coffee and Open Source is hosted by Isaac Levin --- Support this podcast: https://podcasters.spotify.com/pod/show/coffeandopensource/support

Wanny Morellato & Deepak Mohandas from Kong join Justin & Autumn to discuss building, testing & running a load balancer that can run anywhere.

What do you do when your infrastructure runs 1000 miles away and you only have access every 90 minutes? Find out from Andrew Guenther from Orbital Sidekick.

We're back! Jason Hall joins the show to tell Justin & Autumn all about how Chainguard builds hundreds of containers without a single Dockerfile.

This week we're going deep on security and what it takes to shift left, seriously. Adam is joined by Justin Garrison (co-host of Ship It), plus two members of the BoxyHQ team — Deepak Prabhakara, Co-founder & CEO and Schalk Neethling, Community Manager and DevRel as well as fellow Changelog Slack member. We discuss how to shift left, the role of the developer and the burden of security, the importance of tooling, the difference between authentication and authorization, and a mindset change for when security takes place — it's a matter of “when” not “who.”

This week we're going deep on security and what it takes to shift left, seriously. Adam is joined by Justin Garrison (co-host of Ship It), plus two members of the BoxyHQ team — Deepak Prabhakara, Co-founder & CEO and Schalk Neethling, Community Manager and DevRel as well as fellow Changelog Slack member. We discuss how to shift left, the role of the developer and the burden of security, the importance of tooling, the difference between authentication and authorization, and a mindset change for when security takes place — it's a matter of “when” not “who.”

Justin Garrison joins us to talk about Amazon's silent sacking, from his perspective. He should know. He works there. Well, as of yesterday he quit. We discuss how the cloud and Kubernetes have transformed the way software is developed and deployed, the impact silent layoffs have on employees and their careers, speaking out about workplace issues (the right way), how changes in organizational structure can lead to gaps in expertise and responsibility which can lead to potential outages and slower response times. By the way, we officially let the cat off out of the bag in this episode. Justin has joined the ranks here at Changelog and is taking over as the host of Ship It! Expect new episodes soon.

Justin Garrison joins us to talk about Amazon's silent sacking, from his perspective. He should know. He works there. Well, as of yesterday he quit. We discuss how the cloud and Kubernetes have transformed the way software is developed and deployed, the impact silent layoffs have on employees and their careers, speaking out about workplace issues (the right way), how changes in organizational structure can lead to gaps in expertise and responsibility which can lead to potential outages and slower response times. By the way, we officially let the cat off out of the bag in this episode. Justin has joined the ranks here at Changelog and is taking over as the host of Ship It! Expect new episodes soon.

Dan North tells the tale of Tim, the worst programmer he's worked with (who also is a heck of a programmer), Kevin Lin declares that OpenTelemetry delivers on its promise for open observability, Justin Garrison details Terraform vs GitOps vs System Initiative, Inc. writes how Apple beats burnout & Aline Lerner's advice on how (not) to sabotage your salary negotiations before you even start.

Dan North tells the tale of Tim, the worst programmer he's worked with (who also is a heck of a programmer), Kevin Lin declares that OpenTelemetry delivers on its promise for open observability, Justin Garrison details Terraform vs GitOps vs System Initiative, Inc. writes how Apple beats burnout & Aline Lerner's advice on how (not) to sabotage your salary negotiations before you even start.

Dan North tells the tale of Tim, the worst programmer he's worked with (who also is a heck of a programmer), Kevin Lin declares that OpenTelemetry delivers on its promise for open observability, Justin Garrison details Terraform vs GitOps vs System Initiative, Inc. writes how Apple beats burnout & Aline Lerner's advice on how (not) to sabotage your salary negotiations before you even start.

Everything about this is wrong This week we discuss the digital transformation of paid TV, the struggle to modernize the IRS and DHH's MRSK project. Plus, Matt is Factorio famous… Watch the YouTube Live Recording of Episode 403 (https://www.youtube.com/watch?v=4Ep_x-LOg4M) Runner-up Titles Forbidden Everything needs cables Got to be Grammarly I've got a lot of hills to die on A hatred for their customers They wanted to hate your corpse Except for The Wu-Tang Saga You've abandoned the ship No, no, we need to spy on you You are gaslighting what your selling I wouldn't touch this Full of chef kiss quotes Rundown What the NBA Can Learn From Formula 1 (https://stratechery.com/2023/what-the-nba-can-learn-from-formula-1/) IRS tech is so ‘archaic' the agency struggles to find people to work it (https://www.washingtonpost.com/politics/2023/02/24/irs-technology-gao-report-archaic/) Screaming in the Cloud #357: Stepping Onto the AWS Commerce Platform with James Greenfield (https://www.lastweekinaws.com/podcast/screaming-in-the-cloud/stepping-onto-the-aws-commerce-platform-with-james-greenfield/) US Digital Service (https://www.usds.gov/) Individual Master File (https://en.wikipedia.org/wiki/Individual_Master_File) Introducing MRSK (https://world.hey.com/dhh/introducing-mrsk-9330a267) mrsked/mrsk (https://github.com/mrsked/mrsk) Justin Garrison @rothgar's take (https://twitter.com/rothgar/status/1630634683313848320) Relevant to your Interests After Fraud Charges Against Slync's Ex-CEO, Goldman Sachs Doubles Down With $24 Million Investment (https://www.forbes.com/sites/davidjeans/2023/02/22/slync-goldman-sachs-chris-kirchner-funding/?sh=52642f354594) ChatGPT-style search represents a 10x cost increase for Google, Microsoft (https://arstechnica.com/gadgets/2023/02/chatgpt-style-search-represents-a-10x-cost-increase-for-google-microsoft/) Why everyone's talking about Section 230 - The Hustle (https://thehustle.co/02232023-Section-230/) Reveal Survey Report: Top Software Development Challenges For 2023 (https://www.revealbi.io/whitepapers/reveal-survey-report-top-software-development-challenges-for-2023) Microsoft previews cost-efficient Azure VMs (https://www.theregister.com/2023/02/22/microsoft_cheap_azure_vms/) DOJ Preps Antitrust Suit to Block Adobe's $20 Billion Figma Deal (https://www.bloomberg.com/news/articles/2023-02-23/doj-preparing-suit-to-block-adobe-s-20-billion-deal-for-figma) Oracle Cloud Made All The Right Moves In 2022 - Moor Insights & Strategy (https://moorinsightsstrategy.com/oracle-cloud-made-all-the-right-moves-in-2022/) DoJ to block Adobe purchase of Figma on competition concerns (https://www.theregister.com/2023/02/24/doj_to_block_adobe_purchase/) Your jailbroken ChatGPT might violate OpenAI's safety guidelines when role-playing as ‘DAN' (https://www.fastcompany.com/90845689/chatgpt-dan-jailbreak-violence-reddit-rules) Is WebAssembly Really the Future? (https://thenewstack.io/is-webassembly-really-the-future/) Elon Musk says remaining Twitter employees will receive ‘very significant' stock awards on March 24th (https://www.theverge.com/2023/2/27/23616933/elon-musk-twitter-employees-stock-awards-march-after-more-layoffs) Salesforce weighing up more job cuts to hit margin goal (https://www.theregister.com/2023/02/27/salesforce_job_losses_not_over/) Alphabet Needs to Replace Sundar Pichai (https://www.theinformation.com/articles/alphabet-needs-to-replace-sundar-pichai) LastPass Reveals Second Attack Resulting in Breach of Encrypted Password Vaults (https://thehackernews.com/2023/02/lastpass-reveals-second-attack.html) Stack Overflow Stats (https://twitter.com/sahnlam/status/1629713954225405952) Nonsense Twitter had 88,188 channel (https://twitter.com/zoeschiffer/status/1630346916335865857?s=46&t=DiH5HJagHYkpKEP13Yz6Cg%20%20Zoë%20SchifferZoë%20Schiffer%20@ZoeSchiffer) but they don't have THE THREAD. (https://softwaredefinedtalk.slack.com/archives/C5GPMBXQT/p1590186505165200) Sponsors The MacGeekGab.com Podcast (https://www.macgeekgab.com) provides tips, Cool Stuff Found, and answers to your questions about anything and everything Apple. Subscribe now! (https://www.macgeekgab.com/subscribe-to-podcast/) Conferences Southern California Linux Expo, (https://www.socallinuxexpo.org/scale/20x) Los Angeles, March 9-12, 2023 Matt (https://www.socallinuxexpo.org/scale/20x/presentations/kubernetes-cloud-cost-monitoring-opencost-optimization-strategies) & Cote (https://www.socallinuxexpo.org/scale/20x/presentations/lessons-learned-7-years-running-developer-platforms)! Use Discount Code: DEVOP Coté and Matt arranging a live recording. PyTexas 2023, Austin, TX April 1 - 2, 2023 (https://www.pytexas.org) KubeCon EU Amsterdam, April 18-21 (https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/) - Matt & Cote will be there DevOpsDays Birmingham, AL 2023 (https://devopsdays.org/events/2023-birmingham-al/welcome/), April 20 - 21, 2023 DevOpsDays Austin 2023 (https://devopsdays.org/events/2023-austin/welcome/), May 4-5 SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us on Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), Mastodon (https://hachyderm.io/@softwaredefinedtalk), LinkedIn (https://www.linkedin.com/company/software-defined-talk/) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Brandon: (https://www.homedepot.com/p/Husky-5-Tier-Industrial-Duty-Steel-Freestanding-Garage-Storage-Shelving-Unit-in-Black-90-in-W-x-90-in-H-x-24-in-D-N2W902490W5B/319132842) Drive to Survive Season 5 (https://www.netflix.com/title/80204890) Matt Factorio Story Missions (https://mods.factorio.com/mod/Story-Missions) Recent podcast appearances Software Engineering Daily (https://softwareengineeringdaily.com/2023/02/10/kubernetes-cost-management/) The Cloudcast (https://www.thecloudcast.net/2022/07/kubernetes-cost-management.html) Open Observability Talks (https://www.youtube.com/watch?v=mhqXQV2jsxo) Photo Credits Header (https://unsplash.com/photos/kAJLRQwt5yY) CoverArt (https://unsplash.com/photos/U-Vu_r6qyyU)

Kris Nóva is an author, engineer, public speaker and transgender activist best known for her work on Aurae, Linux, and Kubernetes. She specializes in Linux kernel security, distributed systems, infrastructure management, and open source software engineering. In 2022 she authored Hacking Capitalism an independently published book about modeling the tech industry as a system. In 2017 she co-authored Cloud Native Infrastructure published by O'Reilly Media with Justin Garrison. Nóva is well known for her open source work. She has created many successful open source projects and has contributed to projects like Linux, Kubernetes, Rust, Go, etc. A popular public speaker, she is best known for her Kubernetes clusterfuck talks. Today she works as a principal engineer at GitHub focusing on infrastructure platform engineering. You can follow Kris on Social Media https://hachyderm.io/@nova https://nivenly.com/ https://github.com/krisnova PLEASE SUBSCRIBE TO THE PODCAST - Spotify: http://isaacl.dev/podcast-spotify - Apple Podcasts: http://isaacl.dev/podcast-apple - Google Podcasts: http://isaacl.dev/podcast-google - RSS: http://isaacl.dev/podcast-rss You can check out more episodes of Coffee and Open Source on https://www.coffeeandopensource.com/n Coffee and Open Source is hosted by Isaac Levin (https://twitter.com/isaacrlevin) --- Support this podcast: https://podcasters.spotify.com/pod/show/coffeandopensource/support

Connecting with Justin Garrison (@justingarrison), Managing Director of Riviera Luxury Rentals ✨ (@rivieraluxuryrentals) They have exclusively the most amazing collection of luxury villas for rent in the French Riviera

Show notes:Normally I'd plug the Patreon but I'm in the process of switching over to GitHub Sponsors. More info soon.Justin's TwitterRich's TwitterKube Cuddle TwitterLinks:Kubernetes the Hard WayNomadJustin's scheduler written in BashThe yes command's man pageJustin's TikTokJustin's KubeCon talk where he built Kubernetes with a spreadsheetRich and Justin on Containers from the CouchTGIKKarpenterkOpsJustin's re:Invent talk on using ECS at DisneyCopilot | App RunnerListener question from @landau_charles, thank you!Episode TranscriptLogo by the amazing Emily Griffin.Music by Monplaisir.Thanks for listening. ★ Support this podcast on Patreon ★

“I would rather entertain and hope that people learned something than educate people and hope they were entertained” ~ Walt Disney Justin provides us an insight on how he comes up with his entertaining but educational ideas. More info about Justin http://www.tiktok.com/@justinleegarrisontwitter.com/rothgar cftc.info - Justin's work on YouTube The recent hardware project I mentioned https://www.justingarrison.com/blog/2022-07-06-cubernetes/

“I would rather entertain and hope that people learned something than educate people and hope they were entertained” ~ Walt Disney Justin provides us an insight on how he comes up with his entertaining but educational ideas. More info about Justin http://www.tiktok.com/@justinleegarrisontwitter.com/rothgar cftc.info - Justin's work on YouTube The recent hardware project I mentioned https://www.justingarrison.com/blog/2022-07-06-cubernetes/

About ChrisChris Short has been a proponent of open source solutions throughout his over two decades in various IT disciplines, including systems, security, networks, DevOps management, and cloud native advocacy across the public and private sectors. He currently works on the Kubernetes team at Amazon Web Services and is an active Kubernetes contributor and Co-chair of OpenGitOps. Chris is a disabled US Air Force veteran living with his wife and son in Greater Metro Detroit. Chris writes about Cloud Native, DevOps, and other topics at ChrisShort.net. He also runs the Cloud Native, DevOps, GitOps, Open Source, industry news, and culture focused newsletter DevOps'ish.Links Referenced: DevOps'ish: https://devopsish.com/ EKS News: https://eks.news/ Containers from the Couch: https://containersfromthecouch.com opengitops.dev: https://opengitops.dev ChrisShort.net: https://chrisshort.net Twitter: https://twitter.com/ChrisShort TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. Coming back to us since episode two—it's always nice to go back and see the where are they now type of approach—I am joined by Senior Developer Advocate at AWS Chris Short. Chris, been a few years. How has it been?Chris: Ha. Corey, we have talked outside of the podcast. But it's been good. For those that have been listening, I think when we recorded I wasn't even—like, when was season two, what year was that? [laugh].Corey: Episode two was first pre-pandemic and the rest. I believe—Chris: Oh. So, yeah. I was at Red Hat, maybe, when I—yeah.Corey: Yeah. You were doing Red Hat stuff, back when you got to work on open-source stuff, as opposed to now, where you're not within 1000 miles of that stuff, right?Chris: Actually well, no. So, to be clear, I'm on the EKS team, the Kubernetes team here at AWS. So, when I joined AWS in October, they were like, “Hey, you do open-source stuff. We like that. Do more.” And I was like, “Oh, wait, do more?” And they were like, “Yes, do more.” “Okay.”So, since joining AWS, I've probably done more open-source work than the three years at Red Hat that I did. So, that's kind of—you know, like, it's an interesting point when I talk to people about it because the first couple months are, like—you know, my friends are like, “So, are you liking it? Are you enjoying it? What's going on?” And—Corey: Do they beat you with reeds? Like, all the questions people have about companies? Because—Chris: Right. Like, I get a lot of random questions about Amazon and AWS that I don't know the answer to.Corey: Oh, when I started telling people, I fixed Amazon bills, I had to quickly pivot that to AWS bills because people started asking me, “Well, can you save me money on underpants?” It's I—Chris: Yeah.Corey: How do you—fine. Get the prime credit card. It docks 5% off the bill, so there you go. But other than that, no, I can't.Chris: No.Corey: It's—Chris: Like, I had to call my bank this morning about a transaction that I didn't recognize, and it was from Amazon. And I was like, that's weird. Why would that—Corey: Money just flows one direction, and that's the wrong direction from my employer.Chris: Yeah. Like, what is going on here? It shouldn't have been on that card kind of thing. And I had to explain to the person on the phone that I do work at Amazon but under the Web Services team. And he was like, “Oh, so you're in IT?”And I'm like, “No.” [laugh]. “It's actually this big company. That—it's a cloud company.” And they're like, “Oh, okay, okay. Yeah. The cloud. Got it.” [laugh]. So, it's interesting talking to people about, “I work at Amazon.” “Oh, my son works at Amazon distribution center,” blah, blah, blah. It's like, cool. “I know about that, but very little. I do this.”Corey: Your son works in Amazon distribution center. Is he a robot? Is normally my next question on that? Yeah. That's neither here nor there.So, you and I started talking a while back. We both write newsletters that go to a somewhat similar audience. You write DevOps'ish. I write Last Week in AWS. And recently, you also have started EKS News because, yeah, the one thing I look at when I'm doing these newsletters every week is, you know what I want to do? That's right. Write more newsletters.Chris: [laugh].Corey: So, you are just a glutton for punishment? And, yeah, welcome to the addiction, I suppose. How's it been going for you?Chris: It's actually been pretty interesting, right? Like, we haven't pushed it very hard. We're now starting to include it in things. Like we did Container Day; we made sure that EKS news was on the landing page for Container Day at KubeCon EU. And you know, it's kind of just grown organically since then.But it was one of those things where it's like, internally—this happened at Red Hat, right—when I started live streaming at Red Hat, the ultimate goal was to do our product management—like, here's what's new in the next version thing—do those live so anybody can see that at any point in time anywhere on Earth, the second it's available. Similar situation to here. This newsletter actually is generated as part of a report my boss puts together to brief our other DAs—or developer advocates—you know, our solutions architects, the whole nine yards about new EKS features. So, I was like, why can't we just flip that into a weekly newsletter, you know? Like, I can pull from the same sources you can.And what's interesting is, he only does the meeting bi-weekly. So, there's some weeks where it's just all me doing it and he ends up just kind of copying and pasting the newsletter into his document, [laugh] and then adds on for the week. But that report meeting for that team is now getting disseminated to essentially anyone that subscribes to eks.news. Just go to the site, there's a subscribe thing right there. And we've gotten 20 issues in and it's gotten rave reviews, right?Corey: I have been a subscriber for a while. I will say that it has less Chris Short personality—Chris: Mm-hm.Corey: —to it than DevOps'ish does, which I have to assume is by design. A lot of The Duckbill Group's marketing these days is no longer in my voice, rather intentionally, because it turns out that being a sarcastic jackass and doing half-billion dollar AWS contracts can not to be the most congruent thing in the world. So okay, we're slowly ameliorating that. It's professional voice versus snarky voice.Chris: Well, and here's the thing, right? Like, I realized this year with DevOps'ish that, like, if I want to take a week off, I have to do, like, what you did when your child was born. You hired folks to like, do the newsletter for you, or I actually don't do the newsletter, right? It's binary: hire someone else to do it, or don't do it. So, the way I structured this newsletter was that any developer advocate on my team could jump in and take over the newsletter so that, you know, if I'm off that week, or whatever may be happening, I, Chris Short, am not the voice. It is now the entire developer advocate team.Corey: I will challenge you on that a bit. Because it's not Chris Short voice, that's for sure, but it's also not official AWS brand voice either.Chris: No.Corey: It is clearly written by a human being who is used to communicating with the audience for whom it is written. And that is no small thing. Normally, when oh, there's a corporate newsletter; that's just a lot of words to say it's bad. This one is good. I want to be very clear on that.Chris: Yeah, I mean, we have just, like, DevOps'ish, we have sections, just like your newsletter, there's certain sections, so any new, what's new announcements, those go in automatically. So, like, that can get delivered to your inbox every Friday. Same thing with new blog posts about anything containers related to EKS, those will be in there, then Containers from the Couch, our streaming platform, essentially, for all things Kubernetes. Those videos go in.And then there's some ecosystem news as well that I collect and put in the newsletter to give people a broader sense of what's going on out there in Kubernetes-land because let's face it, there's upstream and then there's downstream, and sometimes those aren't in sync, and that's normal. That's how Kubernetes kind of works sometimes. If you're running upstream Kubernetes, you are awesome. I appreciate you, but I feel like that would cause more problems and it's worse sometimes.Corey: Thank you for being the trailblazers. The rest of us can learn from your misfortune.Chris: [laugh]. Yeah, exactly. Right? Like, please file your bugs accordingly. [laugh].Corey: EKS is interesting to me because I don't see a lot of it, which is, probably, going to get a whole lot of, “Wait, what?” Moments because wait, don't you deal with very large AWS bills? And I do. But what I mean by that is that EKS, until you're using its Fargate expression, charges for the control plane, which rounds to no money, and the rest is running on EC2 instances running in a company's account. From the billing perspective, there is no difference between, “We're running massive fleets of EKS nodes.” And, “We're managing a whole bunch of EC2 instances by hand.”And that feels like an interesting allegory for how Kubernetes winds up expressing itself to cloud providers. Because from a billing perspective, it just looks like one big single-tenant application that has some really strange behaviors internally. It gets very chatty across AZs when there's no reason to, and whatnot. And it becomes a very interesting study in how to expose aspects of what's going on inside of those containers and inside of the Kubernetes environment to the cloud provider in a way that becomes actionable. There are no good answers for this yet, but it's something I've been seeing a lot of. Like, “Oh, I thought you'd be running Kubernetes. Oh, wait, you are and I just keep forgetting what I'm looking at sometimes.”Chris: So, that's an interesting point. The billing is kind of like, yeah, it's just compute, right? So—Corey: And my insight into AWS and the way I start thinking about it is always from a billing perspective. That's great. It's because that means the more expensive the services, the more I know about it. It's like, “IAM. What is that?” Like, “Oh, I have no idea. It's free. How important could it be?” Professional advice: do not take that philosophy, ever.Chris: [laugh]. No. Ever. No.Corey: Security: it matters. Oh, my God. It's like you're all stars. Your IAM policy should not be. I digress.Chris: Right. Yeah. Anyways, so two points I want to make real quick on that is, one, we've recently released an open-source project called Carpenter, which is really cool in my purview because it looks at your Kubernetes file and says, “Oh, you want this to run on ARM instance.” And you can even go so far as to say, right, here's my limits, and it'll find an instance that fits those limits and add that to your cluster automatically. Run your pod on that compute as long as it needs to run and then if it's done, it'll downsize—eventually, kind of thing—your cluster.So, you can basically just throw a bunch of workloads at it, and it'll auto-detect what kind of compute you will need and then provision it for you, run it, and then be done. So, that is one-way folks are probably starting to save money running EKS is to adopt Carpenter as your autoscaler as opposed to the inbuilt Kubernetes autoscaler. Because this is instance-aware, essentially, so it can say, like, “Oh, your massive ARM application can run here,” because you know, thank you, Graviton. We have those processors in-house. And you know, you can run your ARM64 instances, you can run all the Intel workloads you want, and it'll right size the compute for your workloads.And I'll look at one container or all your containers, however you want to configure it. Secondly, the good folks over at Kubecost have opencost, which is the open-source version of Kubecost, basically. So, they have a service that you can run in your clusters that will help you say, “Hey, maybe this one notes too heavy; maybe this one notes too light,” and you know, give you some insights into Kubernetes spend that are a little bit more granular as far as usage and things like that go. So, those two projects right there, I feel like, will give folks an optimal savings experience when it comes to Kubernetes. But to your point, it's just compute, right? And that's really how we treat it, kind of, here internally is that it's a way to run… compute, Kubernetes, or ECS, or any of those tools.Corey: A fairly expensive one because ignoring entirely for a second the actual raw cost of compute, you also have the other side of it, which is in every environment, unless you are doing something very strange or pre-funding as a one-person startup in your spare time, your payroll costs will it—should—exceed your AWS bill by a fairly healthy amount. And engineering time is always more expensive than services time. So, for example, looking at EKS, I would absolutely recommend people use that rather than rolling their own because—Chris: Rolling their own? Yeah.Corey: —get out of that engineering space where your time is free. I assure you from a business context, it is not. So, there's always that question of what you can do to make things easier for people and do more of the heavy lifting.Chris: Yeah, and to your rather cheeky point that there's 17 ways to run a container on AWS, it is answering that question, right? Like those 17 ways, like, how much of this do you want to run yourself, you could run EKS distro on EC2 instances if you want full control over your environment.Corey: And then run IoT Greengrass core on top within that cluster—Chris: Right.Corey: So, I can run my own Lambda function runtime, so I'm not locked in. Also, DynamoDB local so I'm not locked into AWS. At which point I have gone so far around the bend, no one can help me.Chris: Well—Corey: Pro tip, don't do that. Just don't do that.Chris: But to your point, we have all these options for compute, and specifically containers because there's a lot of people that want to granularly say, “This is where my engineering team gets involved. Everything else you handle.” If I want EKS on Spot Instances only, you can do that. If you want EKS to use Carpenter and say only run ARM workloads, you can do that. If you want to say Fargate and not have anything to manage other than the container file, you can do that.It's how much does your team want to manage? That's the customer obsession part of AWS coming through when it comes to containers is because there's so many different ways to run those workloads, but there's so many different ways to make sure that your team is right-sized, based off the services you're using.Corey: I do want to change gears a bit here because you are mostly known for a couple of things: the DevOps'ish newsletter because that is the oldest and longest thing you've been doing the time that I've known you; EKS, obviously. But when prepping for this show, I discovered you are now co-chair of the OpenGitOps project.Chris: Yes.Corey: So, I have heard of GitOps in the context of, “Oh, it's just basically your CI/CD stuff is triggered by Git events and whatnot.” And I'm sitting here going, “Okay, so from where you're sitting, the two best user interfaces in the world that you have discovered are YAML and Git.” And I just have to start with the question, “Who hurt you?”Chris: [laugh]. Yeah, I share your sentiment when it comes to Git. Not so much with YAML, but I think it's because I'm so used to it. Maybe it's Stockholm Syndrome, maybe the whole YAML thing. I don't know.Corey: Well, it's no XML. We'll put it that way.Chris: Thankfully, yes because if it was, I would have way more, like, just template files laying around to build things. But the—Corey: And rage. Don't forget rage.Chris: And rage, yeah. So, GitOps is a little bit more than just Git in IaC—infrastructure as Code. It's more like Justin Garrison, who's also on my team, he calls it infrastructure software because there's four main principles to GitOps, and if you go to opengitops.dev, you can see them. It's version one.So, we put them on the website, right there on the page. You have to have a declared state and that state has to live somewhere. Now, it's called GitOps because Git is probably the most full-featured thing to put your state in, but you could use an S3 bucket and just version it, for example. And make it private so no one else can get to it.Corey: Or you could use local files: copy-of-copy-of-this-thing-restored-parentheses-use-this-one-dot-final-dot-doc-dot-zip. You know, my preferred naming convention.Chris: Ah, yeah. Wow. Okay. [laugh]. Yeah.Corey: Everything I touch is terrifying.Chris: Yes. Geez, I'm sorry. So first, it's declarative. You declare your state. You store it somewhere. It's versioned and immutable, like I said. And then pulled automatically—don't focus so much on pull—but basically, software agents are applying the desired state from source. So, what does that mean? When it's—you know, the fourth principle is implemented, continuously reconciled. That means those software agents that are checking your desired state are actually putting it back into the desired state if it's out of whack, right? So—Corey: You're talking about agents running it persistently on instances, validating—Chris: Yes.Corey: —a checkpoint on a cron. How is this meaningfully different than a Puppet agent running in years past? Having spent I learned to speak publicly by being a traveling trainer for Puppet; same type of model, and in fact, when I was at Pinterest, we wound up having a fair bit—like, that was their entire model, where they would have—the Puppet's code would live in an S3 bucket that was then copied down, I believe, via Git, and then applied to the instance on a schedule. Like, that sounds like this was sort of a early days GitOps.Chris: Yeah, exactly. Right? Like so it's, I like to think of that as a component of GitOps, right? DevOps, when you talk about DevOps in general, there's a lot of stuff out there. There's a lot of things labeled DevOps that maybe are, or maybe aren't sticking to some of those DevOps core things that make you great.Like the stuff that Nicole Forsgren writes about in books, you know? Accelerate is on my desk for a reason because there's things that good, well-managed DevOps practices do. I see GitOps as an actual implementation of DevOps in an open-source manner because all the tooling for GitOps these days is open-source and it all started as open-source. Now, you can get, like, Flux or Argo—Argo, specifically—there's managed services out there for it, you can have Flux and not maintain it, through an add-on, on EKS for example, and it will reconcile that state for you automatically. And the other thing I like to say about GitOps, specifically, is that it moves at the speed of the Kubernetes Audit Log.If you've ever looked at a Kubernetes audit log, you know it's rather noisy with all these groups and versions and kinds getting thrown out there. So, GitOps will say, “Oh, there's an event for said thing that I'm supposed to be watching. Do I need to change anything? Yes or no? Yes? Okay, go.”And the change gets applied, or, “Hey, there's a new Git thing. Pull it in. A change has happened inGit I need to update it.” You can set it to reconcile on events on time. It's like a cron or it's like an event-driven architecture, but it's combined.Corey: How does it survive the stake through the heart of configuration management? Because before I was doing all this, I wasn't even a T-shaped engineer: you're broad across a bunch of things, but deep in one or two areas, and one of mine was configuration management. I wrote part of SaltStack, once upon a time—Chris: Oh.Corey: —due to a bunch of very strange coincidences all hitting it once, like, I taught people how to use Puppet. But containers ultimately arose and the idea of immutable infrastructure became a thing. And these days when we were doing full-on serverless, well, great, I just wind up deploying a new code bundle to the Lambdas function that I wind up caring about, and that is a immutable version replacement. There is no drift because there is no way to log in and change those things other than through a clear deployment of this as the new version that goes out there. Where does GitOps fit into that imagined pattern?Chris: So, configuration management becomes part of your approval process, right? So, you now are generating an audit log, essentially, of all changes to your system through the approval process that you set up as part of your, how you get things into source and then promote that out to production. That's kind of the beauty of it, right? Like, that's why we suggest using Git because it has functions, like, requests and issues and things like that you can say, “Hey, yes, I approve this,” or, “Hey, no, I don't approve that. We need changes.” So, that's kind of natively happening with Git and, you know, GitLab, GitHub, whatever implementation of Git. There's always, kind of—Corey: Uh, JIF-ub is, I believe, the pronunciation.Chris: JIF-ub? Oh.Corey: Yeah. That's what I'm—Chris: Today, I learned. Okay.Corey: Exactly. And that's one of the things that I do for my lasttweetinaws.com Twitter client that I build—because I needed it, and if other people want to use it, that's great—that is now deployed to 20 different AWS commercial regions, simultaneously. And that is done via—because it turns out that that's a very long to execute for loop if you start down that path—Chris: Well, yeah.Corey: I wound up building out a GitHub Actions matrix—sorry a JIF-ub—actions matrix job that winds up instantiating 20 parallel builds of the CDK deploy that goes out to each region as expected. And because that gets really expensive with native GitHub Actions runners for, like, 36 cents per deploy, and I don't know how to test my own code, so every time I have a typo, that's another quarter in the jar. Cool, but that was annoying for me so I built my own custom runner system that uses Lambda functions as runners running containers pulled from ECR that, oh, it just runs in parallel, less than three minutes. Every time I commit something between I press the push button and it is out and running in the wild across all regions. Which is awesome and also terrifying because, as previously mentioned, I don't know how to test my code.Chris: Yeah. So, you don't know what you're deploying to 20 regions sometime, right?Corey: But it also means I have a pristine, re-composable build environment because I can—Chris: Right.Corey: Just automatically have that go out and the fact that I am making a—either merging a pull request or doing a direct push because I consider main to be my feature branch as whenever something hits that, all the automation kicks off. That was something that I found to be transformative as far as a way of thinking about this because I was very tired of having to tweak my local laptop environment to, “Oh, you didn't assume the proper role and everything failed again and you broke it. Good job.” It wound up being something where I could start developing on more and more disparate platforms. And it finally is what got me away from my old development model of everything I build is on an EC2 instance, and that means that my editor of choice was Vim. I use the VS Code now for these things, and I'm pretty happy with it.Chris: Yeah. So, you know, I'm glad you brought up CDK. CDK gives you a lot of the capabilities to implement GitOps in a way that you could say, like, “Hey, use CDK to declare I need four Amazon EKS clusters with this size, shape, and configuration. Go.” Or even further, connect to these EKS clusters to RDS instances and load balancers and everything else.But you put that state into Git and then you have something that deploys that automatically upon changes. That is infrastructure as code. Now, when you say, “Okay, main is your feature branch,” you know, things happen on main, if this were running in Kubernetes across a fleet of clusters or the globe-wide in 20 regions, something like Flux or Argo would kick in and say, “There's been a change to source, main, and we need to roll this out.” And it'll start applying those changes. Now, what do you get with GitOps that you don't get with your configuration?I mean, can you rollback if you ever have, like, a bad commit that's just awful? I mean, that's really part of the process with GitOps is to make sure that you can, A, roll back to the previous good state, B, roll forward to a known good state, or C, promote that state up through various environments. And then having that all done declaratively, automatically, and immutably, and versioned with an audit log, that I think is the real power of GitOps in the sense that, like, oh, so-and-so approve this change to security policy XYZ on this date at this time. And that to an auditor, you just hand them a log file on, like, “Here's everything we've ever done to our system. Done.” Right?Like, you could get to that state, if you want to, which I think is kind of the idea of DevOps, which says, “Take all these disparate tools and processes and procedures and culture changes”—culture being the hardest part to adopt in DevOps; GitOps kind of forces a culture change where, like, you can't do a CAB with GitOps. Like, those two things don't fly. You don't have a configuration management database unless you absolutely—Corey: Oh, you CAB now but they're all the comments of the pull request.Chris: Right. Exactly. Like, don't push this change out until Thursday after this other thing has happened, kind of thing. Yeah, like, that all happens in GitHub. But it's very democratizing in the sense that people don't have to waste time in an hour-long meeting to get their five minutes in, right?Corey: DoorDash had a problem. As their cloud-native environment scaled and developers delivered new features, their monitoring system kept breaking down. In an organization where data is used to make better decisions about technology and about the business, losing observability means the entire company loses their competitive edge. With Chronosphere, DoorDash is no longer losing visibility into their applications suite. The key? Chronosphere is an open-source compatible, scalable, and reliable observability solution that gives the observability lead at DoorDash business, confidence, and peace of mind. Read the full success story at snark.cloud/chronosphere. That's snark.cloud slash C-H-R-O-N-O-S-P-H-E-R-E.Corey: So, would it be overwhelmingly cynical to suggest that GitOps is the means to implement what we've all been pretending to have implemented for the last decade when giving talks at conferences?Chris: Ehh, I wouldn't go that far. I would say that GitOps is an excellent way to implement the things you've been talking about at all these conferences for all these years. But keep in mind, the technology has changed a lot in the, what 11, 12 years of the existence of DevOps, now. I mean, we've gone from, let's try to manage whole servers immutably to, “Oh, now we just need to maintain an orchestration platform and run containers.” That whole compute interface, you go from SSH to a Docker file, that's a big leap, right?Like, you don't have bespoke sysadmins; you have, like, a platform team. You don't have DevOps engineers; they're part of that platform team, or DevOps teams, right? Like, which was kind of antithetical to the whole idea of DevOps to have a DevOps team. You know, everybody's kind of in the same boat now, where we see skill sets kind of changing. And GitOps and Kubernetes-land is, like, a platform team that manages the cluster, and its state, and health and, you know, production essentially.And then you have your developers deploying what they want to deploy in when whatever namespace they've been given access to and whatever rights they have. So, now you have the potential for one set of people—the platform team—to use one set of GitOps tooling, and your applications teams might not like that, and that's fine. They can have their own namespaces with their own tooling in it. Like, Argo, for example, is preferred by a lot of developers because it has a nice UI with green and red dots and they can show people and it looks nice, Flux, it's command line based. And there are some projects out there that kind of take the UI of Argo and try to run Flux underneath that, and those are cool kind of projects, I think, in my mind, but in general, right, I think GitOps gives you the choice that we missed somewhat in DevOps implementations of the past because it was, “Oh, we need to go get cloud.” “Well, you can only use this cloud.” “Oh, we need to go get this thing.” “Well, you can only use this thing in-house.”And you know, there's a lot of restrictions sometimes placed on what you can use in your environment. Well, if your environment is Kubernetes, how do you restrict what you can run, right? Like you can't have an easily configured say, no open-source policy if you're running Kubernetes. [laugh] so it becomes, you know—Corey: Well, that doesn't stop some companies from trying.Chris: Yeah, that's true. But the idea of, like, enabling your developers to deploy at will and then promote their changes as they see fit is really the dream of DevOps, right? Like, same with production and platform teams, right? I want to push my changes out to a larger system that is across the globe. How do I do that? How do I manage that? How do I make sure everything's consistent?GitOps gives you those ways, with Kubernetes native things like customizations, to make consistent environments that are robust and actually going to be reconciled automatically if someone breaks the glass and says, “Oh, I need to run this container immediately.” Well, that's going to create problems because it's deviated from state and it's just that one region, so we'll put it back into state.Corey: It'll be dueling banjos, at some point. You'll try and doing something manually, it gets reverted automatically. I love that pattern. You'll get bored before the computer does, always.Chris: Yeah. And GitOps is very new, right? When you think about the lifetime of GitOps, I think it was coined in, like, 2018. So, it's only four years old, right? When—Corey: I prefer it to ChatOps, at least, as far as—Chris: Well, I mean—Corey: —implementation and expression of the thing.Chris: —ChatOps was a way to do DevOps. I think GitOps—Corey: Well, ChatOps is also a way to wind up giving whoever gets access to your Slack workspace root in production.Chris: Mmm.Corey: But that's neither here nor there.Chris: Mm-hm.Corey: It's yeah, we all like to pretend that's not a giant security issue in our industry, but that's a topic for another time.Chris: Yeah. And that's why, like, GitOps also depends upon you having good security, you know, and good authorization and approval processes. It enforces that upon—Corey: Yeah, who doesn't have one of those?Chris: Yeah. If it's a sole operation kind of deal, like in your setup, your case, I think you kind of got it doing right, right? Like, as far as GitOps goes—Corey: Oh, to be clear, we are 11 people and we do have dueling pull requests and all the rest.Chris: Right, right, right.Corey: But most of the stuff I talk about publicly is not our production stuff, so it really is just me. Just as a point of clarity there. I've n—the 11 people here do not all—the rest of you don't just sit there and clap as I do all the work.Chris: Right.Corey: Most days.Chris: No, I'm sure they don't. I'm almost certain they don't clap… for you. I mean, they would—Corey: No. No, they try and talk me out of it in almost every case.Chris: Yeah, exactly. So, the setup that you, Corey Quinn, have implemented to deploy these 20 regions is kind of very GitOps-y, in the sense that when main changes, it gets updated. Where it's not GitOps-y is what if the endpoint changes? Does it get reconciled? That's the piece you're probably missing is that continuous reconciliation component, where it's constantly checking and saying, “This thing out there is deployed in the way I want it. You know, the way I declared it to be in my source of truth.”Corey: Yeah, when you start having other people getting involved, there can—yeah, that's where regressions enter. And it's like, “Well, I know where things are so why would I change the endpoint?” Yeah, it turns out, not everyone has the state of the entire application in their head. Ideally it should live in—Chris: Yeah. Right. And, you know—Corey: —you know, Git or S3.Chris: —when I—yeah, exactly. When I think about interactions of the past coming out as a new DevOps engineer to work with developers, it's always been, will developers have access to prod or they don't? And if you're in that environment with—you're trying to run a multi-billion dollar operation, and your devs have direct—or one Dev has direct access to prod because prod is in his brain, that's where it's like, well, now wait a minute. Prod doesn't have to be only in your brain. You can put that in the codebase and now we know what is in your brain, right?Like, you can almost do—if you document your code, well, you can have your full lifecycle right there in one place, including documentation, which I think is the best part, too. So, you know, it encourages approval processes and automation over this one person has an entire state of the system in their head; they have to go in and fix it. And what if they're not on call, or in Jamaica, or on a cruise ship somewhere kind of thing? Things get difficult. Like, for example, I just got back from vacation. We were so far off the grid, we had satellite internet. And let me tell you, it was hard to write an email newsletter where I usually open 50 to 100 tabs.Corey: There's a little bit of internet out Californ-ie way.Chris: [laugh].Corey: Yeah it's… it's always weird going from, like, especially after pandemic; I have gigabit symmetric here and going even to re:Invent where I'm trying to upload a bunch of video and whatnot.Chris: Yeah. Oh wow.Corey: And the conference WiFi was doing its thing, and well, Verizon 5G was there but spotty. And well, yeah. Usual stuff.Chris: Yeah. It's amazing to me how connectivity has become so ubiquitous.Corey: To the point where when it's not there anymore, it's what do I do with myself? Same story about people pushing back against remote development of, “Oh, I'm just going to do it all on my laptop because what happens if I'm on a plane?” It's, yeah, the year before the pandemic, I flew 140,000 miles domestically and I was almost never hamstrung by my ability to do work. And my only local computer is an iPad for those things. So, it turns out that is less of a real world concern for most folks.Chris: Yeah I actually ordered the components to upgrade an old Nook that I have here and turn it into my, like, this is my remote code server, that's going to be all attached to GitHub and everything else. That's where I want to be: have Tailscale and just VPN into this box.Corey: Tailscale is transformative.Chris: Yes. Tailscale will change your life. That's just my personal opinion.Corey: Yep.Chris: That's not an AWS opinion or anything. But yeah, when you start thinking about your network as it could be anywhere, that's where Tailscale, like, really shines. So—Corey: Tailscale makes the internet work like we all wanted to believe that it worked.Chris: Yeah. And Wireguard is an excellent open-source project. And Tailscale consumes that and puts an amazingly easy-to-use UI, and troubleshooting tools, and routing, and all kinds of forwarding capabilities, and makes it kind of easy, which is really, really, really kind of awesome. And Tailscale and Kubernetes—Corey: Yeah, ‘network' and ‘easy' don't belong in the same sentence, but in this case, they do.Chris: Yeah. And trust me, the Kubernetes story in Tailscale, there is a lot of there. I understand you might want to not open ports in your VPC, maybe, but if you use Tailscale, that node is just another thing on your network. You can connect to that and see what's going on. Your management cluster is just another thing on the network where you can watch the state.But it's all—you're connected to it continuously through Tailscale. Or, you know, it's a much lighter weight, kind of meshy VPN, I would say, if I had to sum it up in one sentence. That was not on our agenda to talk about at all. Anyways. [laugh]Corey: No, no. I love how many different topics we talk about on these things. We'll have to have you back soon to talk again. I really want to thank you for being so generous with your time. If people want to learn more about what you're up to and how you view these things, where can they find you?Chris: Go to ChrisShort.net. So, Chris Short—I'm six-four so remember, it's Short—dot net, and you will find all the places that I write, you can go to devopsish.com to subscribe to my newsletter, which goes out every week. This year. Next year, there'll be breaks. And then finally, if you want to follow me on Twitter, Chris Short: at @ChrisShort on Twitter. All one word so you see two s's. Like, it's okay, there's two s's there.Corey: Links to all of that will of course be in the show notes. It's easier for people to do the clicky-clicky thing as a general rule.Chris: Clicky things are easier than the wordy things, yes.Corey: Says the Kubernetes guy.Chris: Yeah. Says the Kubernetes guy. Yeah, you like that, huh? Like I said, Argo gives you a UI. [laugh].Corey: Thank you [laugh] so much for your time. I really do appreciate it.Chris: Thank you. This has been fun. If folks have questions, feel free to reach out. Like, I am not one of those people that hides behind a screen all day and doesn't respond. I will respond to you eventually.Corey: I'm right here, Chris. Come on, come on. You're calling me out in front of myself. My God.Chris: Egh. It might take a day or two, but I will respond. I promise.Corey: Thanks again for your time. This has been Chris Short, senior developer advocate at AWS. I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice and if it's YouTube, click the thumbs-up button. Whereas if you've hated this podcast, same thing, smash the buttons five-star review and leave an insulting comment that is written in syntactically correct YAML because it's just so easy to do.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

We conclude our two-part conversation with Weaveworks co-founder Alexis Richardson, picking up when the company received Series A investment in December 2014. Since then, they built projects like Scope, Cortex and Flux as well as SaaS offerings based on them. We also look at Alexis’s role in the founding of the CNCF. Please be sure to listen to the first part before this one! Do you have something cool to share? Some questions? Let us know: web: kubernetespodcast.com mail: kubernetespodcast@google.com twitter: @kubernetespod Chatter of the week Educational YouTubers: Film Riot Mental Floss Animator Island Infrastructure for Entertainment by Justin Garrison at KubeCon NA 2020 Episode 20, with Justin Garrison News of the week Kubernetes 1.21 PodSecurityPolicy deprecation KubeVela 1.0 Argo Workflows 3.0 and Argo CD 2.0 Cilium launches NetworkPolicy site IBM Cloud Code Engine is GA Tanzu Cloud Native Runtimes public beta New security offerings from Tanzu Cisco Intersight Kubernetes Service is GA Tetrate Service Bridge is also GA Updates to Azure Arc enabled Kubernetes and OpenServiceMesh add-on for Azure in Preview etcd project journey report published Single sign-on guide for Kubernetes by Ben Dixon Apache Mesos moving to the Attic Links from the interview Last week’s episode Weaveworks Weaveworks takes a $5m Series A round Weave Scope and its annoucement Cortex Flux CD and its announcement as a service routing layer Weave Cloud Docker Swarm Mode kubernetes-anywhere kubeadm How we made kubeadm Brandon Philips’ newsletter Launching eksctl The August 2017 post introducing GitOps Peter Bourgon and Michael Bridgen Kelsey Hightower talk at GitOpsDays Guide to GitOps Steam engine centrifugal governor Flux joins the CNCF Flagger Announcement about Argo and Flux joining forces Weaveworks is a founding member of the CNCF Alexis elected as TOC chair Battlestar Galactica Weave Kubernetes Platform Series C funding Alexis Richardson on Twitter

Today's Full Stack Journey podcast explores AWS Controllers for Kubernetes (ACK). Currently available as a developer preview, the ACK project lets customers manage their AWS services directly from Kubernetes. Our guide to ACK is Justin Garrison, a container advocate at AWS and author.

Today's Full Stack Journey podcast explores AWS Controllers for Kubernetes (ACK). Currently available as a developer preview, the ACK project lets customers manage their AWS services directly from Kubernetes. Our guide to ACK is Justin Garrison, a container advocate at AWS and author.

Today's Full Stack Journey podcast explores AWS Controllers for Kubernetes (ACK). Currently available as a developer preview, the ACK project lets customers manage their AWS services directly from Kubernetes. Our guide to ACK is Justin Garrison, a container advocate at AWS and author. The post Full Stack Journey 046: Understanding AWS Controllers For Kubernetes (ACK) appeared first on Packet Pushers.

Today's Full Stack Journey podcast explores AWS Controllers for Kubernetes (ACK). Currently available as a developer preview, the ACK project lets customers manage their AWS services directly from Kubernetes. Our guide to ACK is Justin Garrison, a container advocate at AWS and author. The post Full Stack Journey 046: Understanding AWS Controllers For Kubernetes (ACK) appeared first on Packet Pushers.

En esta ocasión David Gómez, gerente y miembro fundador de IAS Software será quien dirija la conversación. Nuestro invitado en esta oportunidad es David Montoya, ingeniero de sistemas del politécnico Jaime Isaza Cadavid. Trabajó en IAS Software como desarrollador de plataformas web, posterior fue desarrollador en McCamish Systems, Bridge2 solutions en procesos de elaboración de código. Así mismo, fue consultor en Thought Works, una de las grandes consultoras de software en todo el mundo y actualmente es ingeniero de resiliencia en Expel, una startup radicada en EE.UU y enfocada en procesos de seguridad digital. En este episodio David nos habla sobre cultura empresarial alrededor del software, procesos de Devops, adopción de nube y cómo han cambiado los paradigmas de elaboración de software en los años, así como su experiencia técnica, Y cultural de trabajar en una empresa extranjera. David nos comparte algunos recursos que publicamos a continuación: Notas del episodio Expel: https://expel.io/ ThoughtWorks: https://www.thoughtworks.com/ Radical Candor, Kim Scott: https://www.radicalcandor.com/ Accelerate: Building and Scaling High-Performing Technology Organizations,Nicole Forsgren: https://www.goodreads.com/book/show/35747076-accelerate Building microservices, Sam Newman: https://www.amazon.com/-/es/Sam-Newman/dp/1491950358 The phenix project, Gene Kim: https://www.amazon.com/-/es/Gene-Kim/dp/0988262592 Pragmatic programmer, Andrew Hunt: https://www.amazon.com/-/es/Andrew-Hunt/dp/020161622X Cloud Native infraestructure, Justin Garrison: https://www.oreilly.com/library/view/cloud-native-infrastructure/9781491984291/ David Montoya: https://www.linkedin.com/in/davidmontoyago/ Ilustración de portada hecha por Santiago Valencia - IG:Santiago109 --- Send in a voice message: https://anchor.fm/ias-lab-podcast/message

Contributing editor Mark Bauerlein is joined by Justin Garrison and Ryan Holston, the editors of “The Historical Mind: Humanistic Renewal in a Post-Constitutional Age.”

This is a special episode, with me I had Andre Almar and we had the honor to interview Justin Garrison and talk a lot about Cloud Native, Immutable infrastructure and much more.Questions:We have been talking about and implementing Cloud Native Infrastructure for some time, an immutable part of the infrastructure and a game changer in my opinion. What’s the core of Cloud Native Infrastructure, in your opinion?What is the importance to distinguish between “infrastructure as code” and “infrastructure as software”?What do you think about immutable infrastructure point-to-point, when you run IAAS, K8s, Docker etc.It is feasible to think that we can achieve Cloud Native Infrastructure in On-Premises environments? If so, how to do that?Our architecture increasingly becomes more complicated and we always need more. What do you think about the cloud SAAS offers ?I’ve seen more and more people saying that they are adopting Cloud Native Architecture and microservices. What is the weakest spot, or the security point, that everyone should double check?I’m already running a Cloud Native Infrastructure with Cloud Native apps deployed on it. What are the next steps? I mean in terms of evolution of my Cloud Native stack.How hard it was to write the Cloud Native Infrastructure Book?For the recommendations of the week we have:André: Cloud Native Infrastructure (by Justin Garrison, Kris Nova)Justin: Understand the basics, how an ip address and all the network layers works.João: Relax with Sharknado!That’s all folks, don’t forget to share! #kubicastAvailable on your favorite player: Spotify, Overcast, Itunes ou RadioPublic.

In this episode of The New Stack Makers, we talk to Nóva, chief open source advocate at Sysdig, about the progression of the open source world and her perspective examining it through the lens of San Francisco's COVID-19 lockdown. She calls the book she wrote with Justin Garrison a kind of thesis that looks to predict the infrastructural patterns that could solve a lot of the challenges cloud-native infrastructure teams face.

This week Coté interviews Justin Garrison coauthor of Cloud Native Infrastructure (https://www.cnibook.info/). They discuss all things "Cloud Native" and what it's like to be a software engineer who helps make movies. Photo by David Brooke Martin on Unsplash (https://unsplash.com/photos/dxtEFmAfkOk) Special Guest: Justin Garrison .

Mozilla speeds up its open source speech-to-text engine, Disney+ is now available on Linux, and Amazon has a new AI-powered service for automated code review.

Speaking of nachos, more earnings this week. Plus, identity theft. There’s a clutch of data breaches this week and Coté finally learns why this is bad. Also, monitoring company IPOs, nachos, and the eating management and the terrors of European fry condiment management. Buy Coté’s book dirt cheap (https://leanpub.com/digitalwtf/c/sdt)! And check out his other book that this guy likes (https://www.linkedin.com/feed/update/urn:li:activity:6559881947412340736/). Moodboard: I’m making my way to the microphone. The only way I know how. We need to start a YouTube channel where we do webinar reactions. We got some cool stuff to talk about with this latest breach. I just wanted a meal and now I have a problem to solve. I think I have some swamp stuff in Europe for the geographic oddity section. That’s my problem, I don’t like fun. Back to nachos The nacho of nachos Speaking of nachos, more earnings this week. The nonsense was the logs, not the log reader. Unnonsense your nonsense. Cause lawyers get paid. No time for the infinite scrolling ban. He had an affinity for green glass. Relevant to your interests All about Pivotal stuff on kubernetes (https://soundcloud.com/pivotalconversations/pas-pksand-rabbitmq-on-kubernetes) - Richard and Coté discuss it on this week’s Pivotal Conversations episode. The inevitability of K8s: Pivotal CEO describes the pain and benefits of technology transition (https://www.theregister.co.uk/2019/07/29/the_inevitability_of_kubernetes_pivotal_ceo_describes_the_pain_and_the_benefit_of_technology_transition/) Apple Acquiring the Majority of Intel's Smartphone Modem Business (https://www.macrumors.com/2019/07/25/apple-intel-acquisition/) Google Cloud's annual revenue run rate disclosure adds color to cloud race | ZDNet (https://www.zdnet.com/article/google-clouds-annual-revenue-run-rate-disclosure-adds-color-to-cloud-race/) Google Cloud to run VMware Cloud Foundation workloads (https://www.datacenterdynamics.com/news/google-cloud-run-vmware-cloud-foundation--workloads/) Google debuts migration tool for its Anthos hybrid cloud platform (https://siliconangle.com/2019/07/30/google-debuts-migration-tool-anthos-hybrid-cloud-platform/) Google teams up with VMware to bring more enterprises to its cloud (https://techcrunch.com/2019/07/29/google-teams-up-with-vmware-to-bring-more-enterprise-customers-to-its-cloud/) Oracle has quietly altered course on the way it sells its 'private-cloud' product, a key area of its cloud-computing strategy (https://www.businessinsider.com/oracle-cloud-private-sales-change-2019-7) Google Cloud’s run rate is now over $8B (https://techcrunch.com/2019/07/25/google-clouds-run-rate-is-now-over-8b/) Amazon reports $63.4 billion in Q2 2019 revenue: AWS up 37%, subscriptions up 37%, and ‘other’ up 37% (https://venturebeat.com/2019/07/25/amazon-earnings-q2-2019/) Microsoft reports $33.7 billion in Q4 2019 revenue: Azure up 64%, Surface up 14%, and LinkedIn up 25% (https://venturebeat.com/2019/07/18/microsoft-earnings-q4-2019/) Why Zoom Is the Best Videoconferencing Service (https://thewirecutter.com/reviews/best-video-conferencing-service/) URGENT/11 VxWorks RTOS Vulnerabilities Found, Critical Systems Affected (https://www.bleepingcomputer.com/news/security/urgent-11-vxworks-rtos-vulnerabilities-found-critical-systems-affected/) GitHub restricts developer accounts based in Iran, Crimea, and other countries under US sanctions (https://www.theverge.com/2019/7/29/8934694/github-us-trade-sanctions-developers-restricted-crimea-cuba-iran-north-korea-syria) Write like an Amazanion (https://pbs.twimg.com/media/EAXt9B0U4AIrRzJ.jpg) A former Amazon employee hacked the credit card data of 100 million Americans (https://www.vox.com/recode/2019/7/30/20747163/capital-one-data-hack-100-million-americans-new-york-investigation) Amazon refuses blame for massive Capital One data breach, says its cloud services were "not compromised in any way" (https://www.newsweek.com/amazon-capital-one-hack-data-leak-breach-paige-thompson-cybercrime-1451665) FTC warns Equifax claimants will get 'nowhere near' $125 cash payout (https://www.engadget.com/2019/08/01/ftc-equifax-claimants-choose-credit-monitoring/) Microsoft will drop Skype for Business Online on July 31, 2021 | ZDNet (https://www.zdnet.com/article/microsoft-will-drop-skype-for-business-online-on-july-31-2021/) Proposed US law would ban infinite scroll, autoplaying video (https://arstechnica.com/tech-policy/2019/07/proposed-us-law-would-ban-infinite-scroll-autoplaying-video/#p3) Should your B2B brand create social media stories? (https://diginomica.com/should-your-b2b-brand-create-social-media-stories) Datadog IPO: Cloud-based Monitoring's Next Move? - ChannelE2E (https://www.channele2e.com/investors/datadog-ipo-preparation/) Dynatrace Prices IPO Above Range At $16/Share, Valuing The Software Company At $4.5B (https://news.crunchbase.com/news/dynatrace-prices-ipo-above-range-at-16-share-valuing-the-software-company-at-4-5b/) IBM Fired as Many as 100,000 in Recent Years, Lawsuit Shows (https://www.bloomberg.com/news/articles/2019-07-31/ibm-fired-as-many-as-100-000-in-recent-years-court-case-shows) Nonsense Our Favorite Laptop Backpacks for 2019 (https://thewirecutter.com/reviews/our-favorite-laptop-backpacks/) This is a black and white photograph. Only the lines have colour. (https://twitter.com/page_eco/status/1155077311399489536?s=21) Contact Lenses That Can Change Focus and Zoom When You Blink Move Closer to Reality (https://gizmodo.com/contact-lenses-that-can-change-focus-and-zoom-when-you-1836789660) Technician keeps computer made in 1959 still humming along：The Asahi Shimbun (http://www.asahi.com/ajw/articles/AJ201907280007.html) Cel (https://twitter.com/hist/status/1154898478838870016?s=12)s (https://twitter.com/hist/status/1154898478838870016?s=12)ius vs.Fahrenheit (https://twitter.com/hist/status/1154898478838870016?s=12) Get real good-like at talking English (https://www.youtube.com/playlist?list=PLD_5T89Ssbn3F830QF2h_xoJJdbteSeg7). Will Matt Ray give an Emacs keynote? (https://emacsconf.org/2019/) Sponsors Solarwinds Loggly (https://loggly.com/sdt): https://www.loggly.com/sdt TrackJS (http://TrackJS.com/sdt) — https://trackjs.com/sdt/ Conferences, et. al. August 30th - Agile Scotland, Glasgow (https://www.agilescotland.com/august) - Coté giving 90 minute workshop (https://www.agilescotland.com/august#comp-jwjlafj0__item1inlineContent-gridWrapper). Use the code AS-SPEAKER-MICHAEL for a discount: from £70 to £56.13. Oct 7th to 10th - SpringOne Platform, Oct 7th to 10th, Austin Texas (https://springoneplatform.io/) - get $200 off registration before August 20th. Come to the EMEA party (https://connect.pivotal.io/EMEA-Cocktail-Reception-S1P-2019.html) if you’re in EMEA. Oct 9th to 10th - Cloud Expo Asia (https://www.cloudexpoasia.com/) Singapore, Oct 9th and 10th Oct 10th to 11th - DevOpsDays Sydney 2019 (http://devopsdays.org/events/2019-sydney/), October 10th and 11th Kubeyland 2019 (https://docs.google.com/forms/d/e/1FAIpQLSevM4mDeM_P1spKbz7gysMSNm_ONRpiNN60ifg-Gi4avmJ9pg/viewform) via Justin Garrison (https://twitter.com/rothgar/status/1155930353250385920?s=21) December - 2019, a city near you: The 2019 SpringOne Tours are posted (http://springonetour.io/): Toronto Dec 2nd and 3rd (https://springonetour.io/2019/toronto), São Paulo Dec 11th and 12th (https://springonetour.io/2019/sao-paulo). December 12-13 2019 - Kubernetes Summit Sydney (https://events.linuxfoundation.org/events/kubernetes-summit-sydney-2019/) Follow-up Italy had a swamps that were drained (https://en.wikipedia.org/wiki/Pontine_Marshes): “The road proved difficult to keep above water. Under Augustus, a compromise was reached with the construction of a parallel canal. The part of the marsh above sea level was successfully drained by channels, and new agricultural land of legendary fertility came into being. Whenever the channels were not maintained, the swamp reappeared. Meanwhile, frequent epidemics of malaria at Rome and elsewhere kept the reclamation issue alive. Under Benito Mussolini's regime in the 1930s, the problem was nearly solved by placing dikes and pumping out that portion of the marsh below sea level. It continues to need constant maintenance. Italian confidence in the project was so high, the city placed by Mussolini in 1932 in the center of the marsh, Latina, became the capital of a new province, Latina.” There were German colonies (https://en.m.wikipedia.org/wiki/German_colonial_empire) - mostly in Africa. SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us on Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/) or LinkedIn (https://www.linkedin.com/company/software-defined-talk/) Listen to the Software Defined Interviews Podcast (https://www.softwaredefinedinterviews.com/). Check out the back catalog (http://cote.coffee/howtotech/). Brandon built the Quick Concall iPhone App (https://itunes.apple.com/us/app/quick-concall/id1399948033?mt=8) and he wants you to buy it for $0.99. Use the code SDT to get $20 off Coté’s book, (https://leanpub.com/digitalwtf/c/sdt) Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Recommendations Brandon: Running from Cops (https://podcasts.apple.com/us/podcast/running-from-cops-headlong-season-3/id1459118695). Matt: Stories from the Frontlines of Synthetic Fraud (https://a16z.com/2019/06/25/a16z-podcast-stories-from-the-frontlines-of-synthetic-fraud/) Coté: Grolsch Blond (https://www.grolsch.nl/proeverij/grolsch-blond.html); Freak Kingdom (https://amzn.to/317Aj4t) and The Gonzo Tapes (https://www.youtube.com/watch?v=QE-aDdbllcI). Outro: T (https://www.youtube.com/watch?v=tDfZ5HmA6fs)he Usual Suspects (https://www.youtube.com/watch?v=tDfZ5HmA6fs).

Justin Garrison is both a student and a teacher. A senior systems engineer in the media industry, he has boiled his experience and wisdom, as well as that of his co-author Kris Nova, into the book Cloud Native Infrastructure. He talks to Craig and Adam about the Kubernetes community and the process of writing. Do you have something cool to share? Some questions? Let us know: web: kubernetespodcast.com mail: kubernetespodcast@google.com twitter: @kubernetespod Chatter KubeCon NA ‘17 keynote: Your Philips Hue Light Bulbs Are Turned On By Kubernetes by Mark van Straten Philips Lighting case study on Google Cloud News of the week Cisco Hybrid Cloud Platform for Google Cloud is now generally available Enter the Cisco & Google Cloud Challenge! Win things! Consul + Kubernetes from Hashicorp Open Match announced by Google Cloud and Unity Agones 0.4.0 released Couchbase Autonomous Operator Amazon EKS now available in Ireland Google Cloud now available in Finland Platform9 introduces spot instance arbitrage External DNS 0.5.6 released Red Hat on Kubernetes and application servers Links from the interview mintCast, which featured Justin a long time ago Cloud Native Infrastructure book: website and O’Reilly The Economics of Writing a Technical Book Justin’s last KubeCon talk: Let’s Build Kubernetes, With a Spreadsheet and Volunteers! Justin Garrison on Twitter and GitHub Dashiell, rothgar/v2 Justin’s blog

On today’s Datanauts episode, we talk to Justin Garrison, a senior systems engineer, about managing cloud native applications. We cover the challenges of managing a microservices architecture, sidecars, troubleshooting and more The post Datanauts 141: Managing Cloud-Native Applications appeared first on Packet Pushers.

On today’s Datanauts episode, we talk to Justin Garrison, a senior systems engineer, about managing cloud native applications. We cover the challenges of managing a microservices architecture, sidecars, troubleshooting and more The post Datanauts 141: Managing Cloud-Native Applications appeared first on Packet Pushers.

On today’s Datanauts episode, we talk to Justin Garrison, a senior systems engineer, about managing cloud native applications. We cover the challenges of managing a microservices architecture, sidecars, troubleshooting and more The post Datanauts 141: Managing Cloud-Native Applications appeared first on Packet Pushers.

Paris Pittman and Garrett Rodrigues join Mark and Melanie to discuss the Contributor Experience on Kubernetes, and how people can get involved with Kubernetes! Paris Pittman Co-Chair of Contributor Experience Special Interest Group for Kubernetes. Bay Area Kubernetes Meetup Co-Organizer Paris is a Developer Relations Program Manager on the Google Cloud Open Source Strategy team focusing on Kubernetes Community. She has 13 years of professional experience in attracting, retaining, growing, and incentivizing engineering talent for organizations and open source projects. She has also been organizing communities in one form or another for over 20 years, and at one point ran enough hackathons and meetups to subsist solely on the free pizza leftovers. Garrett Rodrigues Technical Lead of the Contributor Experience SIG for Kubernetes. Garrett is a Technical Program Manager at Google, and he joined the Kubernetes and GKE Team at Google in June 2016. As a lead of ContribX, he has focused on scaling the Kubernetes project in a sustainable way. Garrett developed a lot of the tooling and automation to support OSS code review, issue triage, and data collection about the project. In addition to his work on Contributor Experience, Garrett is currently involved with the app-def working group to get a new declarative application management tool released. Cool things of the week Highlights from the TensorFlow Developer Summit, 2018 blog TensorFlow Hub site Announcing TensorRT integration with TensorFlow 1.7 blog Announcing Google Cloud Security Talks during RSA Conference 2018 blog Exploring container security: An overview blog How to run Windows Containers on Compute Engine blog Interview Kubernetes site github Kubernetes SIGs and Working Groups github Kubernetes Community Content github Kubernetes Contributor Guide github Kubernetes slack join! Kubernetes design proposals github Kubernetes Issues help wanted Kubernetes Contributor Summit site Kubernetes Weekly Community Meeting github Dev Statistics site Kubernetes Mentoring Initiatives github Question of the week If I need to temporarily increases the power of a Cloud Shell, how do I do that? Boost Mode docs Justin Garrison tweet Where can you find us next? Melanie will be speaking about AI at Techtonica on April 11th, and April 14th will be participating in a panel on Diversity and Inclusion at the Harker Research Symposium

In this week’s podcast, we speak with Justin Garrison, co-author of Cloud Native Infrastructure (CNI). • Behind scenes for O’Reilly book and choice of cover animal • Infrastructure and CNI approach • State and Immutability / Immutable VM • Terraform and Kubernetes • Observability • The Why of Immutability • Infrastructure as Software (Netflix) • Site Reliability Engineering and DevOps

Ready to learn a little more about Cloud Native? Justin Garrison wrote the book on the subject (literally!), so we thought he'd be a great person to talk about what cloud native is, which companies should and shouldn't try to go cloud native, and what to do if you want to get the whole cloud native thing right.

SPOILER ALERT: THIS PODCAST DISCUSSES SOME IMPORTANT PLOT ELEMENTS IN "A GAME OF THRONES." SO DON'T CUT OUR HEADS OFF! PLEASE! Is it possible to be both good and effective in politics? If you're a fan of Game of Thrones, you already know the answer to that one. To be a member of the prominent Stark family is to be both good and, most likely, dead. But is that necessarily true in the real world? This is a question of vital importance in any political system, including our constitutional republic. That's why Stewart (who loves Game of Thrones, by the way) recently sat down with Justin Garrison, a political scientist from Roanoke College in Virginia. It's a fascinating conversation, so bring your wits, and your sword!

Love him or hate him (and, either way, you have lots of company) Ronald Reagan was, and continues to be, an important figure in American constitutional history. We'll speak with Justin Garrison, a professor at Roanoke College in Virginia, who's written a balanced, fascinating, readable book called "An Empire of Ideals: the Chimeric Imagination of Ronald Reagan." Justin is that rare scholar who not only writes well, but also speaks well. He's even funny and charming - kinda like Ronald Reagan was. Justin's book is available here: http://www.amazon.com/Empire-Ideals-Imagination-Routledge-Governance/dp/0415818486.