text
stringlengths
0
1.8k
**Dan Mangum:** I believe you need an actual replace stanza down there at the bottom.
**Gerhard Lazu:** You think?
**Dan Mangum:** I believe so...
**Gerhard Lazu:** Okay. This is a require. So the way I understand it, I need to replace this, with this.
**Dan Mangum:** No, I believe that you'll have a dependency there on HashiCorp Terraform plugin SDK, and then you'll have a replace statement at the bottom of the go mod, that indicates you want to replace that dependency that's in your require with the fork there that Hassan has.
**Gerhard Lazu:** Okay. So you're saying that all I need to do is comment out this line. This replace.
**Dan Mangum:** Yup, that should be what we're looking for here.
**Gerhard Lazu:** Okay. I wasn't sure that go mod supports this...
**Dan Mangum:** Yup.
**Gerhard Lazu:** ...but okay. Yeah, okay. They're more tidy.
**Dan Mangum:** I believe here is where we need to setup whatever the credentials are needed to talk to Linode...
**Gerhard Lazu:** I see.
**Dan Mangum:** So we may want to do the same thing that the Terraform provider is doing, but --
**Gerhard Lazu:** I see what you mean. Okay, I'm with you.
**Dan Mangum:** Yeah.
**Gerhard Lazu:** So the only thing that we really need is a key.
**Dan Mangum:** To talk to Linode?
**Gerhard Lazu:** Yeah. That's the only thing.
**Dan Mangum:** Cool.
**Gerhard Lazu:** I would call it CLI token, because that maps it to what the Linode CLI expects it to be.
**Dan Mangum:** Is that what you use with Terraform to be able to authenticate?
**Gerhard Lazu:** I don't know.
**Dan Mangum:** Because I believe what we're doing here - so we're taking things out of the provider config and then setting the environment variable based on that, so when the underlying Terraform plugin is invoked, it will utilize those credentials specified by the environment variables.
**Gerhard Lazu:** Yup. Let's see... Linode token.
**Dan Mangum:** Nice. So I'm guessing that's what we want there.
**Gerhard Lazu:** That's what we want, yeah. Where does this key come from? Hang on, let me see. Key username. Where does this key come from?
**Dan Mangum:** You just deleted the variable that was key username... But you can name it whatever -- sorry, it was way up at the top.
**Gerhard Lazu:** Ah, nftoken. I see, okay.
**Dan Mangum:** Yup, that sounds good. I also am gonna have to wrap up here pretty soon...
**Gerhard Lazu:** Okay, let's wrap up now.
**Dan Mangum:** Okay.
**Gerhard Lazu:** Yeah, let's wrap up now. I think this is a good point.
**Gerhard Lazu:** After the pairing session with Dan, I had a few more with Muvaffak Onuş, one of the Terrajet creators. And then he joined me to talk about the end result.
**Muvaffak Onuş:** Yeah, I'm glad to be here.
**Gerhard Lazu:** We had a couple of early mornings, and I think I had a couple of late nights... So why did we do this? The reason why we did this is because we wanted our Kubernetes clusters to not be provisioned via UI or CLI. So no ClickOps, Dan; that was a great word. No ClickOps, no UI, and not even CLI. We didn'...
**Muvaffak Onuş:** Well, so you see, in the Crossplane ecosystem there are many providers, and not all of them have support for all APIs that clouds actually expose.
**Gerhard Lazu:** Right.
**Muvaffak Onuş:** And one of the examples was Linode. We didn't have it provided. Also, the plan with Terrajet, the motivation was that "Let's build something that can utilize the whole great Terraform community and the great work that they did." So that was how it came to be. Design a code generator and a generic con...
**Gerhard Lazu:** \[01:04:02.21\] Right. So this is full-circle happening. Markus, if you're listening to this - this is what happened with your Terraform provider. I remember I worked with Markus while he was still at Linode. We were using Terraform to provision the instances, which were running Docker at the time, to...
So that's what we're using as a generator for a Linode provider that uses Terraform. So - okay... How many providers have been generated with Terrajet to date, and where can we see them?
**Muvaffak Onuş:** Yeah, so today we have the provider for the big three, AWS, Azure and GCP, and those three providers have almost 2,000 CRDsin total.
**Gerhard Lazu:** Right.
**Muvaffak Onuş:** And then if you go to Crossplane Contrib, you will see other providers, similar to like Jet Linode; for example, we have Equinix, Equinix Metal, we have Exoscale... All of these are completely bootstrapped by the community. So I would say in total like seven or eight right now.
**Gerhard Lazu:** Okay. Yeah, there's quite a few providers... TF, Equinix, I can see that; provider Helm, provider Civo... What else am I seeing here? Provider Jet AWS - this is an interesting one. So even though you have an AWS provider, there's also a Provider Jet AWS. Do you know the story behind that?
**Muvaffak Onuş:** So the provider AWS, the one that calls APIs directly, has around 100 CRDs, which means perhaps 100 services... But AWS has hundreds. So if you look at that Jet AWS, you will see it has 765 custom resource definitions, which is, you know, just too many for the Kubernetes community at this point.
**Gerhard Lazu:** Yeah. I can imagine having so many CRDs in your Kubernetes. You wouldn't even know which one to pick; there's just so many of them. Okay, so that makes sense. And we added another provider, haven't we? In the last week.
**Muvaffak Onuş:** Yes.
**Gerhard Lazu:** That was amazing. 12 commits, that's all it took to generate a provider Jet Linode, which is Crossplane Contrib. This is, by the way, our gift to you, our Christmas gift to you. If you want to provision Linode Kubernetes Engine clusters using Crossplane, this is the modern way of doing it... Because h...
**Muvaffak Onuş:** Yes.
**Gerhard Lazu:** And that is the LKE resource. Linode LKE cluster. Now, if you want more resources, contribute. It's an open source repository, public to everyone. So if there's anything missing, what I would like to see is a Linode instance. I would like to provision some Linode instances, some VMs with this. So that...