text
stringlengths
0
2.46k
[2911.58 --> 2912.86] So we did it a couple years ago.
[2912.98 --> 2917.94] We determined that it wasn't something we wanted to do or support at the time or had the capability.
[2918.16 --> 2920.12] So that just got revived two weeks ago.
[2920.12 --> 2926.80] And then the other thing, Kube Control is versioned as part of the Kubernetes project itself, right?
[2926.90 --> 2931.24] So 120, I can't release a separate version of Kube CTL.
[2931.32 --> 2931.34] That makes it harder.
[2931.34 --> 2931.98] That does, yeah.
[2932.06 --> 2932.24] Right?
[2932.32 --> 2935.58] So we do have a proposal out that probably needs to get revived.
[2935.68 --> 2937.06] But that was something we wanted to do.
[2937.18 --> 2940.58] But then you get the problem of the compatibility and SKU matrix.
[2941.12 --> 2944.34] What version of the client is supported by what version of the API server?
[2944.34 --> 2944.82] Yeah.
[2946.26 --> 2947.78] Useful software gets upgraded.
[2948.64 --> 2956.90] So if you, here's one thing we learned from GitHub and a lot of other things out there where it's like permission to mess up, permission to do something different.
[2956.90 --> 2970.46] You know, if you can release a different version of it in parallel that has what everybody wants and it fixes all the problems and maybe internally it's easier to develop and it's potentially easier to have contributors and easier to document.
[2970.72 --> 2972.90] Like that has potential.
[2973.56 --> 2978.24] There's an opportunity for that useful software just to get upgraded because, hey, this is just so useful.
[2978.58 --> 2978.72] Yeah.
[2978.82 --> 2979.96] This person is using it.
[2980.00 --> 2980.96] That company is using it.
[2981.54 --> 2985.56] And it's sort of like a social norm to upgrade because it's just useful.
[2985.56 --> 2985.96] Right.
[2985.96 --> 2992.92] The rewriting thing would probably get, like, it probably would be impossible to get through.
[2993.08 --> 2993.24] Right.
[2993.30 --> 2999.60] Because we do any significant changes to the project go through what we call the KEP process, the Kubernetes enhancement proposals.
[3000.02 --> 3005.54] And I could just see, like, opening a KEP for rewrite, kubectl, and just like, no.
[3006.12 --> 3007.00] It just gets closed.
[3007.14 --> 3007.34] Right.
[3007.64 --> 3007.80] Yeah.
[3007.82 --> 3008.88] What if you already did it?
[3009.02 --> 3010.12] What if we already did it?
[3010.24 --> 3010.88] That's what I was thinking.
[3010.98 --> 3011.72] I mean, it's not stuff.
[3011.72 --> 3014.20] First time contributor shows up, I rewrote this.
[3014.20 --> 3017.50] There's nothing stopping us or anyone from doing that.
[3017.50 --> 3017.66] Yeah.
[3018.12 --> 3024.42] The reality is we are changing the tires on a bus that's moving 1,000 miles an hour down the highway, right?
[3024.58 --> 3024.76] Right.
[3024.76 --> 3036.74] Maybe it actually turns into more like a yarn and NPM kind of situation where it's not you guys that rewrite it, but it's somebody else that comes alongside and says, well, we can write our own CLI against the Kubernetes API.
[3036.74 --> 3038.50] And here's seven ways it's better.
[3039.62 --> 3041.34] And, hey, who wants to use this?
[3041.42 --> 3049.78] And I don't know if you can actually, you know, just side install that sucker and use maybe it's kubectl with C-U-D-D-L-E or something, you know?
[3049.84 --> 3050.82] That's a conference now.
[3050.98 --> 3051.44] Oh, it is?
[3051.56 --> 3051.66] Yeah.
[3051.86 --> 3052.20] Dang it.
[3052.20 --> 3056.96] In a perfect world, the kubectl wouldn't exist, right?
[3057.00 --> 3057.70] Why is that?
[3057.90 --> 3062.48] Because it's, you can think of it like SSH for a server, right?
[3062.50 --> 3064.88] Like I don't want my developers SSHing to my server.
[3065.08 --> 3070.30] I don't want my developers pushing and making configuration changes to my production server.
[3070.52 --> 3075.62] I want a trusted build entity that is applying these changes after they've been reviewed.
[3075.62 --> 3079.44] And so it's just like, it's kind of giving a developer keys to the castle.
[3079.70 --> 3080.70] And I'd rather if I...
[3080.70 --> 3081.40] Deleting namespaces.
[3081.70 --> 3081.92] Yeah.
[3082.08 --> 3082.28] Right.
[3082.30 --> 3085.72] Like I'd rather not have to give people the client in the first place.
[3085.80 --> 3094.02] So I think instead of building one from scratch, I'd love to see us get to a point where the GitOps tooling and all this other stuff is in a place where you don't need it in the first place.
[3095.12 --> 3097.98] You can rewrite it in a different route.
[3098.26 --> 3098.44] Yeah.
[3098.80 --> 3099.60] You know, through...
[3099.60 --> 3100.24] Write something else.
[3100.36 --> 3102.66] In the GitOps world, build that thing to make it obsolete.
[3102.94 --> 3103.74] Yeah, that's fair.
[3104.14 --> 3105.30] Then you can take a vacation.
[3105.62 --> 3106.06] Yeah.
[3107.42 --> 3107.82] Yeah.
[3107.94 --> 3108.78] I would love one of those.
[3108.86 --> 3112.24] What I like about this podcast is we look at things like Yarn and NPM.
[3112.80 --> 3119.52] We look at, you know, we're not only in this cloud native specific world and, you know, sort of have tunnel vision.
[3119.64 --> 3122.26] We sort of see outside of all of software.
[3122.44 --> 3124.40] What was done here to solve that problem?
[3124.58 --> 3128.08] And what was wise about that choice that we can apply here?
[3128.50 --> 3131.94] You know, that's what I love about the conversation I think we get to have is that we...
[3131.94 --> 3137.24] Jared and I have the luxury and the privilege to speak at software at large, really.
[3137.50 --> 3137.74] Right.
[3137.80 --> 3138.06] You know?
[3138.28 --> 3141.72] Plus, we get to bike shed things but not actually be the person that has to go paint the bike shed.
[3141.80 --> 3142.10] That's right.
[3142.26 --> 3144.24] We can give you the idea of, hey, Eddie.
[3144.62 --> 3145.22] We're like...
[3145.22 --> 3146.04] Godspeed, bro.
[3146.04 --> 3148.62] I told Eddie to rewrite the thing and he just won't do it.
[3149.22 --> 3150.92] I got a good one for you all then.
[3151.04 --> 3154.30] So I also work on the build and test infrastructure for the project.
[3154.64 --> 3160.56] And we're unique as a project in that we handle distribution of all of our own artifacts and binaries.
[3161.04 --> 3163.40] And our artifacts aren't just binaries.
[3163.56 --> 3165.60] They're containers and OCI images, right?
[3165.60 --> 3169.12] So our CI bill is like $3 million a year.
[3169.62 --> 3172.12] Google gives us $3 million of GCP credit.
[3172.30 --> 3172.76] Shout out to them.
[3172.84 --> 3173.28] Thank you, Tim.
[3173.42 --> 3173.50] Wow.
[3174.42 --> 3183.06] And I think it costs us like $250,000 a month for storage and network ingress and compute and egress.
[3183.82 --> 3186.54] And we're working very hard to get that down, actually.
[3186.72 --> 3187.60] We just...
[3187.60 --> 3191.90] Amazon just also gave us a $3 million donation and we set up a registry proxy.
[3192.06 --> 3192.10] Yeah.