just now

The One Where We Geek Out on Kubernetes with Kelsey Hightower

Adriana geeks out with the one and only Kelsey Hightower on Kubernetes, open source, and making tech accessible. Kelsey delves into Kubernetes' rise as an essential yet complex ecosystem, and shares his thoughts on where things might be headed. He switches gears a bit to talk about Kubernetes and Nomad: how they're similar and different, and how they benefit each other. The discussion also touches upon the significance of community engagement in open source projects, as Kelsey emphasizes the responsibilities of contributors and maintainers amidst the constant evolution and monetization of open-source software. Finally, Kelsey talks about the importance of learning and making complex topics accessible, punctuated by his own commitment to demystifying Kubernetes and encouraging progress over perfection in the tech field.

Listen to this episode

0:00 / 0:00

Summary

Adriana geeks out with the one and only Kelsey Hightower on Kubernetes, open source, and making tech accessible. Kelsey delves into Kubernetes' rise as an essential yet complex ecosystem, and shares his thoughts on where things might be headed. He switches gears a bit to talk about Kubernetes and Nomad: how they're similar and different, and how they benefit each other. The discussion also touches upon the significance of community engagement in open source projects, as Kelsey emphasizes the responsibilities of contributors and maintainers amidst the constant evolution and monetization of open-source software. Finally, Kelsey talks about the importance of learning and making complex topics accessible, punctuated by his own commitment to demystifying Kubernetes and encouraging progress over perfection in the tech field.

First published

12/05/2023

Genres

technology

Tags

innovation journalism media critique future of communication in-depth interviews digital literacy disruptive media social change reporting

Duration

38 minutes

Parent Podcast

Geeking Out with Adriana Villela

View Podcast

Share this episode

