text stringlengths 0 1.8k |
|---|
[4777.24 --> 4778.30] Yeah, Jared wouldn't do that. |
[4778.38 --> 4779.50] No, Jared wouldn't do that. |
[4779.84 --> 4780.66] No, he wouldn't. |
[4780.66 --> 4782.18] I do that all the time. |
[4782.18 --> 4784.20] You know, like, let's just take production down. |
[4784.58 --> 4785.14] You know, whatever. |
[4785.26 --> 4785.98] Let's see what happens. |
[4785.98 --> 4786.86] Just for the fun of it. |
[4787.22 --> 4791.86] So, what will this do behind the scenes with the new setup that we have? |
[4791.98 --> 4793.00] Can you tell us? |
[4793.56 --> 4793.82] Yes. |
[4793.96 --> 4800.26] So, what's going to happen is that the controller will reconcile and see that the cluster is not there. |
[4800.26 --> 4804.44] It's gone, which is like, you know, what happens when you first create the resource. |
[4805.08 --> 4810.12] The very first thing that a provider does is to check whether a resource is there and create it if not. |
[4810.24 --> 4810.34] Yeah. |
[4811.06 --> 4814.52] And it will be for the controller, it will be just like that. |
[4814.58 --> 4816.28] Hey, I checked the resource and it's not there. |
[4816.32 --> 4817.38] So, I need to create it. |
[4817.38 --> 4821.86] So, it goes ahead and tries to create a new cluster. |
[4822.18 --> 4822.28] Right. |
[4822.48 --> 4824.78] And that takes 30 seconds, a minute. |
[4825.08 --> 4827.98] How long does it take for it to figure out that, hey, I'm missing a cluster? |
[4828.36 --> 4838.58] Well, so, because it doesn't get any events or anything in Kubernetes cluster, it will need to hit the long wait period, which is like, you know, one minute. |
[4838.68 --> 4838.86] Yeah. |
[4838.86 --> 4843.50] So, at most in a minute, it will recognize that change. |
[4843.50 --> 4849.04] Or, you can make a change on the custom resource, which will trigger a Kubernetes event. |
[4849.40 --> 4853.52] You go to that controller and it will start all the processes there. |
[4854.06 --> 4857.40] So, I was trying to find this out to see where it's reconciling. |
[4857.48 --> 4858.34] It's finding it. |
[4858.66 --> 4860.22] I think I just missed it. |
[4860.72 --> 4863.10] The event, everything is synced now. |
[4863.52 --> 4863.72] Right. |
[4863.78 --> 4864.58] Everything's ready. |
[4864.84 --> 4865.68] The cluster's back. |
[4865.82 --> 4867.24] I mean, I just had to refresh the page. |
[4867.48 --> 4867.70] Nice. |
[4868.02 --> 4869.66] What about the Linodes? |
[4870.30 --> 4871.34] Is it still there? |
[4871.56 --> 4872.48] It's offline. |
[4872.48 --> 4872.56] Offline. |
[4873.20 --> 4873.68] Interesting. |
[4874.08 --> 4875.36] I don't know why that's offline. |
[4876.08 --> 4885.92] So, when I deleted the cluster, whatever happened behind the scenes, maybe the node pool, the default node pool got deleted as well. |
[4886.08 --> 4886.78] Oh, it's booting. |
[4887.02 --> 4890.52] So, I think that the node was deleted as well. |
[4890.76 --> 4893.44] And this is like the worker VM. |
[4893.92 --> 4895.86] And the new one was created. |
[4895.86 --> 4902.92] So, deleting the cluster from the Linode UI, from the cloud, linode.com, it also deletes all the worker nodes. |
[4903.28 --> 4906.70] So, when the cluster gets recreated, it has to obviously recreate all the nodes. |
[4906.78 --> 4907.30] And there it is. |
[4907.34 --> 4908.00] It's back. |
[4908.26 --> 4908.46] Okay. |
[4908.68 --> 4909.76] So, everything here is ready. |
[4909.88 --> 4910.36] It's synced. |
[4910.36 --> 4918.16] Because while the cluster has been created, like the object, the cluster object, the node pool that's associated with it hasn't been finished yet. |
[4918.22 --> 4920.70] And I think that's where composite resources come in. |
[4920.96 --> 4922.12] Can you tell us a bit about that? |
[4922.12 --> 4931.72] So, in other cases where you have the node group as represented as a different resource, you can actually have like, you know, two resources in a single composition. |
[4932.02 --> 4932.16] Right. |
[4932.54 --> 4938.68] And additionally, just like you mentioned earlier, we can have more things installed there as well. |
[4938.92 --> 4943.58] Because like, you know, the dependencies that are resolved automatically, just like, you know, Kubernetes. |
[4943.58 --> 4948.22] So, for example, you would create your composite cluster resource. |
[4948.66 --> 4951.42] Cluster will be created and node groups will be booted. |
[4952.12 --> 4953.42] And then the installations will start. |
[4953.54 --> 4953.64] Right. |
[4953.68 --> 4955.74] With provider kubeconfig or provider helm. |
[4956.48 --> 4962.40] So, like, you know, once your composite cluster CR reports ready, everything is ready. |
[4962.52 --> 4965.96] And like, you know, just back in its initial state. |
[4966.08 --> 4966.18] Yeah. |
[4966.32 --> 4971.80] So, it will just like, you know, revert it back to the original state, including all the things in composition. |
[4971.80 --> 4972.40] Okay. |
[4972.58 --> 4979.76] So, now what happened is we are targeting the same control plane and we could see how the pods were being recreated. |
[4979.92 --> 4983.54] So, 90 seconds ago, 100 seconds ago, everything was created from scratch. |
[4983.76 --> 4989.52] We accidentally, air quotes again, deleted the cluster, cross plane, recreated the cluster. |
[4989.80 --> 4990.76] The node pool was recreated. |
[4990.86 --> 4992.02] The node pool had a single node. |
[4992.54 --> 4994.32] And then everything was put back on it. |
[4994.38 --> 4995.96] Like, by default, what's there? |
[4995.96 --> 5007.36] What we would have been missing, if, for example, if we had added any extra resources, like ingress nginx or external DNS or all the other components that we need, those would no longer be present. |
[5007.52 --> 5009.42] Because, let's be honest, we deleted the cluster. |
[5009.80 --> 5011.18] And that should delete everything in it. |
[5011.36 --> 5017.26] And this is, I think, where a human, i.e. me, would have come in and like run commands. |
[5017.38 --> 5019.86] Oh, I have to get production back, you know, because it was deleted. |
[5019.86 --> 5023.22] But how amazing would it be if cross plane could do this? |
[5023.34 --> 5028.90] So, it would know, oh, it's not just a cluster which I need, it's all this extra stuff that needs to be present in the cluster. |
[5029.36 --> 5030.56] Now, that is really exciting. |
[5031.04 --> 5032.00] Next year, right? |
[5032.40 --> 5033.10] I think we did enough. |
[5033.12 --> 5033.26] Yep. |
[5033.42 --> 5034.62] I think we did enough this Christmas. |
[5035.34 --> 5035.74] Cool. |
[5036.22 --> 5036.68] All right. |
[5037.32 --> 5040.32] So, what happens next? |
[5041.00 --> 5041.90] What happens next? |
[5042.42 --> 5046.26] Well, I think there's a couple of improvements that we can do. |
[5046.26 --> 5051.18] I already mentioned about installing all like the base, having, I think, I think this is your idea. |
[5051.32 --> 5052.54] Can you tell us about your idea? |
[5052.88 --> 5054.82] Vafak, this is really, really good. |
[5055.10 --> 5055.82] The two compositions. |
[5056.36 --> 5059.82] So, maybe I can give a little summary about what composition does. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.