Datasets:
willtheorangeguy
/
2021-Ship-It-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
1.8k
[3953.80 --> 3954.82] ProviderJet AWS.
[3955.08 --> 3956.16] This is an interesting one.
[3956.22 --> 3959.74] So, even though you have an AWS provider, there's also a ProviderJet AWS.
[3959.94 --> 3961.06] Do you know the story behind that?
[3961.06 --> 3967.38] So, the Provider AWS, the one that calls APIs directly, has around 100 CRDs.
[3967.48 --> 3967.72] Okay.
[3967.84 --> 3970.36] Which means like you know it maps 100 services.
[3970.54 --> 3972.60] But AWS has like you know hundreds.
[3973.10 --> 3979.12] So, if you look at that Jet AWS, you will see it has 765 custom resource definition.
[3980.20 --> 3984.84] Which is like you know just too many for Kubernetes community at this point.
[3985.10 --> 3987.62] I can imagine having so many CRDs in your Kubernetes.
[3987.62 --> 3990.10] Like you wouldn't even know which one to pick.
[3990.20 --> 3991.48] I mean there's just so many of them.
[3991.58 --> 3991.74] Okay.
[3991.82 --> 3992.56] So, that makes sense.
[3993.20 --> 3995.04] So, and we added another provider.
[3995.22 --> 3995.66] Haven't we?
[3995.88 --> 3996.80] In the last week.
[3997.66 --> 3997.90] Yes.
[3998.00 --> 3998.84] That was amazing.
[3999.16 --> 4000.98] Like 12 commits.
[4001.42 --> 4004.98] That's all it took to generate a ProviderJet Linode.
[4005.02 --> 4006.22] Which is in Crossplane Contrib.
[4006.28 --> 4007.80] This is by the way our gift to you.
[4007.86 --> 4008.86] Our Christmas gift to you.
[4009.00 --> 4012.54] If you want to provision Linode Kubernetes engine clusters using Crossplane.
[4013.26 --> 4014.72] This is the modern way of doing it.
[4015.20 --> 4015.42] Right.
[4015.46 --> 4018.38] Because Mark has built a Crossplane provider for Linode.
[4018.72 --> 4020.78] Which hasn't seen much maintenance I think.
[4020.94 --> 4022.88] The last update was a year ago.
[4022.96 --> 4023.64] Maybe a bit longer.
[4023.82 --> 4025.96] And I don't think it's working with the latest Crossplane versions.
[4026.16 --> 4027.42] Many things have changed since.
[4028.46 --> 4030.08] So, this one we know it works.
[4030.66 --> 4032.16] But it only has a single resource.
[4032.24 --> 4032.42] Right.
[4032.88 --> 4034.10] Because that's all that we needed.
[4034.10 --> 4036.38] And that is the LKE resource.
[4036.68 --> 4038.52] Linode LKE cluster.
[4039.32 --> 4041.20] Now, if you want more resources.
[4041.92 --> 4042.48] Contribute.
[4042.82 --> 4044.48] It's an open source repository.
[4044.68 --> 4045.52] Public to everyone.
[4045.74 --> 4046.94] So, if there's anything missing.
[4047.14 --> 4048.90] What I would like to see is a Linode instance.
[4049.40 --> 4051.86] I would like to provision some Linode instances and VMs with it.
[4051.98 --> 4054.62] So, that would be my request to anyone that's listening.
[4054.82 --> 4055.02] This.
[4055.22 --> 4055.82] Marcus maybe.
[4056.42 --> 4057.08] What do you think?
[4057.24 --> 4058.08] Or someone else.
[4058.62 --> 4059.36] But anyways.
[4059.44 --> 4059.84] It's there.
[4060.14 --> 4062.12] I'm wondering what is coming next for TerraJet.
[4062.12 --> 4064.08] So, TerraJet.
[4064.20 --> 4066.12] So, when we first started with TerraJet.
[4066.34 --> 4068.02] We had hit a problem.
[4068.90 --> 4071.78] With API server handling that many CRDs actually.
[4072.18 --> 4072.38] Right.
[4072.42 --> 4074.46] When you install 700 CRDs.
[4074.84 --> 4078.48] API server gets like unresponsive for like 40 minutes or something.
[4078.76 --> 4081.06] Which like, you know, affects all the workloads.
[4081.36 --> 4083.44] That it was supposed to schedule.
[4084.88 --> 4086.72] So, we have fixed that problem.
[4086.94 --> 4087.86] I mean, there was a patch.
[4087.96 --> 4090.62] And we accelerated some of the processes in upstream.
[4090.62 --> 4094.98] So, now we are able to use those Jet providers.
[4095.56 --> 4099.64] And in January, we will have a big splash of announcements.
[4099.84 --> 4100.14] Okay.
[4100.34 --> 4103.68] That will announce AWS, Azure, and GCP providers.
[4103.78 --> 4104.44] Jet providers.
[4105.06 --> 4107.94] With their like, you know, API groups stabilized.
[4108.78 --> 4109.84] Configures are stabilized.
[4109.96 --> 4112.24] And API fields are stabilized.
[4112.34 --> 4116.62] And then we will start making some of the resources version.
[4116.62 --> 4117.96] Version V1, beta 1.
[4118.28 --> 4118.54] Right.
[4118.54 --> 4120.42] Which has like, you know, more guarantees around that.
[4120.52 --> 4123.58] And then we will have conversion webhooks in cross-plane.
[4123.72 --> 4130.02] Which will affect like, you know, how easily we can make a resource.
[4130.16 --> 4134.12] Let's say that you're not happy with the implementation in Terraform provider.
[4134.66 --> 4135.98] You can just switch it to native.
[4136.20 --> 4136.48] Okay.
[4136.48 --> 4139.14] With API calls directly to AWS.
[4139.58 --> 4145.88] So, all this like, you know, new stuff that will allow community to bootstrap new providers.
[4146.12 --> 4149.22] And like, you know, make upstream work with them.
[4149.60 --> 4153.56] And then like, you know, it's just so many CRDs and built easily.
[4153.76 --> 4153.94] Yeah.
[4154.02 --> 4155.92] That you won't have a problem.
[4156.04 --> 4157.54] Like, you know, hey, is this resource supported?
[4157.74 --> 4158.94] Well, yes, probably.
[4159.32 --> 4163.22] Instead of like, you know, let me take a look at how it would be to implement it.
[4163.22 --> 4171.44] I do have to say, having gone from nothing, like I knew nothing about how to implement a cross-plane provider to using TerraJet.
[4171.76 --> 4173.04] That was really smooth.
[4173.24 --> 4177.98] I think anyone that is determined to write a cross-plane provider doesn't exist yet.
[4178.34 --> 4182.46] And there is a Terraform provider which exists, ours, and they can have it.
[4182.64 --> 4183.70] Which is amazing to see.
[4183.86 --> 4187.44] So, this is basically proof that your idea works.
[4187.62 --> 4188.08] Yeah.