Similar Episodes

  • The One Where We Geek Out at KubeHuddle on Mental Health

    05/08/2024

    geekingout@dzerolabs.io (Adriana Villela, Hannah Maxwell, Lian Li, Diana Pham, Marino Wijay, Tim Banks)

    It's a very special episode of Geeking Out! We were live at KubeHuddle on May 7th in Toronto, Canada for a mental health panel featuring host Adriana Villela, joined by Tim Banks, Lian Li, Diana Pham, and Marino Wijay. We discuss three key topics: 1. What are some of your indications that you or your co-workers are suffering? 2. How can we prioritize & take care of our mental health, while advocating for others to do the same? 3. What changes in the industry and our environments would be beneficial to mental health going forward? We close off with some audience questions!

    Explicit
  • The One Where We Geek Out on Learning with Hannah Maxwell

    09/03/2023

    geekingout@dzerolabs.io (Hannah Maxwell, Adriana Villela)

    About Hannah Maxwell:Hannah is a high school student living in Toronto, Canada. She’s also the daughter of OCMM co-host Adriana Villela. She loves showing off her artistic side, whether it’s through baking, sewing, painting, or knitting. You can see her creations on Instagram. Hannah has been bouldering since she was 3, and still enjoys going to the bouldering gym with her parents. Although both of her parents work in tech, Hannah would rather not spend her time sitting at a desk and staring at a computer all day. That’s why she’s planning on becoming a dentist when she grows up. Find our guest on:InstagramFind us on:All of our social channels are on bento.me/geekingoutAdriana’s TwitterAdriana’s MastodonAdriana’s LinkedInAdriana’s InstagramAdriana’s BlueskyTranscript:ADRIANA: Is this thing on?HANNAH: Is this thing on?ADRIANA: Is this thing on?HANNAH: Is this thing on?ADRIANA: Ready?HANNAH: YeahADRIANA: Hey Y'all. Welcome to Geeking Out, the podcast about all geeky aspects of software delivery, reliability, Observability,TOGETHER: And everything in between.HANNAH: I've heard this too many times.ADRIANA: I'm your host, Adriana Villela, and with me for our very first episode of Geeking Out, I have my wonderful daughter and producer and just know overall, all around wonderful person.HANNAH: I was going to say overall, just know your emotional support human. Actually, I think I cause you the opposite.ADRIANA: My emotional support human, Hannah, and this is the first episode of Geeking Out, and I'm super excited to be bringing you this episode. You know, if you were a fan of the On Call Me Maybe podcast, you know, it's sad that the podcast has come to a close, but we have started this podcast talking about similar subject matter to On Call Me Maybe. And this time it's been a treat because Hannah is helping me with production of this podcast, because she has mad video editing skills.HANNAH:I wouldn't say mad.ADRIANA: And as a teenager is very tapped into this Youtube sub-culture...HANNAH: I know the social media. I'm very self conscious of people walking by...ADRIANA: Because we're recording outside. This was Hannah's idea. It's kind of nice. I mean, look, it's the end of summer. We're enjoying some outdoor time, right?HANNAH: Yeah.ADRIANA: Cool. Well, okay, so this very first episode of Geeking Out, I'm going to start off with a series of lightning round questions that I usually ask all my guests, and I guess my first guest is Hannah, so I'm going to read them off my phone. Sorry.HANNAH: She doesn't have good memory.ADRIANA: I don't.HANNAH: Sorry if there's noise, but hopefully the microphone...ADRIANA: I really hope so. Okay, first question. Are you a lefty or a righty?HANNAH: Righty. But I wish I was a lefty.ADRIANA: Because all cool people are lefties.HANNAH: Like, honestly, leftiness is cool.ADRIANA: It IS cool. I have to say, I love it. Okay, next question. iPhone or Android?HANNAH: iPhone.ADRIANA: Mac, Linux or Windows?HANNAH: Mac? Is that correct? Is that correct?ADRIANA: There's no wrong answer.HANNAH: No, but I don't know. I only understand Mac.ADRIANA: Okay, Mac it is. Okay. Favorite programming language.HANNAH: HTML or Excel?ADRIANA: I think Excel kind of counts.HANNAH: Yeah.ADRIANA: You'll see more in a future episode with Hazel Weakly.HANNAH: Yeah, but in my business class, we had to basically code inside the cells of Excel, and then we had to make an invoice for a magic store.ADRIANA: Yes, true. Okay, next question.HANNAH: And HTML is great. I love HTML.ADRIANA: I don't love HTML, sorry. Okay. Dev or opsHANNAH: Dops.ADRIANA: Dops! [laughts] JSON or YAML?HANNAH: YAML! It sounds like, "ya", "yak", and "llama"ADRIANA: Okay, awesome. That's great reasoning behind it. What is your superpower?HANNAH: Okay, so I thought about this long and hard. Long and hard. Long and hard. Okay, that's actually a good question.ADRIANA: I know. I just stuck it in, actually. This is a new. New for...HANNAH: Okay. Super speed, because I feel like you can do so much with that.ADRIANA: No, the question is not what superpower would you like? What is your actual current superpower? I'm super glad to know, though, that you would love super speed. I think that's actually a really good one, because it'd be nice to do.HANNAH: I'm so embarrassed.ADRIANA: Don't be embarrassed. This is hilarious. Don't worry. Wait 'til you watch one of our future episodes where I basically invent DevOps all over again. Ha. Ha. Ha. So if you feel embarrassed, don't worry.HANNAH: Okay. That felt like a job interview. Like, what's your superpower?ADRIANA: Yeah. One of the questions that I actually like to ask when I interview people.HANNAH: My superpower is at certain times, I can be very laser focused on what I'm doing and get it done really effectively. And I care so much about my work that I'm going to make sure it's the highest quality that it can be. I'm never going to slack off on anything if I truly love it.ADRIANA: That's true. Yeah. I can definitely vouch for that, which is why Hannah is such an awesome producer, video editor, social media, manager of this.HANNAH: Did I get the job?ADRIANA: Yes. Congratulations. Congratulations. You got the job. Okay, final question, and this is actually our topic for today, which is, do you prefer to consume information through text or video?HANNAH: Video definitely. I cannot...like, things just don't process as much if I read. I can read an entire book and be like, I kind of know what it's about. But then if I see it visually and I have someone kind of telling me the parts with actions and videos, I understand it way more. Like for a Shakespeare test, I cannot read very well. It does not process in my head.So it was the night before the Shakespeare test. I'm like, "Oh, my God, I don't understand any of this."ADRIANA: I mean, Shakespeare requires a secret decoder ring to begin with.HANNAH: Yeah, but I'm like, "I do not understand this. I'm going to fail this test." And so I watched YouTube videos breaking down each scene, and I'm like, "Oh, that makes sense."ADRIANA: So then you pass the Shakespeare test.HANNAH: Yes.ADRIANA: And then some.HANNAH: Yeah.ADRIANA: And you know what? I think that's actually a really important thing to discuss that a lot of people don't discuss, because I think there is a lot of emphasis in reading when kids are growing up in school, et cetera. And I think yes, I think we all need to learn how to read.It is an essential skill.HANNAH: But you don't need to be able to read high level books.ADRIANA: Yeah, I feel there's a lot of people are looked down upon if they're not amazing, avid readers. I do love reading. I do love to get lost in a novel, but Hannah doesn't. But I don't think any less of her or I don't think she's any less intelligent because she doesn't like to get lost in a good book. But you like to get lost in a good YouTube video.HANNAH: Yeah, people get so mad at someone deciding to watch a movie instead of read. They're both entertainment. They both teach you things. If you have the same story in a book and a movie, they will end up teaching you the same things.Who cares if it's on a screen or in a play or on a book? Like with text, it really doesn't matter as long as you end up getting the same or at least good things out of it.ADRIANA: Yeah, so true. Yeah, it's funny because even as you're growing up, we watch a lot of TV. No harm in that.HANNAH: No harm in that.ADRIANA: No harm in that.HANNAH:I don't like the stigma around like...ADRIANA: Oh, you watch so much TV, you must be a horrible person.HANNAH: I've learned so much from even TV shows like "Friends".ADRIANA: So many good life lessons.HANNAH: Or "That '70s Show" or "My Little Pony".ADRIANA: "My Little Pony" is a legit good show. Honestly, every adult should watch. It';s got such wholesome messages. I love it.HANNAH: Yeah, but it just really bothers me that people think I'm less of a human because I use YouTube videos or TV shows to learn when they're basically the same thing as a book.ADRIANA: I don't, by the way. I honestly...I embrace your learning style.HANNAH: I know, but when I tell someone about the Shakespeare story, they're like, "Well, that's cheating."ADRIANA: Not cheating.HANNAH: And it's like, but I bet if you're in my place and you just can't process stuff with reading...I can go through an entire page and not know what it was about and it's a struggle with me and I just feel like I should play to my own strength.And there's nothing wrong with playing to your own strength. What would be cheating was if you had the YouTube video playing on a headphone while you're doing the test. That's cheating.ADRIANA: That is cheating. Yeah, I totally agree.HANNAH: It's definitely not cheating to just learn your own way. And there's nothing wrong with however you learn as long as you end up learning from it.Like, maybe if I was just watching all these videos or TV and I'm not learning anything good from it, maybe then you'd have to be like, well...BUT, I'm learning something and I don't think people should get upset or tell you that you're learning wrong.ADRIANA: Yeah. Yeah, I agree. And I think it's really important because everybody has different learning styles. I'm not a video person, so usually when someone sends me a YouTube link, I'm like, this better be a short video and it better have captions because that's going to capture my attention.But if I need to learn something, I much prefer skimming through a blog post.But I appreciate that that does not work for everyone and different strokes for different folks. And I think we shouldn't look down upon anyone because they learn in a different manner. I think what I find really awesome about you is you've found out what works for you in terms of learning and so you basically hacked yourself. Right?The Hannah hack.HANNAH: But also I think it's more important now as we're trying as a society to destigmatize learning disabilities and different ways that people learn.I think one of the things that we do need to look at is we can't get mad at someone for learning in a way that maybe you don't learn.Because I just get really annoyed when I say that I don't read books and people look at me like...ADRIANA: "Oh, you're an idiot."HANNAH: Yeah. It's actually very upsetting because I spend a lot of time doing the things that I like and learning about them, and I have end up learning about them and I'm proud of that.But then for someone to say, "Oh no, you didn't learn it the right way" It's like, but I still ended up learning.ADRIANA: Hannah wants to become a dentist when she grows up. And guess what? You learned a bunch of dentist facts. So oh, tell us some dentist facts.HANNAH: Charcoal is bad for your teeth. Do not brush more than like two times a day. Also, this is not professional advice. This is stuff that I've learned and that braces are sometimes on dogs.You don't want to mess with braces stuff.ADRIANA: You don't want to put braces on dogs? Or you do?HANNAH: No, you do want to put braces on dogs. If you have braces, you don't want to do anything else that the Orthodontist doesn't recommend, like trying to find a hack to move faster.ADRIANA: Oh, yeah, fair enough.HANNAH: I get that social media is like, yes, there's a lot of bad stuff that comes with it, but youalso have to think of it as a different perspective on someone who has actually been helped by social media.I don't think I'd be the same person that I am if I didn't have social media.ADRIANA: That's true. Yeah. You've learned so many cool things, like the most random stuff, like Hannah's been getting financial advice from YouTube.HANNAH: I have! You know, all about investing.Yeah, but I just think that we really need to stop thinking of social media as a bad thing.Like this horribly toxic thing.ADRIANA: Like you said, there's bad aspects to it that are soul sucking and trolls are horrible and that'll mess with your mind.But we also need to remember that social media can be a really cool source of education and I think we need to embrace that as well.HANNAH: Yeah. And someone said to me, well, you're just "mindlessly" scrolling on YouTube? And I'm like, but then if I hadn't mindlessly been scrolling, I never would have actually found these things. I don't think I would have discovered different trying to think of something I've learned, like stuff about job interviews or disability rights issues if I hadn't been just like,I don't look for these things, but because they came to me, I'm interested in them and I can spread my information that I've learned.And so there's nothing wrong with scrolling on social media because it'll take you to places that you never would have gone otherwise.Because I don't think I would have actively been looking for financial advice. Yeah, financial advice, something like that. So I just think it's a really helpful tool. Yes.I'm not saying that there isn't bad stuff. There's a lot of bad stuff and misinformation, but you have to look at the light of and think of someone else's viewpoint of it.And we can't just say get rid of all social media, because then that would be getting rid of a resource.It would be like getting rid of a library.ADRIANA: Yeah. Because it's basically demonizing the whole thing, where it's like, well, guess what? There are bad books out there.HANNAH: Yeah, they're books with, like...ADRIANA: Misinformation...HANNAH:...comments...Exactly. Yeah, there is misinformation books.ADRIANA: So how's that any different? It's just, back in the day, we had books. Nowadays we have books and videos, and others...we've got, like, social media. So it's just like the evolution of how we consume information, which I think is super cool.And I think really the moral of the story is don't judge somebody by how much they read or don't read. Judge them by like...HANNAH: what they've come out of it with.ADRIANA: Yeah, exactly. And being tolerant of how people consume information and understand that not everybody's going to learn like you do.And I think it's been really cool getting to see like, you know, I learn in a very particular way and you learn in a very different way. And you also like to learn by sometimes by watching others being shown. Which is something that her teacher in the early years of Montessori, her teacher Cecile, figured out early on.I mean, that's so cool to be able to understand how we learn so that we can be our better selves, right? Because there's no way that we can improve if we can't learn.And part of hacking ourselves is understanding how we consume information.HANNAH: Some may say, oh, well, you're getting better at spelling and vocabulary when you read. You can still do that by watching something. Yeah, I can learn new words by someone just saying them. And I can be like, "Hey, let me look it up.""What's that word?"Or if I like to watch stuff with subtitles on, I'm like, "Oh, that's how that's spelled."ADRIANA: Yeah, that's so true. There are just so many ways that people can learn, and the more we say, well, this is bad, you're just trying to stop people from learning, which.You're excluding an entire group of people who choose not to learn or cannot learn in the same manner.HANNAH: Yeah. So I think that's all I wanted to say, you know. I may come back for another episode about this. We might have a guest on who has an opposite opinion.ADRIANA: Oh, yes, on social media. Yes. Hannah's friend Alice we've tapped her to come for a future episode. We're very excited to have her on.Yeah, well thank you Hannah for joining me today.I hope y'all enjoy our inaugural episode of Geeking Out.Make sure that you follow us on all the socials...HANNAH: And let us know what you think about this topic because it's a very interesting topic that a lot of people have a lot of different opinions on, so I'd like to hear those different opinions.ADRIANA: Yeah, definitely.And the interesting thing about this topic too is it's not a technical topic, but it applies to pretty much any job out there, right?Whether or not you have a techie job like me or a non techie job like you want to pursue.I think understanding how we learn makes us better at doing the jobs that we want to.Yay.Well thank you, Hannah.And with that, thank you so much for joining us on Geeking Out.Be sure to follow us on all all the socials. We've got show notes coming your way.Until next time...HANNAH: Peace out, and geek out.ADRIANA: Geeking Out is produced and hosted by me, Adriana Villela. I also composed and perform the theme music on my trusty clarinet. Geeking Out is also produced by my daughter, Hannah Maxwell, who, incidentally designed all of the cool graphics. Be sure to follow us on all the socials, by going to bento.me/geekingout.

    Explicit
  • TRAILER: Geeking Out Live at KubeHuddle on May 7th

    05/03/2024

    geekingout@dzerolabs.io (Adriana Villela, Hannah Maxwell, Helen Shen)

    Geeking Out will be doing a LIVE episode at the KubeHuddle Conference in Toronto, Canada, on May 7th at 16:25. We will be doing a very special mental health panel featuring Tim Banks, Marino Vijay, Diana Pham, and Lian Li. You can catch us either live in-person, or streaming on one of our socials: YouTube, X, or LinkedIn. For links to these, go to https://bento.me/geekingout.

    Explicit
  • The One Where We Geek Out on Authorization with Ori Shoshan of Otterize

    11/07/2023

    geekingout@dzerolabs.io (Adriana Villela, Hannah Maxwell, Ori Shoshan)

    About our guest:Ori Shoshan is the Co-Founder and CTO of Otterize, where he spearheads a leading Workload Identity and Access Management platform that automates and simplifies access control for cloud-native environments. By offering a declarative and zero-trust approach to access management, Otterize empowers organizations to streamline network policy management while ensuring maximum security.Drawing from a remarkable 15-year career as a seasoned platform engineer, Ori's expertise is underpinned by his leadership roles in both technology and personnel at esteemed institutions. Notably, he made significant contributions at the IDF cybersecurity unit 8200 and served pivotal roles in cybersecurity and developer tooling startups, such as Guardicore (now part of Akamai) and Rookout (now a part of Dynatrace).Find our guest on:LinkedInX (Twitter)Find us on:All of our social channels are on bento.me/geekingoutAdriana’s X (Twitter)Adriana’s MastodonAdriana’s LinkedInAdriana’s InstagramAdriana’s BlueskyShow Links:OtterizeMicrosoft IntelliMouseBlue Screen of Death (BSOD)MacOS Kernel Panic (Mac equivalent of BSOD)Mac Spinning Beachball (or Pinwheel)Yeti (mythological creature)Python async awaitHCLINI fileMSDNOtterize Client IntentsOtterize Network MapperNetwork Mapper OpenTelemetry PROtterize CLIGraphvizOtterize CloudClay Smith (OTel PR contributor for Otterize Network Mapper)KomodorOpenTelemetry DemoKubeshopTracetestAdditional Links:Find the Otterize team at KubeCon NA 2023 in Chicago, in booth P18.Adriana’s KubeCon talk on Platform Engineering with co-speaker Ana Margarita Medina (sched.com)Adriana’s Observability Day talk on the Observability of CI/CD Pipelines with co-speaker Reese Lee (sched.com)Transcript:ADRIANA: Hey, y'all! Welcome to Geeking Out, the podcast about all geeky aspects of software delivery, DevOps, Observability, reliability, and everything in between. I'm your host, Adriana Villela, coming to you from Toronto, Canada.And geeking out with me today is Ori Shoshan of Otterize. Welcome, Ori.ORI: Hi, thank you for having me.ADRIANA: Super excited to have you here today. Where are you calling in from today?ORI: So I'm actually in Berlin, but normally I am in the periphery of Tel Aviv, Israel.ADRIANA: Cool. Well, let's let's get started with our lightning round questions. Are you ready? Okay, first of all, are you left-handed or right-handed?ORI: It's a complicated answer. I know you said the lightning round was going to be easy.ADRIANA: It's all good.ORI: I'm left-handed on the computer, but I write with my right hand. You can thank my school for that. They basically made me use my right hand, so I guess I'm ambidextrous.But I tend to write...like, I basically just sign stuff with my right hand at this point in life because everything else is on the phone or typed, so yay.ADRIANA: Oh, yeah, it so you were probably born a lefty, but turned into a righty.ORI: Yeah, but I like my left-handed mouse.ADRIANA: That's interesting. I'm left-handed and I never got the left handed mouse thing, I think because the first time that someone presented a mouse to me was, like, a right-handed mouse, so I never even thought of holding it with my left.ORI: Yeah, that's a big problem. I always have to like when I buy a new mouse, sometimes I feel like as the years go on, it gets harder and harder to find, like a symmetric mouse that isn't specifically for right handed people.ADRIANA: True. That's true. Actually, you just made me think of, like do you remember? I think it was like the Microsoft mouse that was like it was shaped for right-handed people, and I remember thinking, oh, my God, if you're left-handed, you're screwed.ORI: Exactly. Yeah. So I make do with the smaller mice. But it's nice. It's an excuse to buy a gamer mice sometimes. Yeah, but it must be hard to find a cool mouse that will either be ambidextrous or tailored for left-handed mousers. Yeah, but it's a once in a few years thing. I just wish it was more like headphones, where you can basically buy the same pair again and again when they go bad.ADRIANA: Yeah, that's true.ORI: As long as they don't discontinue it.ADRIANA: Yeah.ORI: With the mice every time, I'm like, I want to buy this mouse again and they don't make it anymore, so I have to find the closest one.ADRIANA: Yeah. I feel you. I feel you. Okay, next question. iPhone or Android?ORI: Android,ADRIANA: All right. Mac, Linux or Windows?ORI: Honestly, Windows, even though I use Mac daily because I've given up because everybody else at the company wanted Macs, so I didn't want to be the odd one out, but I'm a Windows guy, through and through.ADRIANA: Interesting, interesting. I grew up on Windows, and then the first time I used a Mac, I hated it so much, and now I'm a full Mac convert. But I remember when Windows came out, I was like, this is the greatest thing ever.ORI: I think the thing that gets me is like, I've been in software development a lot of years by now and so on Windows, I really know how things work, like, beneath the outer shell, and when something doesn't work in the system, I know how to debug it. But with MacOS, my understanding only goes so far. So it's like if you see the famous beach ball spinning and something stuck on Windows, I would know how to figure out what is doing that. But on Mac, I feel useless. I'm just like, okay, better force close it and try again. Pray that it fixes itself.ADRIANA: I find that the funniest thing on Mac that ever happened to me is when I got, like, the Mac's equivalent of the blue screen of death, but it was so polite, and I'm like, oh, shoot, when this happens, I know I'm in trouble. I think I only got it once, but I was like, Damn, I should have taken, like, a picture of it. I don't even know what it looks like.ORI: I think I've had a few the last couple of weeks because I opened my laptop into, oh, everything's closed, and by the way, we've crashed. So you want to send an error report? Maybe, but I didn't get to see the actual crash screen.ADRIANA: I got to find a picture to include in the show notes. I'm sure someone's taken a picture of it.ORI: It's hard to see. They don't let you see it.ADRIANA: Yeah, that's right. It's like a Yeti sighting.ORI: Yeah, exactly.ADRIANA: Okay, next question. What's your favorite programming language?ORI: It changes along the years. Right now it's Golang definitely. I like to say it's a language for stupid people, and I'm one of those stupid people because it's really prescriptive about how you should do things. Generally, most of the time, there's only one way to do something, and I find that really valuable. I think it's insane that I can look at our own code base, like the back end and our open source code base and the Kubernetes code base, and they look pretty similar. And other languages not so much. I think Rust code bases will look very different. Don't get me started with C++, where the language basically it's worse than JavaScript. The language reinvents itself every couple of years. And there was so much sorcery to know. I probably couldn't read C++ code by now, even though like six years ago it was what I was doing all day...ADRIANA: Oh, wow.ORI: ...and before that it was Python.bPython will always have a dear place in mybheart, but it got complicated in Python free whenbthey added async await, it got kind of fragmented.ADRIANA: Yeah, fair enough, fair enough. Yeah, I do agree with you. Python...I have much love for Python. I started out in Java, and Java...I don't know, it's like coding in spaghetti. It's, like, such a verbose language, and most of my career was Java, but I'm like, nah, Java, I'm over you. I do like go. It's like, generally succinct except with error-handling. It's kind of weird.ORI: Yeah, it is weird. And it's a common refrain. I feel like a macro could help there, but I actually like the concept of like no, this is how you do things. And there are clear downsides to using Panics. You could use them theoretically as exceptions, as you would use exceptions in Python.ADRIANA: Yeah.ORI: But I like that they say this is how you do things, just do it this way. Shut up.ADRIANA: I do like, prescriptive things in that manner. I think we can do with more prescriptive languages, to be honest.ORI: It's just so opinionated. And at the same time, they leave some stuff out. Like it's not so batteries included that you don't have to do anything, which is a strange combination, but I feel it works well.ADRIANA: Yeah, definitely. All right, next question. Dev or Ops?ORI: So can I say both? I feel like probably a lot of people said it.ADRIANA: Yeah, a couple of people have said DevOps, so I'm like, yeah...but it's okay to have a preference of one over the other or, like, both. It's totally cool. Like I said, no wrong answers.ORI: Yeah, I guess both, you know, nowadays it's the popular thing to DevOps. And if you talk to people who work at, like, I think at Apple, they still separate dev and SRES a lot. And I talked to people who said they basically just throw stuff over the wall, over to Ops and they get to deploy it. And I really enjoy looking at the entire stack. So DevOps is for my spirit. I like seeing things happen end-to-end and like understanding, you know, like I said about Mac, that I can only debug so far. So I like that about DevOps, that I know what the code is and where it runs and when something strange happens, I can understand the system as a whole. That's really appealing to me.ADRIANA: Yeah, I can totally relate to that. Awesome. Okay, next question. JSON or YAML?ORI: JSON yeah, the spaces. The spaces. It's also like that spaces or tabs being part of syntax.ADRIANA: Yeah, that should be a question I could ask: spaces or tabs?ORI: Another thing I hate about Python is just there are so many discussions about that, like should we use this or that in Python too? And it's like it's meaningless and so many stupid bugs just by missing one space. No, definitely JSON even though it's annoying too. But I don't think that there is an ideal choice.ADRIANA: Yeah, fair enough. Fair enough. I did have one person say HCL, which I'm kind of down for because I feel like if JSON was, like, a little more pared down with some of the love from YAMLYeah, HCL is like a bit closer to INI files, right? INI files.ADRIANA: Yeah, true.ORI: Yeah. It is simpler to parse. I feel like I got to use them in the Windows part of my career.ADRIANA: Yeah, nice. All right, two more questions left. All right, so do you prefer to consume content through video or text?ORI: Definitely textADRIANA: That seems to be the winner so far. I've had some where it's like it depends, but it's mostly text. Word I feel like it's a little bit of a cultural thing, like in the front-end community. It seems that even JavaScript in general, I feel like videos are much more common, but growing up in the C++, no one will tell you anything. Just read man pages and like, MSDN documentation. I have a hard time when I can't scroll past stuff. So video is like the antithesis for that.ADRIANA: I know, right? Yeah, that's my biggest issue also, is, like, I need to be able to skim and search easily, and video just makes it a little bit harder. I use video out of desperation. It's like I have no other options, and all Google is giving me is a bunch of videos. I'm like, crap.ORI: It yeah, exactly. But for some things, it can be useful. And I get why it's more popular with front-end, because you want to see stuff in many cases.ADRIANA: Yeah, totally. Yeah, I definitely agree. I definitely agree.ORI: So yeah, I can understand it.ADRIANA: All right, final question. What is your superpower?ORI: Yeah. So can I say my wife? Can it be not something about me, IADRIANA: That's probably our most creative answer so far.ORI: Because I guess, like, at Otterize, we're not even two years old now. And being a founder is very demanding in terms of time and stress, and even the stress is showing up here and here [points to hairline], I like to say. So my wife has been really supportive this entire time. And just beyond not just being supportive or understanding, she talks to me about stuff, and it really helps me think things through, which can be important.And honestly, I think I would probably do a much worse job if not for her, because she really helps me process things, which is really important in such a stressful environment where you can if you're too stressed out, you can reach for knee-jerk reactions. And that's the opposite of what you want to do since you want to manage and not react. So she kind of helps center things for you.ADRIANA: That's awesome.ORI: Yeah, it's honestly, it I think that the biggest thing that has had an influence on how I do things. She gives a lot of space and support.ADRIANA: That's great. I really love to hear that. And I think this is actually a perfect segue for our topic of conversation because, as you mentioned, you are a founder of Otterize. So why don't you tell us a little bit about what Otterize is all about, how the idea came about, and what it's like to be a founder because you hear stories of the stress.ORI: Yeah, I think okay, let me start with Otterize. I was going to start with the end. So, Otterize...what we do... The name is a funny joke that alludes to what we do. So we do authorization for your back end. So it's called Otterize, because if you're Israeli and you say "otterize". Authorize and otters...they're cute animals. So it's a win-win. It's a pun.ADRIANA: Totally. Totally.ORI: So what we do is we make declarative zero-trust easy. We have released open source tooling that lets you map your Kubernetes clusters. And using that map, you can then auto-generate what we call Client Intents. So each backend service in your cluster declares its intentions, which is what it needs to access. So say I have a service that needs to access a database, an AWS IAM resource, another service. So my intent would say, I need to access this thing, and it does this in a high level Kubernetes resource called Client Intent. And then Otterize figures out how to configure your infrastructure to make it work, whether that means something like Kubernetes Network Policies or AWS IAM Policies or Kafka ACL Rules. Whatever infrastructure you have and we do that all open source with a Kubernetes operator.And I guess in one sentence it would be to make access control not a nightmare because there are so many different kinds. And as a developer, what do you want to do is I just want to call this freaking API and have it work, but then all of a sudden you've got configure IAM policies and that other service that's in a different cluster, so they have a different way that you need to authenticate and authorize.So as an aside to all that, I still get to do quite a bit of hands-on work, which is fun, and it's thanks to my awesome team that is very independent and awesome.ADRIANA: It that sounds super cool. And I think as our software is only getting more and more complex, and IAM is, I think, the bane of our existence in this space, and to be able to make it accessible, easier, less nightmarish, is awesome. And definitely very much needed in this space. And to be able to also codify in a standardized way, who'd have thought? I think that's a very awesome use case. So yay. Nice to see a tool like that in the space.ORI: It you know, as a developer, you want to say, I need to connect to that thing. You don't care if it happens with IAM and you need like a thousand different permissions, so we want to take all that away. The security team cares, you don't care, so you shouldn't care. High level.ADRIANA: Is the intent that you work like...developers work with the security team to kind of determine what those policies are supposed to be, but then the developers can, I guess, self provision that access? Is that how it works?ORI: Yeah, essentially, because what we've learned is that in most cases, security teams don't actually care to approve the policy except in very sensitive cases. Like if the ledger service for a bank has an API that transfers money so that one might be approved on a case by case basis, but in a lot of other cases, they just want to know that the access is intentional, that it's not an attacker.Just like they want to know that the code that gets deployed to production has been reviewed and approved, but they don't want to review the code themselves. And developers also don't want to talk to the security team. So both sides don't want to talk. They just want to get access and for it to be intentional.ADRIANA: Yeah. That's so great. I love that use case. Going back to we understand what Otterize does. Tell us a little bit about starting up this company. How has that been, and have you guys been around?ORI: We've been around since January 2022 and, well, it's been a crazy journey, as I guess any startup founder would say that.ADRIANA: Yeah, I would imagine.ORI: I think the biggest surprise for me would be I came into this as the CTO, and the CTO at a small size manages the dev team in the early stages. So I thought like, hey, this is going to be similar to managing a small team of developers, which I've done many times before. But what it turned out to be is I found out that when you start a new company, it's not just about managing the team because in an existing culture, an existing company, a lot of decisions have been made already.When you go to make a new decision, like, should we use this language or this library? Like the smallest decisions within an existing culture. A lot of decisions around that serve effectively as guardrails and in a new company. Even though everyone we hired were people we knew personally and worked with and have even worked together sometimes, some of them when we all joined, like day one, everybody has been to different companies. Like the previous company was different. So they all come with slightly different expectations for culture, for technical choices.So the challenge is less about how do you make...Bigger companies, the challenge is about how do you move quickly and how do you keep quality and all that. And for a new startup, I feel like the challenge is how do you end up with the right culture and do it quickly while everyone gets a chance to express themselves and feels included, while taking into account that everybody has different expectations day one, and that all happens really quickly. Like at a big company, when you start a new team, people might trickle in, but you start day one with four new people. So now you're four developers and the founders, and you're like, oh my God, so all of this has to happen at once. And everybody also really wants to work quickly.ADRIANA: Right, right.ORI: And beyond that, it just teaches you a lot about how a business works, like any business, the technical stuff, how does payroll work, all kinds of regulation. You learn a ton of stuff, which is really interesting and useful.In my day-to-day, I just got a mortgage, and I understand how banks see lawyers and people and companies and how to navigate that, which has been really useful now that I'm super busy.ADRIANA: Yeah. Um, so how did it all get started?ORI: I guess I didn't answer that. So as founders, we have experienced the pain of solving for authorization and authentication at every company repeatedly. And this is like authorization is one of those things that people just sort of accept for what it is. You start a new project or you need access to something else on IAM, so you accept that it's like this. But it doesn't have to be that way because you know, Android apps, when you build an Android app or an iOS app, you know that if you specify, "I need to open the microphone," you don't have to say which specific API it is or it's very high-level. And you know that if the user and the user sees all the permissions that they're going to need, and if they approve that, then your app is going to work.And you don't have the same level of confidence and simplicity in Cloud Native. You have to say on AWS IAM, if you're using a service that is writing to like, say, if you use Cloud Watch, it's writing to S3 buckets. And you got to make sure you also have access to write to the S3 buckets that is going to access beneath it all, which is insane. You're just a developer. You're doing one simple thing, and you have to think so deep, which, I mean, I love, but I think it slows it down if you have 500 engineers and everybody needs to understand this to make progress. And different teams use different tech stacks. We've seen people struggle with it. We've struggled with it and we see how it can be better in the mobile world. So like, why not for Cloud Native? Shouldn't accept it.ADRIANA: I think that's such a great idea. I think we see this recurring theme, too, in our space, which is, like, we keep solving the same problems over and over and over. Right? And you get to the point where, like, let me just package it into a damn tool already. Right? Because it's starting to get annoying. Like, why do we need to keep reinventing the wheel? We got better things to do.So I think that makes a lot of sense. Now, you mentioned AWS with Otterize. Does it work with other cloud providers as well?ORI: Yeah, it will.ADRIANA: Okay, cool. Nice. You got to start somewhere, right?ORI: Yeah. I think the reason no one has done this before, even though for mobile apps, it seemed kind of obvious, so both Google and Apple did it is because there are so many different kinds for other kinds of software that it's hard to even put them together. I mean, I don't think a lot of people would put network policies and AWS im policies, even though they both have the same word in their name in the same category, they would think of them as different things. It's an architectural problem, right? And you can't just imagine it all together. It's exactly the kind of problem that you would start a company for if you need to work on it for a while with a team.ADRIANA: Yeah, absolutely. Now, switching gears a bit, because I think this is the thing that got us connected initially. You all are doing some cool stuff around OpenTelemetry at Otterize, so why don't you share some of that with our audience?ORI: Yeah, sure. So we have built the authorized network mapper, which prior to OpenTelemetry, the way it worked is you set it up on your cluster, it's zero config, it's all open source and it captures DNS traffic and uses that DNS traffic to create a map of your cluster. Now, with OpenTelemetry, I've actually had a chance to work with OpenTelemetry relatively recently, but alsoa while back at my previous employer when parts of it were still called open tracing. And it can be a bit of an involved deployment to get your first few bits of data because you need to integrate SDKs and all that.So the Network mapper being an infrastructure level component that you deploy in your cluster, if it was able to export OpenTelemetry metrics, then it could make the first step to OpenTelemetry adoption a lot easier. Because I think the first step when you add instrumentation is to ask yourselves, what do I want to instrument? And if you don't know what you have, which in a large enough organization as the platform team, which might be keen on implementing OpenTelemetry, that can be where you are, that you don't even know what are the different components, which is connecting to whom, what are the dependencies that I care about.And the Network Mapper had that info and the awesome team at Lightstep/ServiceNow saw the Network Mapper and contributed an awesome pull request that exports OpenTelemetry metrics from the Network Mapper. And it was really a no-brainer for us to accept the contribution and support you guys because, you know, we think of the Network Mapper as there are a bunch of cybersecurity products with simple similar capabilities for network mapping, but we really wanted the network mapper to be a standalone thing that you could use independent of the rest of Otterize.So it's really like seeing what was possible to do with Grafana Tempo so easily with the same data that the Network Mapper has. We saw how it could make people's lives easier and really, that's what the network mapper is trying to do. To be a simple tool. You can just "helm install" on your cluster with zero configuration and get as much value as you can in a complete open source fashion.And that really works well with OpenTelemetry. So far, the Otterize Network Mapper had a CLI that was using Graphviz to create a visual map of the traffic. And you could also hook it up to Otterize Cloud to get an interactive map. But now with OpenTelemetry, you can hook it up to your Grafana instance and get an interactive map, which then helps you see, okay, I'm interested in this service and it's communicating to these three other services and that's where I want to start with OpenTelemetry.ADRIANA: Right.ORI: Yeah, it's pretty powerful...the combination, I think.ADRIANA: Yeah. And it's so cool to I think it's nice to see more and more vendors, including OpenTelemetry as part of their products, because, first of all, I think it shows the staying power of OpenTelemetry, but secondly, like, the recognition that, "Hey, this could help our customers, too." Right?ORI: Exactly. And mission number one is to make people successful in what they do.ADRIANA: Yes.ORI: And we really want Intents and Otterize and easy network mapping to be something that everybody in the Cloud Native community has access to. So we have aspirations to turn Client Intents into the way that you do authorization, even independent of Otterize, contributing to upstream.So that really falls in line with that. How do we make the network mapper more useful? Like a no brainer.ADRIANA: Yeah, absolutely. So have you seen internal and external benefits as a result of the work around the network mapper, like, with OpenTelemetry?ORI: Um, so it's still quite early.ADRIANA: Fair enough.ORI: I think it's just been out for about a week or so and we are I believe we're going to publish a blog post together that will help it get noticed.ADRIANA: Yeah, definitely.ORI: So right now, I think it's depending on people organically discovering it, which, I mean, it can happen and the Network Mapper gets organic traffic, but people who are specifically looking for OpenTelemetry and using it with Grafana Tempo are going to be best served by content that points to that. We want to add a tutorial for that too,ADRIANA: Cool. And do you have any future plans around continuing OpenTelemetry integrations?ORI: So we still need to explore that. Off the top of my mind, I'm not well versed enough to say what, but definitely I think even now there's more data that the Network Mapper has access to. Like, if you have Istio or Kafka, then it can tap into resource-level or topic-level information which can probably be reflected in OpenTelemetry as well in the same infrastructure way. And once we add more capabilities to the Network Mapper, we want to add cross-cluster discovery and the ability to discover infrastructure outside of Kubernetes from within Kubernetes. So that could also be interesting to add to the OpenTelemetry support.ADRIANA: Right. Awesome. And can you speak to how OpenTelemetry is being set up or are you guys running like a Collector as part of your internal infrastructure or...what does the landscape look like?ORI: So we're we're pretty new in terms of the internal deployment. I mean, I've had the opportunity to use OpenTelemetry before, but at other eyes we really only got into it with you guys saying, "Hey, remember Grafana Tempo?" Which we knew about before, but then we were like, "Of course." So as part of dog-fooding yeah, we started with setting up a Collector and a Grafana instance, but it's also really fresh at Otterize. We make it a point to use everything we put out, including contributions, so we know how it works for users. So we're pretty early there. But yeah...ADRIANA: Yeah, amazing how's the learning curve been for you and within the company in general for OpenTelemetry.ORI: I think there are some pretty cool tutorials and guides for we've looked particularly at Grafana Tempo which we said, videos and text.ADRIANA: Yeah, I always appreciate the tutorials with the screenshots.ORI: So Grafana Tempo has tutorials with screenshots, so getting like the initial setup has been pretty easy. But we did like I think if we built the integration completely ourselves then we would have had a slightly steeper learning curve because Clay at Lightstep did the research for us of what the metric should look like and how to configure it. So it was pretty straightforward. But I think also for a user that's trying to use it now, it would also be pretty straightforward because it was just one configuration value that we needed to pass to the network mapper after all is said and done. But I think it's interesting now to explore what else can we get from it now that we have the base layer of information there is.ADRIANA: Yeah. As a follow up, do you envision at some point adding Open Telemetry traces to your core product, for example?ORI: You mean like our back-end infrastructure or like the product itself?ADRIANA: For your application code.ORI: Yeah, because we use some level of Datadog APM to debug. So there's like a natural hook point that we would go into and hook up to OpenTelemetry now that we have it set up.ADRIANA: Right.ORI: Datadog was like we set it up just because it's the natural thing we reached for from previous experience. But we're just one step away from OpenTelemetry now. From places in OpenTelemetry.ADRIANA: You've got your foot in the door now with OpenTelemetry.ORI: Yeah, it's like all the infrastructure is there, the traceability of the code is there. Like we have contexts and everything in Go so that it's easy to pass traces. So I think we're a middleware away, which is a tiny step.ADRIANA: Awesome. That's so great. That's very exciting. And I think it's, you know, the other thing that that's super important to underscore here too is the fact that you had somebody making an outside contribution to your code base and it speaks to the power of open source, really, to be able to have your...your code's out in the wild. And someone saw this and they're like, "Hey, I got a cool use case."ORI: Yeah, absolutely. First of all, it was a pretty major contribution, which was cool. It's actually the first major contribution that we've had. We've had contributions before but they were of a bit smaller scale so it was exciting on that front as well. But yeah, the cool thing is that we were actually aware of Grafana Tempo but we didn't think to do that if we had thought about it, I think we would have built it ourselves before. But it's cool that somebody saw it, saw the potential, and just wrote the code, and now it's out there, and it's open source, and anyone can use it, and you guys contributed to it.And there's actually one other company, Komodor.io, which has incorporated the Network Mapper into their own product and their own open source, which is cool.ADRIANA: Oh, cool.ORI: It's cool to see people use it in ways we haven't thought of. That really. It's like you said, it's the power of open source that we don't need to think about every use case because someone else can think about it and add it, and all we need to do is to support and go like, yeah.ADRIANA: Yeah, totally. I mean, basically you've provided the seed and then people are just like, "Hey, what can we do with this now?"ORI: Right. And it's kind of like the pitch for Google Fiber in the United States was, we don't know what people will do with one gigabit of data, but we will build it and see what they do. So the Network Mapper is really that it's just it's raw data of your network, and it does the collection bit, and then you can just add more and more exporters, which just this is like an OpenTelemetry exporter. So there's so much you can do with a map of your network. I think every developer product and every cybersecurity product has a map of your network, so it's the most valuable and flexible kind of data for a development teammate.ADRIANA: Yeah, absolutely. And I'm just spitballing here, but I think a really interesting I wonder if there could be like...a really interesting use case with...I don't know if you're aware of the Open Telemetry demo.ORI: Which one exactly? I guess not.ADRIANA: So there's a repo called Open Telemetry Demo and it's based on the Hipster Shop app, which I believe originated with Google and they've turned it into like a telescope shop now, but it basically showcases instrumentation with OpenTelemetry. So it's this multi-microservices app written in different languages and so it shows different instrumentation in different languages with OpenTelemetry. And it started last year, just before KubeCon, and it's turned into this massively complex, but very cool showcase of OpenTelemetry's capabilities.And it made me think of something where...so recently there's this company called Tracetest. So they're part of this company called Kubeshop. Tracetest is the product and they offer trace-based testing. And so basically the idea is, like, you're already emitting traces. Why don't we take those traces and create test case pieces out of these? And so they recently integrated trace-based testing into the OpenTelemetry Demo to showcase hey, like we can leverage this to basically run automated integration tests.So then I'm thinking, hey, wouldn't it be kind of cool to have Otterize, especially the Network Mapper, integrated into this demo, showcasing, again, OpenTelemetry, the Network Mapper emitting metrics. So anyway...ORI: Yeah, it it a it's a great idea. I wasn't aware of it, but we definitely should do that. And it's funny because most of our tutorials are based on the Google Microservices demo. It's the we still have the stock shop. It's not a telescope shop, but yeah, I guess that app is everywhere. I've seen it on Calico too, and Istio for sure that's a good way to help people discover that the Network Mapper can emit OpenTelemetry metrics. I'm sure it will be useful to a lot of people.ADRIANA: Exactly. And especially it's an open source tool working with another open source tool.ORI: The way God intended.ADRIANA: Yeah, that's exactly. By the way, so we will be releasing this episode during the week of KubeCon. So by the time everyone's listening watching this episode will be out on the Tuesday. Will you be a KubeCon look for the Otterize?ORI: Yes, definitely will be in the main area. Damn. I don't know what our booth number is, but...ADRIANA: Look for the otters.ORI: maybe I can check and you can...yeah...Look for the otters. Maybe I can check and you can edit that in.ADRIANA: Yeah, you know what? I can add it to the show notes once you find the booth name or in booth number, I should say. Do you guys have, like, really cool swag that you're giving out?ORI: You guys, we're going to have the booth other plushies and T shirts, of course. Of course. Oh, my God, the otters are so cute. They have, like, this little key. I wish I had one to show you now.ADRIANA: Damn it. That means you have to go to the booth.ORI: It's like it's been...yeah... You're going to be there too?ADRIANA: Yes. I'm going to be a KubeCon. I'm going to be giving a couple of talks there. There one on platform engineering, actually, and self-service tooling.ORI: Yeah? I'll come see.ADRIANA: So I feel like it's, like, very on topic.ORI: Yeah, I'll be in the crowd. I'll go, "Woo! Yeah!"ADRIANA: I'm going to now make sure that I visit the booth because I definitely want to score one of those otter plushies.ORI: And socks. Will we have socks? Actually don't know. Last time we had socks, they were a huge hit. The first time we had plushies and socks, I was kind of worried, like, would the platform engineers that come to the booth be happy to get those. Maybe it's a bit like, what do grown-ups do with plushies? But then I was like, no, it's actually a hit. And grown-ups have kids too, so not only are they interested in one plushie for themselves, they need also one for every kid so nobody gets there jealous.ADRIANA: Yes, that's right. Because if you bring a plushie home and one of them is not for your kid, you are in trouble. It is the law. I do find the socks are quite popular because I find, like, for me, T-shirts usually are very hit and miss because I'm very petite, and so if it's not very small and fitted, I swim in the T-shirt. So the socks end up working very well because you can't go wrong with socks. They generally fit.ORI: Yeah, and startup socks tend to be like happy socks, very colorful and...ADRIANA: Yes, exactly.ORI: ... maybe you don't want to walk around every day branded, but the socks are like your little secrets.ADRIANA: Yes, exactly. They're perfect. They're perfect. Well, we are just coming up on time, but before we wrap up, are there any parting words of wisdom or hot takes that you would like to share with our audience?ORI: I guess...I'll go for words of wisdom. I'll try, I'm not good on the spot without my...ADRIANA: All right.ORI: ...without my wife, but I guess the thing that I would keep in mind as a developer is to always think about the people that will encounter your code and read your code. A lot of times we think about the design, the performance, does it look good? Does it work well? But I think the most important thing to pay attention to is about the people. And sometimes the people includes you. I'm sure a lot of people watching have come up on a piece of code they wrote and think like, what the hell, what is this? And then find out it's them a couple of years ago.ADRIANA: Oh, my God. It's so true. What the hell was I thinking?ORI: It yeah, and it like, it really goes a long way because, you know, it's the, it's the feeling you get when you use a product and you expect something to be there or you expect to be able to do something, or even the unboxing experience seems like they thought about the person who's opening the product. If you come upon a confusing bit of code that does something nontrivial and you find a comment that says why it's this way and what you should do if you want to change it, like, oh, someone has thought about me.And in some languages, like Go, you can go a bit further and use the compiler to do some of that. I think if you have a function that is doing I/O and it can block, then it's good hygiene to accept a context as a parameter and allow it to be canceled. Because you're not just allowing cancellation, you're communicating, hey, this thing is going to do something that you may want to cancel, it may block. And the cool thing is the compiler then forces the caller to actually make a choice. Like they have to decide which context are they passing in, which is a bit like returning errors. You're saying with a function signature, this thing can fail, which you can't not in every language.You can do that using exceptions, Java, you can say throws and like an endless list of exceptions. But there's nothing fun, more fun than in C getting an unexpected exception.And you're like, what is even going on? How did this get here? And it's like a leaky abstraction. So, yeah, my parting words are think of the people when you write code, not about the machines, because the machines, they're going to be fine. We're going to throw a bit more CPU and memory at it. The people are more important.ADRIANA: I really love that. That those are really great words of wisdom. Well, thank you so much, Ori for geeking out with me today. And y'all do not forget to subscribe. And be sure to check out the show notes for additional resources and to connect with us and our guests on social media. Until next time...ORI: Peace out, and geek out.ADRIANA: Geeking out is hosted and produced by me, Adriana Vilella. I also compose and perform the theme music on my trusty clarinet. Geeking out is also produced by my daughter, Hannah Maxwell, who, incidentally, designed all of the cool graphics. Be sure to follow us on all the Socials by going to bento.me/geekingout.

    Explicit

