text
stringlengths
0
2.46k
**Jeffrey Sica:** I had a co-worker who was also a roommate, who is also my best friend, and he's my best man; he was my best man at my wedding.
**Jerod Santo:** Oh, wow.
**Jeffrey Sica:** We worked at the University of Michigan since the start, we both moved departments from Pathology over to Advanced Research Computing. I went to Red Hat, he went to Google. My best friend is Bob \[unintelligible 00:28:08.06\] He lives down the street from me.
**Jerod Santo:** That's cool.
**Jeffrey Sica:** \[28:12\] We are almost inseparable, except when I get to go to events and he doesn't. Trust me, if he was here, I would have been asking for another microphone, because we just would have done that.
**Jerod Santo:** We have another microphone. We would have got him on.
**Adam Stacoviak:** We do have one more if we need it. So... Bob, come on!!
**Jerod Santo:** That's cool.
**Jeffrey Sica:** Oh, are you going to KubeCon Chicago? I'll drag him over.
**Adam Stacoviak:** Let's talk off-mic. I've got ideas.
**Jerod Santo:** Alright, thanks, Jeff.
**Jeffrey Sica:** Thank you all.
**Break**: \[28:38\]
**Adam Stacoviak:** So the Kubernetes API... That's what you work on, right?
**Eddie Zaneski:** I work on the CLI.
**Adam Stacoviak:** Oh, the CLI. Okay, that's an abstraction of that, right? You're actually interfacing with the API, with the CLI, right?
**Eddie Zaneski:** We're probably the biggest consumer of the API.
**Adam Stacoviak:** Okay... How does that work, the CLI?
**Eddie Zaneski:** So are you familiar with how the Kubernetes project is broken up into special interest groups?
**Adam Stacoviak:** School me. School me.
**Eddie Zaneski:** Yeah. So we've got to SIGs. So basically, every part of the Kubernetes codebase --
**Adam Stacoviak:** What does a SIG mean?
**Eddie Zaneski:** Special Interest Group.
**Adam Stacoviak:** Okay.
**Eddie Zaneski:** So we've got a SIG for API machinery; they own the API and the stuff that runs on the master nodes... So I work on SIG CLI, which is the SIG for the command line tooling. So it's kubectl, customize, KUI, which is a like GUI framework for kubectl... A couple other sub-projects... But yeah, so I've bee...
**Jerod Santo:** Kubectl, huh?
**Eddie Zaneski:** Yeah.
**Jerod Santo:** Is that official?
**Eddie Zaneski:** Well, you all noticed throughout this talk I say it many different ways on purpose, so...
**Jerod Santo:** Okay. So you rotate.
**Eddie Zaneski:** You just called me out early.
**Jerod Santo:** You're a diplomat.
**Adam Stacoviak:** So if you say kube cuttle here in a bit - that's on purpose.
**Eddie Zaneski:** I'm also gonna say Cub Ektal, so...
**Jerod Santo:** Cub Ektal. \[unintelligible 00:34:04.00\]
**Adam Stacoviak:** Oh, gosh. Who says Cub Ektal?
**Jerod Santo:** Well, if you wanna hit all the variations...
**Adam Stacoviak:** People say Cub Ektal?
**Eddie Zaneski:** Yup.
**Adam Stacoviak:** Is it for fun, or is it for serious?
**Eddie Zaneski:** I've heard both ways. \[laughs\]
**Jerod Santo:** Wow...
**Adam Stacoviak:** Why not, right? If you can interpret something 17 ways, why not be 18?
**Eddie Zaneski:** It's true.
**Jerod Santo:** I just think that maybe Kubernetes is so complex and intimidating that whenever we have people on to talk about it, we just bike-shed the kubectl thing. What do you think?
**Adam Stacoviak:** Sure.
**Jerod Santo:** I feel like you and I always end up right here, talking about the kubectl.
**Adam Stacoviak:** For sure. I mean --
**Eddie Zaneski:** You can go to kubectl.info, and it's a recording of Tim Hockin who originally wrote it saying how he pronounces it.
**Jerod Santo:** I think we had Tim on the show back in the day.