text
stringlengths
0
2.46k
[543.06 --> 544.26] No, I'm...
[544.26 --> 548.14] Honestly, it's over all projects because I'm interacting with projects at every different
[548.14 --> 548.42] level.
[548.56 --> 550.68] It's just, I don't want to say I'm in charge of all of them.
[550.80 --> 551.92] That's not true at all.
[552.32 --> 558.76] But I would say I communicate with all of them and I'm trying to help the CNCF work with
[558.76 --> 559.86] projects in a better way.
[560.22 --> 560.48] Gotcha.
[561.18 --> 562.52] Give us an example.
[562.64 --> 564.40] How does that play out for recent?
[565.40 --> 570.94] Recently, when I joined and one of the things that I've been really pushing for is a lot
[570.94 --> 577.18] of the processes to grant projects access to cloud resources that are like group cloud
[577.18 --> 582.80] resources under the CNCF or we have license scanning software or services.
[582.80 --> 587.08] We want to give those to the projects and then step out of the way.
[587.22 --> 589.36] Hey, we don't want to be the bottleneck.
[589.92 --> 594.38] But most of the way that we grant that access is still a manual process.
[594.38 --> 596.40] Even though all of these things have APIs.
[596.90 --> 602.04] Well, gee, you know, you look at what Kubernetes has done with their like community management,
[602.20 --> 608.00] like creating a user group in Slack is memes aside, like laugh, laugh at home.
[608.00 --> 610.36] You edit a YAML file.
[610.52 --> 614.34] Oh, you're joining a GitHub group or you've become like a SIG chair.
[614.48 --> 615.70] You're editing a YAML file.
[615.82 --> 619.38] And then once that file is committed, it's just GitOps all the way down.
[619.38 --> 623.62] Like your access gets granted in GitHub, your access gets granted in Slack, all of that.
[624.20 --> 628.18] Why don't we do that for all of these services that the CNCF is like hosting?
[628.52 --> 630.40] Right now, it's still ClickOps.
[631.08 --> 636.78] That was cool when the like the foundation was 10 projects or 15 projects or at 160.
[637.66 --> 638.56] 160 projects?
[638.88 --> 640.46] And we're not slowing down.
[640.56 --> 641.86] And 12 more being added.
[641.96 --> 642.42] That's crazy.
[642.70 --> 643.58] Those are up for vote.
[644.06 --> 645.92] Those are up for TOC vote.
[645.96 --> 647.04] How many get rejected?
[647.04 --> 649.86] I actually don't have that off the top of my head.
[650.64 --> 654.34] I would be willing to guess sandbox wise.
[654.46 --> 658.90] It's probably 75% acceptance rate, but please do not hold me to that right now.
[658.90 --> 659.54] Nine out of 12 are getting in.
[660.32 --> 660.76] Don't.
[660.84 --> 661.56] Hey, hey, hey.
[662.14 --> 663.34] We're not naming names.
[663.74 --> 665.98] What is the, I guess, motivation?
[666.14 --> 671.04] Probably might be the best word, but what does the CNCF do in terms of like you got 160 projects.
[671.38 --> 672.38] What's the long-term goal?
[672.42 --> 673.76] Is it to be bigger than that?
[673.76 --> 677.16] Like what service do you provide to the cloud native world?
[677.28 --> 679.50] Like what is it that you all do or hope to do?
[680.72 --> 685.50] This is going to be interesting because if you ask different people in the CNCF, you might get a different answer.
[685.62 --> 688.10] And there might be a canned response and I should know it.
[688.10 --> 701.46] My answer is there is, aside from the couple stable patterns, like Kubernetes and the way that it has an API and like declarative over imperative stuff, everything's stable right now.
[701.72 --> 703.36] Like that pattern is established.
[703.86 --> 709.66] What things and what problems when consuming that pattern need to be solved?
[709.66 --> 718.16] What, like a good example was, okay, so now we can create all of these containers and orchestrate them in a meaningful way.
[718.28 --> 720.12] But now we have a giant distributed system.
[720.76 --> 723.68] What do we do in order to monitor that thing?
[723.82 --> 725.18] Well, Prometheus came out of that.
[725.18 --> 731.08] So this is a long-winded way of saying we have this, you know, foundational technology.
[731.26 --> 737.44] At this point, we are accepting additional projects to help flesh out what cloud native actually means.
[737.64 --> 740.36] And the definition itself is evolving.
[740.74 --> 740.84] Yeah.
[740.92 --> 743.30] Like we have a bunch of WebAssembly projects.
[743.38 --> 744.14] Well, why is that?
[744.14 --> 754.32] Because at its core, WebAssembly is, I don't want to say just another container runtime because that would be bad, but it is another like application runtime.
[754.82 --> 756.28] You build it a different way.
[756.42 --> 760.06] It has a very different like look and feel than a container.
[760.46 --> 764.70] But still like that, that idea still fits into the pattern of cloud native.
[764.98 --> 766.52] So that still solves a problem.
[767.38 --> 769.84] So, geez, what would I do?
[769.84 --> 777.06] TLDR, we're accepting a bunch of projects because not all of the problems or questions have been answered in what cloud native is.
[777.42 --> 783.04] So you're attempting to and in many ways succeeding in defining the foundation of cloud native.
[783.20 --> 783.32] Yeah.
[783.84 --> 790.20] And everything was originally built on Kubernetes because that's what I guess was the founding project that really kicked off.
[790.42 --> 792.22] So we come back from the Dan Kahn days.
[792.34 --> 794.92] Like we were early CNCF days, Michigan.
[794.92 --> 802.04] Dan Kahn, Dan, but like we were there when it was just just two or three projects, you know, a very small CNCF, the original founding days.
[802.50 --> 806.26] And as we see it grow and grow over time, you know, it's a lot of great stuff happening for open source.
[806.36 --> 808.00] But, you know, you're on the inside.
[808.08 --> 808.72] You see what's happening.
[808.80 --> 810.76] You are in touch with all these projects.
[810.88 --> 811.60] What is the mission?
[812.18 --> 814.04] Like what is the end game for CNCF?
[815.42 --> 816.90] Jeez.
[817.22 --> 817.46] Three.
[819.22 --> 821.54] Honestly, it's what is next?
[821.54 --> 827.64] The definition of cloud native in a nutshell is really doing distributive computing in a repeatable way.
[828.92 --> 831.34] I mean, that's my definition in my old noggin, right?
[831.72 --> 835.56] But that doesn't mean always use Kubernetes.
[836.68 --> 837.12] Sure.
[837.28 --> 837.86] Right now.
[837.94 --> 839.18] Hey, Kubernetes is.
[839.62 --> 841.14] I mean, you look at all the stats.
[841.70 --> 844.10] Adoption's still like up into the right.
[844.18 --> 845.00] It's a hockey stick.
[846.42 --> 850.60] That doesn't necessarily mean it's going to be the same thing or it's going to be the answer.
[850.60 --> 853.06] So, like, what is the end goal?
[853.24 --> 863.84] We don't really have an end goal aside from if you are doing some sort of distributed computing, like trying to solve or consume or build distributed computing, distributed platforms.
[864.40 --> 868.66] How can we do it but make sure that how it's being done is in an open source way?
[869.02 --> 872.12] Maybe Kubernetes, you know, goes by the wayside and something else comes up.
[872.12 --> 879.62] Maybe there is some new, like, WebAssembly orchestration platform and then everyone starts adopting that.
[879.72 --> 881.90] We want to make sure that that's still possible.