Similar Podcasts

  • MWAHdcast

    08/15/2020

    Monkey with a Halo

    A podcast about the LA Angels from the staff of the Monkey With A Halo blog. email us at MWAHdcast (@) gmail (dot) com.

    Explicit
  • You're Cozy with Clifford Myers

    08/15/2020

    Clifford

    Hey I'm Clifford and this is my podcast! Send your questions, comments, and suggestions to @CliffordMyers on Twitter or e-mail me at hello@cliffordmyers.ca!

    Explicit
  • Ignorance is Blessed with Jessica Michelle Singleton

    08/12/2020

    Jessica Michelle Singleton

    A podcast that attempts to overcome ignorance mostly be asking ignorant questions. Hosted by world touring standup comedian Jessica Michelle Singleton.

    Explicit
  • Waves of the REALM

    08/11/2020

    REALM Community Centre

    Coming out of REALM Community Centre in Cranbrook, BC, this podcast will feature different genres of music and highlight upcoming events at REALM.

    Explicit
  • Hysteria 51

    08/12/2020

    ForthHand Media

    Hysteria 51 is your offbeat weekly podcast destination for all things weird and wonderful! We navigate the cosmic highways of UFOs, the alien-infested landscapes, and the enigmatic frontiers of the paranormal. With your hosts, Brent Hand and David Flora, alongside our cantankerous tin man, Conspiracy Bot (with a not-so-subtle desire to rule the world, doubling as our chief inquisitor into the unknown), we delve into unique mysteries, the inexplicable, and the downright unusual.Each week, we explore a fresh topic, making one thing crystal clear... the truth is out there, but you won’t find it here.

    Explicit
  • Tenx9

    08/12/2020

    Pádraig and Paul

    Tenx9 is a storytelling night where 9 people have up to 10 minutes each to tell a real story from their lives. Each night has a theme. This podcast brings you a sample of 3 stories from each evening. Check out http://tenx9.com to find out the theme, date and venue of the next live event. Get in touch and tell your story.

    Explicit
  • FCC Presents:

    08/12/2020

    Body Tape Intl.

    An ambient-comedy variety radio show based out of Austin, Texas. Live every Tuesday 8-9 CST on KAOS Radio Austin. Hosted by Ethan Billips, Donna Bourgois, and Stephen Smith.

    Explicit
  • Nine Interview – DJ Xcalibur

    08/11/2020

    DJ Xcalibur

    DJ Xcalibur interviews the emcee, Nine (@Nine212)! He speaks about everything from the beginning of his career to the current state of hip hop. A very in depth interview that should not be overlooked! Check out the interview below!

    Explicit
  • GROWcast

    08/11/2020

    GROWcast

    {www.GROWcast.ca}GROWcast is hosted by Greg Campbell & Paul R. Stevenson and aims to create a community of like minded individuals focused on giving back to the community at the grass roots level. We interview community leaders and local celebrities to help create awareness and hear what they believe the most important aspects of life and community are.GROWcast episodes can be streamed on Soundcloud and iTunes. We have started booking our guests for Season 2 and our first recording will be on January 31st, 2016 with the one and only Tom Green. Other gusts for Season 2 include Stuntman Stu, Choclair and many others!Are you ready to GROW?Come check us out and have a listen!---www.GROWcast.ca

    Explicit
  • An Absolutely Dope Podcast

    08/16/2020

    The Collective

    Listen and laugh with CamQuotes, Brian James, Des, The Producer and Shaka as they "Edutain" you with music and real life and whatever else that may come to mind. It's An Absolutely Dope Podcast!

    Explicit
  • The Two Bobs Podcast

    08/12/2020

    The Two Bobs

    The Two Bobs is a comedy podcast about craft beer and weird news stories! We appreciate all of our listeners, and would love to hear from you, so be sure to check us out on Facebook, Twitter, Instagram, and Untappd! Then leave us a message on our Loyal Listener Line at 530-882-BOBS (2627). Thanks for listening!

    Explicit
  • Tortellini at Noon

    08/12/2020

    Zach Bartron, Conor Bradley, Mark Bryson, Ian Farrell, Donald Patton, Jackie Stein

    We thought it was a good idea to make a podcast, we could've been wrong. We are Zach, Conor, Don, Mark, Ian and Jackie and we are four friends with a mission, to make a dumb podcast. Come hang with us as you listen to conversations we'd have even if we weren't recording. Filled with topics that span from Movies to Music and of course Notes With Conor, which is sure to make you go "what". Hopefully you'll laugh at our intentional and sometimes unintentional comedy and if not, well you're probably smarter than us.

    Explicit

Episode Description

About our guest:

Kelsey Hightower has worn every hat possible throughout his career in tech, and enjoys leadership roles focused on making things happen and shipping software. Kelsey is a strong open source advocate focused on building simple tools that make people smile. When he is not slinging Go code, you can catch him giving technical workshops covering everything from programming to system administration.

Find our guest on:

Find us on:

Show Links:

Additional Links:

Transcript:

ADRIANA: Hey, y'all, welcome to Geeking Out, the podcast about all geeky aspects of software delivery, DevOps, Observability, reliability, and everything in between. I'm your host, Adriana Villela, coming to you from Toronto, Canada. And today I have the pleasure of geeking out with me, Kelsey Hightower. Welcome, Kelsey.

KELSEY: Happy to be here.

ADRIANA: And where are you calling in from today?

KELSEY: I'm in Washington state, so on the border of Portland, Oregon, and Washington.

ADRIANA: Awesome. Well, let us get to it with the warm up questions. Are you ready?

KELSEY: I am.

ADRIANA: Okay, first question. Are you a lefty or a righty?

KELSEY: Right handed.

ADRIANA: All right. iPhone or Android?

KELSEY: iPhone forever. And I've tried android. Given that I've worked at Google for almost eight years, I've tried, but I'm an iPhone person.

ADRIANA: Yeah, I'm an iPhone person too. I never tried android. I went straight from BlackBerry to iPhone.

KELSEY: I think BlackBerry was definitely...I was a BlackBerry person. I was also a Nokia person. But I think once iPhone really dialed in the ability to have third party apps in the App Store, iPhone all day.

ADRIANA: Yeah, I'm the same way. That was like one big sticking point. And for us in Canada, when the iPhone first came out, we didn't even have access to the App Store. So if you wanted any apps, you had to jailbreak your iPhone until it finally became available...because we get everything a little bit late here.

KELSEY: Awesome.

ADRIANA: Okay, next question. What's your favorite programming language?

KELSEY: The one that I can get things done in. So, at one point it was Bash, then it was Python, then it was Ruby when I worked at Puppet Labs, and then it's been Goblin, probably for the last ten years.

ADRIANA: Cool. Awesome. And Mac, Linux, or Windows?

KELSEY: Mac on my desktop. Linux on the server.

ADRIANA: All right, next question. Dev or Ops?

KELSEY: They're one and the same.

ADRIANA: I love it. Okay. JSON or YAML?

KELSEY: JSON. If I had to program against it, YAML if I had to write it.

ADRIANA: By oh, yeah, I definitely agree. I do find, like, manipulating JSON in Python is nicer, but YAML is more readable.

KELSEY: Yeah. To all the people that are like, JSON over YAML, let me watch you write it and see how fast you change your opinion.

ADRIANA: Yes, I totally agree with you there. Okay, this one's a little more controversial, and you can thank one of my previous guests for hinting at it. Spaces or tabs?

KELSEY: I don't care. I actually don't care if Python makes me uses Spaces and my IDE does the right thing. I'm totally fine, actually.

ADRIANA: I'm down for that. Okay, two more questions. Do you prefer to consume video or text when you're consuming content?

KELSEY: It depends. If I'm trying to learn, I need to read it, I need to see it, I need to be able to kind of backscan read it twice. But I do like video in terms of when people are really good at the human side of it. Right? Like, if they're expressing or showing me something, like, I want to see the code run. I want to see where they click. I want to see how they start. But when it's like learning something in the programming world, I need text. People are pretty bad at video and programming lessons.

KELSEY: Like, oh, just write these three lines of code. I'm like, can you please scroll up so I can see what you imported to make this work? So when it comes to seeing code, I want to see no snippets. I want to see as much as possible, but if I'm just going through for the first time to get the flow, video.

ADRIANA: I totally agree with you. And you landed on one of my big pet peeves. When consuming content for learning stuff, which is the code snippets, because I have been and I'm sorry, Hashi people, but this is a crime on the Hashi docs that I see all the time is that I get code snippets, and I don't get to see a full example on the site, and it drives me bananas. And I'm like, what does this apply to? Give me a full fledged code example? Link me to a GitHub repo at some point.

KELSEY: I'm always asking, why are people writing docs out there giving me hints to a murder mystery?

ADRIANA: Yes.

KELSEY: Show me the whole thing. I don't need it to be cute. I don't need it to fit perfectly in your style guide. I just need to see the whole thing and what's going on. So I think people do it out of style. There's really no substance when I'm trying to learn.

ADRIANA: Yeah, I completely agree. I do find it very frustrating. That's why, for me personally, whenever I do technical docs, I give excruciating detail. All right, final question. What is your superpower?

KELSEY: My superpower? I think one thing that I've learned over the years when it comes to mentoring, specifically, I used to be all about sharing my expertise, my background, my learning. And I've noticed that I changed my approach to holding up a mirror in front of other people and convincing them to like what they see and the number of people who actually like what they end up seeing and follow up with me. I really felt like that is a superpower, that you can actually have that impact on people. So that would be my superpower.

ADRIANA: That is such an incredible superpower. And I think it's so relevant to our industry, too, because we have a lot of smart people who suffer from impostor syndrome. And I think showing people that you are actually as good as you think you are is such a huge thing. Right? I mean, we've got some amazing stuff happening. I have some coworkers who are brilliant, and they're like, oh, my God, I feel like I'm just a hack. I'm like, Are you kidding me? I can't even keep up with some of the stuff that you're telling me right now.

KELSEY: Yeah. And I try to get people to understand that sometimes you aren't as good as you want to be. And that's okay too, right? I think there's okay with making progress, entering to new domains, and just helping people just relieve the pressure. Ideally, if you're any good at this thing, you're going to always feel this way forever because you're humble enough to keep learning, so you shouldn't feel so bad about it.

ADRIANA: Yeah, that's true. That's a very excellent point. So let's get into the meaty bits. One of the things that I wanted to share with our audience was how you came to be on the podcast. We met at KubeCon North America in Chicago this year, and you were doing a book signing. And I came, stood in line, the long line. It was totally worth it. And I was wearing this mask that had the sticker for the podcast, Geeking Out, and you said, "Oh, what is that?" And I said, "Oh, that's my podcast."

ADRIANA: And you said, "Oh, I could be on your podcast." So I am so stoked that you were able to join. And yeah, I mean, I've admired your work from afar for many years. I find your approach to Kubernetes very accessible, especially because it's such a complex subject matter. So I wanted to start off with how did you get into this field in the first place? Where did you find your calling to make things technical things, gnarly technical things so accessible to folks?

KELSEY: I want to answer that question, but I want to address this advice that I give to my former self and to people that I run into all the time. And they say, how do you put in the effort to make sure good things happen to you in your career and in your life in general? And so you at that book signing with the podcast on your mask. You're advertising to the world, this is my podcast, this is what I'm doing, and you're advertising what needs to happen next. And so for someone like me, I can see that clearly. I understand in that limited interaction that there is this opportunity that I could actually be on your podcast, because now I know you have one. I think a lot of people really confuse luck and that kind of effort, right? When you put that kind of effort forward, you tend to make things happen. And so I just want to highlight that part of you having that as part of your strategy of going to KubeCon, making the best use of your time and every human interaction. So kudos to you for doing that.

KELSEY: But it's a perfect example of how people kind of design their own careers and create the world that they want. So that's perfect. Now to your question about this whole idea of explaining things simply to other people. When I was getting into tech, a lot of people come from various backgrounds I come from the...fast food was my only job background, and I didn't go to college. And so for me, learning technology was like a pivotal life-making decision. I need to get into this field. I admire people that are in this field.

KELSEY: I don't know anyone that's in this field. And so I would go get all the books and just flip through them. I remember the first book I think I bought was the A+ certification guide. I was like, I'll start there. And you just go through all of this stuff and you look at all your notes, right? You're trying to simplify all the information to truly demonstrate that you understand it. And everyone knows that feeling of the A-ha! moment where you take something that is complex to you and you finally understand it, and your confidence level just goes up. It immediately goes up. And so that feeling, I've always enjoyed having that feeling because it felt so empowering.

KELSEY: So whenever I had the opportunity to speak at a meetup, I've noticed that some people at meetups or conferences, they speak, and it's just like, overwhelming. Hey, here's this computer science diagram. Here's this map that you cannot understand what's happening, and they are happy with just leaving it as a mystery to everyone. And you're like, what the hell was that? You had this opportunity to let me have my light bulb moment, but you chose not to. You chose to try to overwhelm me with your vast understanding of things that I don't. And so I've tried to say, what if I can make people feel like I felt whenever I learned a new subject? So this is why I've always said, hey, now that I understand this thing, I want to show it to you as well. But before I can, I have to give you context where I came from, my understanding beforehand, and then what led me to that understanding. And then let me show it to you.

KELSEY: And I try to use analogies and simple terms, and you can see the light bulb moment go off for people in the audience, and then it becomes a game changer for their own career. So for me, I think I got addicted to that. Like, hey, I don't want to talk. I don't want to write a tutorial if it doesn't have that impact on people.

ADRIANA: I absolutely love that because I can completely relate to that feeling, the euphoria, the high that you get from solving a problem, especially something where you've had to really put on the detective skills hat and try extra, extra hard to solve it. So that is so wonderful. I love that so much, and I think it's so important because making learning accessible to people, I think, makes it fun too, because I agree with you. Like those gnarly architecture diagrams that just look overly complicated, and then your brain starts to wander, and then you miss some important thing, and then that's it your opportunity for learning. That thing is gone if you're watching that lecture, because it's just, like, way over your head. So I think that's so great. Such an awesome approach to really disseminating information across the industry, especially these are not easy topics to unravel, right? So, Kubernetes, for example, how did you come upon doing your work with Kubernetes?

KELSEY: You know how you walk in on someone watching some hit TV show, they're on season six, right? And you ask them, what's going on? Why is this person not like this other person? They're like, I got to recap season three for you to understand what's going on on the screen right now. And so I think for a lot of people, Kubernetes was my season six, right? I had always been in tech trying to share information. If you would have caught me 15 years ago, you would have saw me at a Python conference teaching people about packaging Python applications. If you saw me maybe six years after that, I was at Puppet Labs trying to contribute to configuration management tools using Ruby. And so when I get to Kubernetes, there's a whole career behind me of trying to build similar systems without the terminology or the experience. You just know that there has to be a better way of doing things. So when I saw Kubernetes for the first time and really got hands on time with it, there was an a-ha! moment. I was like, you know what? All the scripts, tools, philosophies, techniques, it has now been serialized into this one checkpoint, and the industry has finally given it a name.

KELSEY: And so when I got that feeling, you know what was next, right? It was like, hey, I can't wait to go to a meetup to show people this thing. And I think the reason why I was able to resonate with so many people is because I had that previous background of doing things manually, trying different automation tools. And so I was just so excited. Like, I think we finally found the thing we've been all trying to build, and it looks like this. And so I think a lot of people got to see that season. It was like, oh, he's the Kubernetes guy. But there's so much historical context that goes into why I was ready to have that conversation, make those contributions at that time.

ADRIANA: That's basically the classic case of, like, everything you've done up until that point has led you to that moment, and now you're ready to take on that thing. Right?

KELSEY: I became a better speaker than I had ever been prior. I became a better engineer than I had ever been prior. And I've gone through all of that experience, and I was able to really articulate what was important. And I think for a lot of people who have been on this DevOps journey for a decade, nothing is working. We're doing all of the things: CI/CD pipeline, infrastructure-as-code. We're missing something here. And I think the industry had overly focused on automation and not abstraction. And Kubernetes was that final thing that you could touch to say, there is a difference between automation and abstraction.

KELSEY: And I think when people saw those new APIs, in many ways, I told people Kubernetes was like this type system to infrastructure. It was like a standard library that we'd never had. It's not like a thing that if you just install, it solves all your problems. But it's definitely a much better checkpoint than what people were doing before.

ADRIANA: Yeah, absolutely. And it's one of those things where I feel like it's a bit of a love hate relationship with Kubernetes. Right. Because in some ways, it makes life so much easier, and then in other ways, it's like, oh, my God, this thing is so complex to try to unravel in your mind. Right.

KELSEY: I want to address that a lot, because there are some people that think I am the biggest Kubernetes fan in the world, and I am not. I actually spent the last four years working on replacements. I spent so much time at Google Cloud working on serverless just to make Kubernetes go away. I learned everything about it because I think the best people that will replace it are the people who understand it the most. And the way I look at Kubernetes is very different. People look at it as a tool that is competing with their other favorite tool or some alternative ways of doing things. To me, Kubernetes is just another word in the dictionary, and my focus has always been, what does it mean? And as a contributor, what should it mean? And when I think about it as an aggregation of the previous ten year set of techniques, and you push them all together, you get this thing. And I study that thing for, like, wow, we've come a long way since those days.

KELSEY: Also, you can see what's missing. And I think that part is where, for me, that's inspiring. Oh, this is what's missing. So this is where the opportunity space is. Go work there and solve that problem. But I think a lot of people get into, oh, this thing is too complex. And I always ask them, but do you understand it? If you don't understand it and you say it's complex, then I think that's a mislabeling of the situation. You can just say, I don't understand it, therefore, I don't know why I would use it.

KELSEY: And I think that's a fair way to start the conversation. I think a lot of people are just dismissing it because it's complex, and I can do something much simpler, and then they tell me what they're doing. I'm like, that sounds like a Rube Goldberg machine. You just named 25 pieces of custom tooling so you can avoid using Kubernetes. I don't know if that adds up.

ADRIANA: Yeah, that makes a lot of sense. I think it makes sense too, like what you said earlier about looking for something that could potentially replace Kubernetes, because I also think that we tend to get into this sort of rut where we think, well, it all ends with Kubernetes. But we all know that software has evolved so much in the last 20 years. Even everyone was talking about Heroku is this awesome thing, and now, yeah, Heroku is still in the picture, but other things have come and kind of taken our attention. So where are we moving towards then in this space?

KELSEY: I think in some ways things haven't changed very much in 20 years. You write code, you build the code, and you try to do some process to get it on the server so people can use the code. About 20 years, people have been doing exactly that thing. Now, how people have gone about doing that thing, that's changed at different speeds. Some people are still writing KornShell scripts right now as we speak, deploying apps at their company, and it probably works well. Then you have some people that are still using tools like Capistrano because they want to use something that's written in their favorite programming language, in that case, Ruby. And so they just want to keep everything within their problem domain. And then you have some people who prefer platforms like Heroku, Cloud Foundry, you name it.

KELSEY: I think the challenge has been is lots of people have been looking for that one solution for everything. I remember when Cloud Foundry, like the Heroku competitor that you could run yourself, it was like, look, twelve factor apps are the way to go, and you can write everything as long as you use Java and Spring Boot. You do that, you're done, you're great. And then it's like, okay, that's fine. What about my batch jobs? Where do I run those? Not there. What about my databases? Where do I run those? Not there? And then what happens is you end up having to bring in a second or third platform. And that's where the harsh reality of all of this stuff is, is that whenever we don't have one solution to solve everything, you end up having to complicate your infrastructure. And I think complicated infrastructure just the actual norm at this point.

KELSEY: What the world wants in terms of if you have a public facing website, you're probably going to have a cache, you're going to have Cloudflare DDoS protection. Various security concerns that Kubernetes versus Heroku is such a small part of the decision making process that even if you got that layer right, it is such a small part of the equation that thinking that's where the complexity is, ignores the big picture, where I think things like Kubernetes are 1/100th of the equation.

ADRIANA: Right. That makes a lot of sense. Now, on a similar vein of Kubernetes like product, you've also done some work with HashiCorp Nomad, right? How would you compare Kubernetes to Nomad for folks who aren't familiar with both?

KELSEY: Respect to everyone that contributes. Because I've written lots of code myself, and you do the best you can. So we just got to make sure we get that out of the way. We're not attacking people here. So if you have a HashiCorp logo tattooed on your body or Kubernetes logo tattooed on your body, this is not about you at all. When I first saw Nomad, I remember, is when they announced it in Portland at one of the smaller first HashiConfs. And I was scheduled to give a talk about Kubernetes, and I changed the talk the night before to do Nomad versus Kubernetes. And I remember Mitchell, Armon and so many people from HashiCorp standing there watching the talk. Everyone's crowded in to watch the talk.

KELSEY: And look, I'm not a mean person, so I'm not someone that's naively attack a project that I'm not working on. Doesn't make any sense. But I did learn it, got it installed. And the things I liked about Nomad, you got this single binary written in Golang. You just put it on the server and it's almost immediately ready to go, starting getting value, right? That part around, just go get a binary and just have it run on the server. It really, really made that easy. The part that wasn't great, though, is the API. You look at it and it's like, what is this thing? Right? I think I get it.

KELSEY: And it felt like, oh, you're trying to copy the Borg white paper about what a task is, but you haven't used Borg enough to know that this is not what you want to copy. And so it was a good serialization of that knowledge that was out there. They built a very high performance fast scheduler. They optimized for scheduling, speed, and performance. But the thing I think that they missed was the ecosystem. This space now is about collaboration. So you have lots of people who want to build infrastructure, automation, tools. And the one problem we've had over time, in my opinion, is that you have to glue them all back together.

KELSEY: And scripting only gets you so far when you have to glue together all these various APIs. So Kubernetes takes a different approach. Kubernetes says these things are all related. Your load balancer and your app and your IPs, and your storage, your secrets, all of it is related. And they depend on each other. And so Kubernetes felt like it lived a life where the maintainers or the people of that project had been using Borg for a decade or two and said, what would we fix? And they come into a popular ecosystem like Docker and all these pieces, and they aggregate them. And when you look at the API, you can see the experience peek through. Right here is a pod.

KELSEY: A pod has to have multiple containers because most apps that people deploy in reality, need things like NGINX or sidecars or logging daemons. And so I felt like Kubernetes had so much more experience baked into it than just being a faster, easier to manage system for deploying things. So given that, it was really nice to see over time that both communities kind of learn from each other. I remember when Nomad started adding things like volumes, sidecars, or other things that you would typically see in Kubernetes. So I think some people like Nomad because of its simplicity. I kind of lean towards the simplicity side of the house, so I kind of resonate with the whole Nomad thing. But watching people kind of glue together, like vault console, and all these other pieces to try to get a whole system, I'm like, man, at this point, now Kubernetes starts to look a little better.

ADRIANA: Yeah, I definitely agree. I worked at a job where so I had come from a Kubernetes background and worked at a job where it was a Hashi shop, and they're like, oh, we're using Nomad. So I'm like, oh, my God. How do I translate this? And when I learned that Nomad is not fully equal to Kubernetes, that you have to still stitch these other pieces together, I'm like, oh, okay, that complicates things. But I definitely agree with you. One of the things that I do appreciate about Nomad is that certain things seem a little bit simpler. And I did find the learning curve not too bad. Maybe it was because I also knew Kubernetes at the time, so maybe that helped and it allowed me to translate.

ADRIANA: But there's definitely a lot of stuff that I appreciate about Nomad, and I'm glad that I've had exposure to both ways of doing things, because I think that's really cool. And like what you were saying, both communities learning from each other rather than, like, let's hoard our secrets, because that way you can end up with better products overall, right?

KELSEY: 100%.

ADRIANA: Now, one thing that I wanted to ask you about was your famous Hashinetes tutorial. What motivated you to put this together? And also, if you can just share with folks what this Hashinetes thing is.

KELSEY: I remember the Hashinetes talk, because that was the year I was like, okay, all of these tools have been out for a while. Vault is out. Consul is out. Nomad is out. Kubernetes is out. Now what? How do you think about all these things? What do you even do with them? And I remember that year I wanted to have fun, right? Previous years, it's more about, what are these things? And then maybe years after that, it's like, it's in production. But I was like, you know what? I want to have a irresponsible talk. I remember starting to talk off: "Today we're going to be irresponsible."

KELSEY: "Do not do this in production." "Do not go to work and say Kelsey said anything." This is just having fun. Okay, and so I remember having a Kubernetes cluster or maybe even Nomad, and said, all right, we're going to install Nomad as an app to see how it works. And I just started adding different layers and components one by one. Number one, teaching people how all of these things actually fit together and how another scheduler could actually arrange them and put them into place. And then I think people had so much fun with the talk. It's like, wow, look how powerful these tools are that they can actually deploy and manage each other if you really wanted to.

KELSEY: And look how they're similar in some ways. And I think a lot of people were like, oh, these are just you need to pick one or the other. And at that time, there was a blog post of a company using Kubernetes for some stuff and then using Nomad for some of their batch jobs that would benefit from the Nomad way of doing things. I thought that was just, like, the right way to think about it. So that talk Hashinetes is like, what happens if you push Kubernetes and all the HashiCorp tools together, like using Vault for secrets instead of the thing that was built into Kubernetes, because I think Vault was a far superior secrets management product and API. And then what if you were to use Consul instead of Kubernetes built-in service-discovery? What would you get? And then let's just say you really do like Nomad. What if you were to run that inside of Nubernetes, too, and let that become the scheduler instead of Kubernetes doing the scheduling? And I think when people kind of saw that talk, they understood how to really fairly evaluate those tools. So we just had a bunch of fun.

ADRIANA: What do you think was the biggest learning from putting this talk together for yourself?

KELSEY: I think, honestly, if you just live 100% in Kubernetes land, all you know is config, maps, secrets, and you have an idea in your mind that there's no other way of thinking about these problems. Right? Everything must be a CRD. Kubernetes, Kubernetes, Kubernetes. But I think people forget I was a contributor to Kubernetes. I knew how some of the inner workings worked. And so it's like, how do you get Vault to work nicely inside of Kubernetes? Then you have to rethink the APIs, and you start, oh, the Kubernetes secret management API isn't that great at all? And so when you bring in Vault and you have to stitch it in and bake it into the whole process, you really do gain empathy for gluing all of these parts together yourself. So I think the biggest learning for me is that, number one, you can do it. There are situations where it does make sense.

KELSEY: Think about it. If you have multiple clusters and you want to have multi cluster service discovery, you cannot do that with Kubernetes alone. When you add something like Consul, you can have Consul be the place that takes over DNS. And guess what? Voilà, you can now address multiple clusters using one service discovery tool. And so it's like, oh, okay. So even though Kubernetes hasn't solved all the problems, it doesn't mean that you can't bring in all these alternative tools to step in and fill that gap.

ADRIANA: And it's nice to see that everything plays nice in that little ecosystem and that you can, I guess, take advantage of each tool superpowers, right, to sort of give that boost to Kubernetes Awesome. Now, on the Hashi front, I also wanted to talk to you briefly about a talk that you gave at KubeCon EU, "From Community to Customers". And I attended that talk, and I really enjoyed the talk. I thought it was very interesting how you were talking about this fine line of what to keep open source versus what not to keep open source. One example that you cited was HashiCorp, and then shortly thereafter, HashiCorp changed their licensing. So what are your thoughts around that?

KELSEY: Yeah, I actually had this question come up a few times, and I always tell people from a place of empathy, I had a project, Confd. It became a little popular. I remember going to FOSSDEM on the other side of the world in Europe, and watching someone give a talk about using Confd, this miniature configuration management tool, and how they were using it and why they thought it was one of the greatest projects ever. Like, as a maintainer of an open source project, you'd love to see a community form around the thing you've built. But as a solo maintainer, you also know how hard it is to say no. And you wake up on, like, a Saturday morning and it's like, hey, I work at a huge company that makes tons of profit, and I get paid really well to do my job. I would like you to work for free and add this feature that we really, really need to make even more money. And you're like, no, this is not my priority.

KELSEY: Number one, you're not paying me anything. And then two, you know what? You're going to have to prioritize that itself and maybe step up and do some contributions. And so when you think about it that way, and as someone who's also contributed code to HashiCorp products in the past, I did those contributions to scratch my own itch. And I understand that once I deliver those changes, it's on the HashiCorp team to maintain them forever. And so I understand the relationship here is me contributing code is not the end of the story. And so when they make that licensing change, I put myself in their shoes of trying to run a business and remember, they're a public traded company. So a lot of these decisions are not in fully their control anymore. The market wants to see profit growth.

KELSEY: I don't know if you've ever worked at a profitable company, people listening to this. But having stagnant revenue year over year is a fast way to get shareholders to leave investing in your stock. So now they have this added pressure of no longer just making the open source community happy. The people that they kind of started their careers off of, now they have to try to make the market happy. And there you get into different behaviors. So now you got to figure out where to get revenue from. And if you ask someone, Where do you get revenue from something that is given away 100% for free? Last I checked, most people do not pay for things unless they have to pay for things. And so you got to draw the line somewhere.

KELSEY: And I think the big controversy is, where do you draw the line? Do you draw the line on the core of the product? NGINX tried to do things like that. It didn't work out well over time, do we draw the line on, like, enterprise features and Web UIs? Right? That could be a fair place to draw the line. And so I think for a lot of people, HashiCorp decided to draw the line at commercial competition. If you take our software and start competing against us, using our name, likeness, whatever we say now in our new license, the business source license, that you can't do that. And so if you're being honest, as a user, don't really care. Like, I don't plan to start a business competing against terror. If you're being honest, I literally don't care.

KELSEY: And most people don't really exercise all their open source freedoms anyway. I'm not saying that's not a good reason not to have them, but a lot of these licenses like Apache 2 to me to fully realize the benefits of them. I think you do need to become a contributor to really understand what the code base does, be willing to step up to fork a project when the time comes and having the skills to maintain it. A lot of people don't understand that's the other part of this deal. And so when they change that license, I think people got a wake up call. They own that project. It is not our project. Even those with that HashiCorp logo somewhere tattooed on their body, it's not your project.

KELSEY: It belongs to HashiCorp. And so now I think there's a rethink. And a lot of people forget HashiCorp predates the CNCF, right? So they're not a part of a foundation, even though a lot of their technologies are foundational, TerraForm, Vault, those things belong to HashiCorp, a private company doing what they have to do. And so for me, I look at that business license change and says, great, they made their stake in the sand. From a business perspective, this will be good for HashiCorp. Now they can say no. And now their terms are a bit clear and no longer vague. Now, for the community that is upset,

KELSEY: now it's time to exercise those open source rights we've all been talking about for so long. You get to fork the project, you get to maintain the project, bug, fixes security, fixes new features and then ask the question how compatible should you remain going forward with the thing in which you branch from? That's what's on the table. So those are my thoughts on it. It's very pragmatic. I think it's one of ownership and responsibility and no matter how you feel about it, you're going to have to take on ownership and responsibility going forward.

ADRIANA: Yeah, absolutely. It makes so much sense and I think you hit on a very important thing when it comes to maintaining an open source project, which is maintaining it. It is a lot of freaking work and especially if it's something that you do on the side for funsies. You can only expect so much, especially if you're the solo maintainer. So also hats off to anyone who is a solo maintainer of an open source project or works with a very small team because it's a lot of work. It's a labor of love at that point, right?

KELSEY: I want to make sure people understand. A lot of people may have an ops background. That's definitely where I come from. And people think dev is easy and there's the same stress that you have in operations, right. For example, if you replace a hard drive in a server with a bad hard drive, you worry the first couple of days like, is that RAID configuration going to actually rebuild on time and the hard drive is going to stop being slow before traffic comes. You worry about these things and this is why we started doing things like on-call. And when you are maintained of open source project, you know that anything you merge in will make its way to someone's production, someone you probably don't know and you're going to feel responsible and accountable for doing that. And so there's a lot of this added pressure of like, hey, I got to be able to say no and make the right decisions to make sure that no one is going to be negatively impacted by these projects.

KELSEY: I think a lot of people forget that when we start to ask and I don't like the way this person runs this open source project, there is so much pressure that goes into it. So just know that there's humans behind these projects. There's a lot at stake. So if they say no to your new feature or they have to make a business license change or stop accepting pull requests for a while while they go tend to other matters, you just have to understand that just what comes with the territory.

ADRIANA: Yeah, absolutely. There are humans behind those repos right at the end of the day. Well, we are coming up on time, but before we wrap up, I was wondering if there are any parting words of wisdom that you would like to share with our audience?

KELSEY: I don't know if there's any parting words of wisdom, but I do think we're at this next cycle of new technology on its way, whether it's AI or LLMs, some people only know that stuff as chat GPT. And the question that I'm hearing a lot around is, like, is this thing going to take my job? And I always ask those folks, what is your job? And they say, "Well, for the last ten years, I've just been running scripts and automating things, and I'm like the same things for ten years in a row." I was like, "Listen, if that's how you would describe your job, then yes, you might have a problem when a new set of tooling comes around that reduces the need to do that." And that's always happened throughout tech. And I think what most people should probably think about is take these moments of insecurity and just do some self reflection and say, "Hey, my tools"...and I think we started the conversation this way. People tend to confuse automation to abstraction, and a lot of times, people get so comfortable automating the same things over and over, almost like a Westworld Loop, that they forget that we should rethink the thing that we're automating and ask ourselves if we should replace it with better abstractions. So I would say this this may be your very moment to pause for a second look at the work you do, and ask yourself, "Is it time for a new abstraction?" And if it is, I think that's the perfect opportunity to either go find a project that's attacking that problem or maybe even start your own that introduces the new abstraction based on all of that experience that you have.

ADRIANA: Awesome. I really love that. Well, thank you so much, Kelsey, for geeking out with me today. Y'all don't forget to subscribe, and be sure to check the show notes for additional resources and to connect with us and our guests on social media. Until next time...

KELSEY: All right, everyone, don't forget to Peace Out and Geek Out.

ADRIANA: Geeking Out is hosted and produced by me, Adriana Villela. I also compose and perform the theme music on my trusty clarinet. Geeking out is also produced by my daughter, Hannah Maxwell, who, incidentally, designed all of the cool graphics. Be sure to follow us on all the socials by going to bento.me/geekingout. Hey, hey Geeking Out fans! We're taking a little break for the holidays, so this will be the last episode of 2023. Be sure to catch us again in January as we Geek Out with a fabulous lineup of guests.

ADRIANA: See you in 2024. And Peace Out, and Geek Out. Bye!

Discussion (4)

Be respectful and constructive in your comments
A
AaravitaKuznetsov7203 5/6/2025, 2:00:49 PM

Just listened to this ep & I'm SO stoked Kelsey Hightower talked about Service Meshes! Definitely added a new layer of complexity to my Kubernetes setup

P
PriyaLi494 5/20/2025, 2:00:51 PM

Just listened to the latest ep with Kelsey Hightower on Kubernetes...mind blown by his experiences in leading containerized projects!

A
AaliyahGrigoropoulos3346 5/24/2025, 1:32:00 AM

OMG yessss Kelsey is soooo knowledgeable about Kubernetes! finally a podcast that makes me feel less lost in the cloud

N
NikhilPatil8099 5/10/2025, 1:32:01 AM

Kelsey is such a legend! I loved how he broke down Kubernetes into super digestible chunks for us non-devs