Yes, so welcome back everyone. We just went on a quick break because we had to get our speakers back here, but you would agree with me that since the beginning of today's section, we've had really exciting topics from introductory down to the expert level, and then we're back to understanding the basics of controllers and introduction to custom resources, which is going to be our next section. So buckle up everyone as we get our speaker on here. So the next section is going to be focused on extending Kubernetes and introducing custom resources, controllers, and operators. This is going to be taken by Ola de Paul Ajayi, who is a Cloud-native engineer. Currently at Continental Solution, helping businesses with Cloud-native transformation from beginning to the end and everything in between. It's good to have you here, DePaul. Thank you very much. Good to be here also. Awesome. All right. Yeah. Sorry for the delay, I think I am. I'll have more time to myself and interact, since I've started nearly. Yes. Yes, I feel so. Okay. Yeah. All right. Thank you very much. Everyone, my name is DePaul Ajayi. I'll be speaking on extending Kubernetes, introducing custom resources, custom controllers, operators, and schedulers. And if there is time, I'll be doing a simple demo where we're at it. Yeah. So for, like I said, my name is DePaul. I'm a Cloud-native engineer at Continental Solutions. I'm a Cloud-active engineer. I'm a DevOps engineer. I do everything on AWS and Azure. I'm also a software engineer when I can. I basically write Python and Golang. For now, I'm majorly focusing on building controllers and operators. Yeah, nice to meet you. So let's get to going. So yeah, what is Kubernetes? I don't want to focus so much on what Kubernetes is and its definition, but I'm going to mention just a couple of things.  It helps orchestrate containers, manages them, and their entire life cycle. Pretty much like that's a very simple definition of what Kubernetes is. Like I said, some of the features are it doesn't miss deployments, helps with auto-scaling, helps with self-healing. So for example, if your pod is down, it cannot just spin it all by itself. And it also helps with secret management and configuration management and so many things. But this are the basic things Kubernetes do. Wait, yeah, we are missing something. What's that? Yeah, Kubernetes is highly extensible. Yeah, that's right. So you can always add your new features, you can add whatever you need to do. And that is one of the key things that people don't talk about about Kubernetes is for. Yeah, like I mentioned, all of those things that I mentioned or I listed earlier, it's really awesome. But Kubernetes is being a very highly extensible system and what I mean is that you can add your own features. And if you go to Kubernetes GitHub repository because it's open source, there are really no patches, right? No request to add like basic major features, right? So if I as a company, I need a particular feature, right? On Kubernetes and it's not very good in the default installation, I can always add it myself because of this extensibility. And what actually makes this happen? What makes this I as the extensibility happen is because the all of Kubernetes is built on APIs. So everything you're saying from your part, your services and everything at APIs. So everything is communicating with API. You're communicating with Kubernetes through the API. You're doing Kubernetes communicating with itself through the Kubernetes API. And that's one of the real beauties of Kubernetes that is not being spoken so much about. So yeah, extending Kubernetes. What does, what do I mean when I say extending Kubernetes? Majorly what it means is that you're adding a new functionality like I mentioned earlier that is in part of your default Kubernetes installation. So if I have, if I decide to install maybe Kubernetes 1.22 for example, 1.201, there are a set of features that come with it. But then there are times when what you need, what you actually need is not included in this particular in the default installation. And you can also always add something to this. So yeah, that's what extending Kubernetes is in here. There are several ways Kubernetes can be extended like a lot of ways. But for this talk will be focused immediately on including endpoints and adding functionality to the Kubernetes API. I'll explain what this means as I go on and to become clear as I move on. But majorly focusing on creating endpoints and adding functionality to the endpoints pretty much. Very, very simple. So let's take it back. Let's take a step back and see. We've already defined what Kubernetes is right. But then let's look at something. I'm sure a couple of us will be familiar with this image. So this image is the Kubernetes cluster and the components that make up a Kubernetes cluster. Now, what we're seeing here is we have the control node or control plane, which is the left-hand side. Everything we deem that blue dotted line is the control plane. And all of those things are things that come packaged with every Kubernetes installation. So we have our controller manager here. We have our HCD. HCD is more like a storage that stores a key value pair of all of the resources, all of the resources within Kubernetes. So your port, your services, your deployment, all the information that Kubernetes needs to know to keep state of that resource is stored in HCD. And then we have the scheduler. The scheduler basically is what the scheduler does is it schedules ports to nodes simple. And then we have our cloud controller manager, which is majorly for cloud providers. So for example, we're looking at AKS in AWS or AKS in Azure or GKE in Google. They all have this feature whereby it makes it easy for them to be able to connect to the baseline infrastructure. So it's not a major part of the Kubernetes cluster, but it's majorly for cloud providers, people that need it, like I mentioned earlier. And then we have our work and nodes here. And those work and nodes majorly connect to the cluster through QCTL and Qproxy. So pretty much this is what you have for every default installation. And this, as you can see, the API sits at the center of everything. And the reason is because that is more like like the update of the cluster itself. Every communication that happens within the Kubernetes cluster, from outside the Kubernetes cluster into the cluster. For example, as a user I'm using QCTL, everything goes to the QCTL API server. And the API server itself, it's what exposes the Kubernetes API that we've been talking about since I began the talk. So yes, what is this? What is the Kubernetes API? Yeah, it's a set of Httpn points, like I mentioned. Majorly exposed by the API server in the control node or the control plane, like I mentioned earlier. And it sounds like an entry points which users or entities connect to the cluster. So users by like the DevOps engineer, Cloud engineer or a software engineer or entities like services within the cluster or maybe a easy to instance for example, just an example that needs to communicate with the cluster. All of these things happens through the API server. And this API server, API actually coordinates all the resources or object that are assessed within the cluster. Now, as you can see in the diagram below, we can see this is very similar to the image that we had initially, but then there's an attachment to the right hand side and that attachment is modest like showing how the Httpn points actually looks like. So we have some set of endpoints like the else, the metrics. So things like these are like common to applications where you can check the else and then get logs and metrics from the cluster. And then for very specific things like for example, pods around to get the list of my pods. Now, for example, in my cluster, the endpoint that will go to majorly is the API for slash API for education one, first large pods and I can use my Http verbs, my get, my list, my create, my update on all of this. And then those are the things, this is majorly is very familiar with us, right? Especially for software engineers that are used to creating API is an endpoint and all of that. So this is what is going on in the background that we are not seeing like a typical Kubernetes user is not seeing. So yeah, here we have it. So this is an example of the Kubernetes API. Now down to what we actually want to talk about the, talk about resources, very, like we said, there's this thing is actually true that the pod is like the simplest units, right? Being a cluster, within a Kubernetes cluster, right? But that's pod itself is actually a resource. And I can mention all resources in Kubernetes are endpoints. So when you think about your node resource, you think about your pod resource, you think about your service resource, you think about your namespace, you think about your volume and so many of that things, your job, your current jobs, anything you can think of, they are all endpoints. Like I've mentioned, I try to view them here. But now that's what is there. To be looking at the right-hand side of the slide right now, we would see there is a point where we have a Kubernetes object and something that isn't a Kubernetes object. Like I mentioned, everything is a resource, it's a Kubernetes resource, but not everything that is a Kubernetes object. And the difference majorly is, objects are usually like persistent entities. So for example, I create a resource type, I have a resource type which is namespace pods, right? And I created a resource instance with my YAML file, I do QCCI apply and I create a pod, right? That creation of pod is a resource instance. But what comes out of it, right? That pod instance that has this entire metadata and the ID and everything being persisted in HCD is Kubernetes object itself. So in comparison to what I do, like a QCCI or API resources command, for example, what this does is it lists a set of resources for us, right? It's a resource instance, but not an object. And the reason it's not an object is because it's not being persisted in the HCD, in the cluster. So it's just doing something, but it's not actually an entity that's doing something that needs to be monitored or controlled or will go back to when we need them. So that's the major difference between a Kubernetes object and instances, resource instances that are not objects. Now that we have an idea what a Kubernetes resources, what do we mean when we say what is a custom resource? Because that is what this talk is about. How do we extend Kubernetes to be able to create custom resources? So what are custom resources? Custom resources is majorly at end point, like we've mentioned in the Kubernetes API that allow the creation of custom objects, like I explained initially of a particular resource type. So in the previous slide, you saw how we created a Kubernetes object, a Kubernetes pod object, right? With a resource type of pod. So we can do the same thing for our custom resources and say, okay, I want to create a custom resource called full, full bar, something. And I want you to be able to create a Kubernetes object of type full bar, for example. And how do we do that? How do we say, okay, I'll add this full bar resource to my end points, my Kubernetes end points. And the way we do that is we use a Kubernetes with a custom resource definition. So a custom resource definition majorly is like a template. And what that template does is it's used to add end points to our resource to a Kubernetes API. And that's what it does. It had end points and it had fields and metadata that can be filled into that resource end points. So for example, the image that we have here, we have the ML file, which is the custom resource definition. It creates a custom resource as an end point. That's what we have in the middle. And anytime we call that end point, we can use that end point, which is the resource and a custom resource. And we can use it to create a lot of objects, a collection of Kubernetes API objects of that's custom resource type. So I'll take it again. I would create a custom resource of a particular resource type. Let's say full bar, like I said earlier, through the custom resource definition. Now, if I want to create an object of that resource type, I would have to query the custom resource end point to be able to create that object and to be able to query it, list it, get it, delete it, just the same way an API would work normally. Yeah, so for this, this is what we have for custom resources. But then they really don't do anything. Custom resources are just labels or let me say like string, for example. Now, when you do maybe A in programming, when you do A equals to quotation mark, A, B, C, D, that doesn't do anything. It's just a placeholder, right? So custom resources are like placeholder. They don't do anything. They don't have any power of their own. They cannot think by themselves, more like a caricature, if I can use that then. But what actually makes them do something, like for example, our pod now, we know that our pod object takes an image, right? Runs that image and then exposes a port and then an end point that we can access, the application that is running within that port, right? What makes that possible? And what makes that possible are controllers. Like I mentioned before, when we're looking at the things that were in the control plane, right? We talked about the controller manager. So the controller manager contains all the logic that all the resources are using, all the default resources. So by default resources, I mean, pods, namespace, nodes, table sets, deployments, stateful sets, how are they reconciled? What did they do? So controllers actually do that for us. So controllers are like our control loops that track a Kubernetes API type to make sure that that current state matches the desired state. So one thing I need to mention before we continue is that Kubernetes was built on an events-driven architecture. And what that means is that a controller, Kubernetes watches for changes to a particular event and then triggers the necessary things that needs to do based on that event. So for example, if I do a create event now, if I do QCTL upgrades or QCTL apply and then I pass in a file, a pod file, and I'm sending in an event to the Kubernetes cluster, it picks that up, looks at my file, gets the resource kind, and then passes it to the right controller. And the controller knows what to do by creating whatever it needs to do. So for our pod example, it looks at things like this is a pod kind or pod resource type. And what it does is it takes the schema, the name, the namespace, the container image, the container name, the container code, for example, and does something which is, and what we have is we have a container, a Tucker container, right, running, and then we can access it with the necessary metadata that was passed in to our pod YAML file. So that's how it works. So for controllers, a controller is that black box you are not seeing, right? When we do QCTL apply or QCTL get or QCTL describe, right? All of those things are part of the controller and the controller actually maintains that for us. So controllers will look at our desired state. So our desired state is what we send into Kubernetes. And the outcast state is what is actually happening within Kubernetes. So for example, if I send in a deployment type and I specify I want to have three or three instances of a particular image running, right? So that's my desired state, right? By the time I send it in, it starts with zero and then it increases to one, two, and three and then it stops. If any of the ports is deleted or maybe it's down for whatever reason, the actual state and desired state are no longer in sync. So in the controller, what the controller does is it makes sure that it returns the actual state of that particular resource into the desired state. So it continues doing that in a loop. But then instead of doing a loop and trying to make sure that everything works, it can overwhelm the system. So that's why they opted in for an event-driven architecture, right? But when there is a change, an event is sent and then the controller can take care of whatever is happening there. So yeah, we've talked about controllers. Now, custom controllers, which is what we want to talk about, right? Custom resources, like I mentioned, are just endpoints created by custom resource definitions. So they're just like an API that can query objects within them. They don't do anything more than that.  Like they become responsive, that's what I mean. And like I mentioned, Kubernetes uses a declarative programming model, which means that you need to take the viral state of the object you want to achieve. That is all you do. You don't care about what is happening in the background. Or you know that I have declared this and I expect Kubernetes to give me what I've declared, right? And because Kubernetes, custom controllers extend the functionality of the Kubernetes API on built-in resources, right? So I have a port now, for example, but I want to do more on it. Or I want to change the way ports behave. The way I do that is I create a controller that handles that logic for me, right? And that's what controllers do. They are used typically when a use case is not covered by the built-in controller manager for a built-in resource type. So very important for us to make true notes there is that they are used for use cases that are not covered by the built-in controller manager in our control plane for built-in resource type. By built-in resource types, the things I mean things like pods, namespaces, deployments, and so on. So like a typical example of when we want to use a custom controller is let's say that we have an application that uses a config map, right? So maybe send some environment variables into the containers that we are creating. So, but then there's always the possibility that those values can change. A typical manual process will have been if I need to make an update to my config map, right? I make the update to the config map with the key and value. And, but then what happens is that the pods that are running on that config map don't change because the values are being passed at runtime. Now for me to be able to make sure that the pods have the necessary things, I would have to go and stop the pod and then restart it, right? So that's the manual process that we need to do. Now we can create a controller that watches for the config map resource type and watches for changes to the config map values. When a controller detects a change to the value, it's automatically restart the pod for us. So that is one of the beauty of controllers. And that's why it has gained too much traction over the last three, four years because it's actually very, very, very reliable and very useful for some particular use cases like this one that we mentioned. So that's what custom controllers are. Yeah, in some way, custom controllers are written by you and what it's built in resources. So deployment, epic assets, and so on. And custom resources, they don't exist in the key controller manager. So what I mean is, like I mentioned, the key controller manager only contains controllers for default resource types, right? But then these controllers do not live in there. What that means is that, and they are independent of the cycle's life cycle, what that means is that I can deploy my controller somewhere else and it's just to be watching for changes to my Kubernetes cluster. So for example, if I delete, if a entire cluster goes down, for example, the controller has to be running. It might not just receive any event. And when you create your cluster again, you continue working. So it doesn't have to be deployed on your Kubernetes cluster. That's what this means. That's what this means. We can only separate it like a separate application that is clearing on its own. Yeah, so operators, yeah, so this is the next step to controllers and what they do. So operators majorly are built on top of the Kubernetes app abstraction. So automate the entire life cycle of the application they manage. So for example, we have Kubernetes resources that I've mentioned, controllers, concept for built-in resources like for a specific use case. Now, controllers are usually used for built-in resources, but operators majorly focus on custom object and custom resources. So like you mentioned, we have custom resources. We have custom objects that are created. The custom resource is being created by the custom resource definition. Now, when we take it a step back and we say, okay, yes, controllers control the life cycle of built-in resources. What about our own native custom resource types that are created and the objects we create through those resource types? That's where operators come in. So that's what they do. Custom controllers, right? They're pretty much almost the same thing, but they track and manage custom objects created by custom resource definitions. Operators are quite powerful in their use cases and they also help to automate the operations of your Kubernetes application, like more like an SRI tool and a software administrator for Kubernetes software application. Like the example I gave earlier, an SRI engineer will have needed to go and stop that board and restart it, right? But your controller, your operator will be able to do that for you automatically without you bothering or wondering about what's going on. So yeah, so this is the beauty of operators and why they are important, right? And why a lot of people have been getting on it. It's still going, it's still a very good community because it takes a lot of time to build an end-to-end operator. For the major operators that we have now, they're usually for major companies, cloud native, for maybe, for example, database is now for, let's say Postgres and DeRest. They probably are the ones using operators because it's quite developer intensive and time-intensive to build and to build the entire end-to-end process. But either way, we can always to build our own mini operators for the things that we need to do. Yeah, so for the last piece here, which is the course schedule as I mentioned, schedule as majorly or basically ensure that ports are assigned to the best possible available nodes. That's what they do. They don't do any other thing. They are not complex. That is the definition. Yeah, like I said, there's an in-built scheduler called the SKU scheduler, which handles most of the scenarios that we would need schedulers for, like most of the scenarios we need schedulers for. But there are times that there are use cases whereby the SKU scheduler would not be able to handle. And that's when we need to probably need to write our own scheduler and attach it to our Kubernetes cluster so that we can use that scheduler instead of the default SKU scheduler. So a typical example is maybe, for example, I have a deployment or a state-for-sets, right? And I want to be able to order outputs deployed across multiple zones. So let's assume I have a Kubernetes cluster, right? And I have multiple nodes. Let me select 10 or 15 availability zones. Across multiple places. And I have worker nodes in all of those zones. What is the scheduler? Direct scheduler that says, okay, this is the order in which I want these nodes, these ports to be deployed to these nodes.  So that is a typical example of what a custom scheduler does. Yeah, so that's what it does. The use cases for this one are usually not as much or as visible as that of controllers or operators, but then they can also be useful. Yeah, so in the first side or in the end side, we have, Kubernetes really has become like a major tool in the cloud native space, right? When you say, and a lot of people would say, when you say Kubernetes, you mean cloud native, right? So cloud native is like equals to cloud Kubernetes and the other way around. Because of its use of use and ability to scale workloads effectively with its right range of use cases by its robust API. So as the adoption of Kubernetes actually increases, there will be scenarios Kubernetes is not equipped to handle by default, but then that's where extensibility comes into play. And we can also always extend it any way we want in whatever fashion that we want to extend it. I'll do a quick demo on custom resources, custom resource definition and controllers, basically before I go. Let me share the right screen. All right, so what I'm going to do here, I hope it's clear enough. What I'm going to do here is I'm going to show us how custom resource is created through custom resource definitions and we'll see how a controller is being used. So this controller here is pretty much basic and simple. And what it does is it creates an engine next image without us specifying the engine next image. And so it's just very basic. It just shows our controllers actually work. Now, like I mentioned, there are a lot of custom resource types that we have in the default Kubernetes cluster. So let me show you a couple. So we can see a lot. I know that we're able to recognize some of these things that you can see nodes, you can see pods, you can see secret service account and so this are the default values for these default resource types for Kubernetes in Kubernetes, right? And now we want to create a new resource type called engine next operator. And so let's do something real quick. Let's see if we can find it within our resource types at the moment. So you can see that there's nothing like that because it didn't return anything. One thing we can do, like I mentioned, for a custom resource, custom resource, so what we need now is we need the custom resource definitions, right? And that custom resource definition, let me look for it, yes. So this is a typical example of what we would have in a custom resource definition. So you can see it's a, and again, custom resource definition is actually a custom resource type also, which is, but that's what makes it really beautiful. So yeah, using an API endpoint to create other API endpoints, right? So you can see it has a kind of custom resource definition it has the name. So this is going to be the name of a custom resource type and you can see a couple of things that have been mentioned, the group it belongs to, the plural form, which is NNS operator, singular form NGNX operator, and we are specifying that it's a namespace resource type. There are two types of resource types, there's namespace and cluster-wide. So cluster-wide operators that you don't need to specify in a namespace to be able to access them. But for namespace operator, you need to specify the namespace if it's in or it's being the default namespace or the whatever default namespace we specify on our Kubernetes cluster. And it shows the version and so many other things. So there's a lot of things going on here. So let me just mention one thing here. We can see the spec and so if you've played a lot with YAML files, Kubernetes YAML files will be familiar with what your spec is, right? So you can see a spec is asking for things like ports, which is the ports of the NGNX operator and the replica, number of replicas you want to have to know that to script, just like in deployments, right? So this is what it does. It's something to notice the status, status sum resource. It shows us, for example, if I have, if I say I want to have three replicas, for example, and I only have one, right? It's going to be, so this is the status pretty much where the actual state of that resource type is recorded. So if it's not aligning with the desired states, then the controller will be activated. So this is what it does. As you can see, we can't find anything that's with NGNX controller, NGNX custom resource here. So I'm going to add it now. So I've created, I've added my custom resource definition. Now, coming back here again, I can let me do the same command again to check. So as you can see now, and I have an NGNX resource type here with everything we need. Now, what's the next thing we need to do? So the next thing we need to do now is create our Kubernetes object, right? So yeah, let's go ahead and do that since we already have our custom resource type coming. So for our NGNX, no, not this one. Yeah, samples. So as you can see, we have a kind of NGNX operator here with the name this. I'm saying let's have two replicas and have a pot of pot 80. Yeah, all right. So let's do that. Keeps it here, apply, dash F, config, samples, operator, no one. Yeah, this one. Now, what happens is we've created our resource object. So let's see it. Yeah, yes, we have our object here. And you can see it was created 15 seconds ago. But then, this is our object is supposed to do what, this is our object is supposed to create two pots, just like deployments work. So let's see if it creates a pot for us or not. We can't see any pot being created. And the reason for this is because we do not have any controller behind it that's listening to activities of this resource type to know what to do. So like I said, it's just like a placeholder. Nothing happens. Like you're not seeing anything what's going on. So if I do, for example, QCTL, describe NGNX operator, you can see at the bottom, you can see there are no events coming in at the bottom. So nothing is going on. We don't know what's going on. So how do we make sure that what we have is actually going, is actually correct, fine. We will need to create a controller and deploy our controller. So for this term, I'm just going to run it. Like I said, to just show what I've said, I don't need to deploy my controller on Kubernetes. I can just run it as an application. So for this one, we are using Go, right, to write our controller. And this is the logic here. This is very simple, very basic. Just, this is all you need to run it. A lot of things, I won't spend time to explain what all of this is doing. But what you just need to know is that this is what we need. We are making use of the deployment resource type to create our pods. So there's this layer of our NGNX operator custom resource which is built on top of the deployment resource just to be able to create our pods. Now, for me to run, let me do this, make, I'm waiting for it to start running. So it's running now. It got, as you can see, we know initially when we did QTL get pod, nothing was running. Now we can see our NGNX operator pod actually running now. Let's test one more thing. So show that it's actually working the way, so let's delete one of these pods. So if I delete one of them, QTL, delete pod, let's just copy this and paste. Wait for it to return. Yes. Wait for it to return one of the pods. Let's see what happens. So what that means is that it's going to change stage rights, our stage. So if you do, because this is quite fast, it will probably be done by now. So we'll be able to see it. So it's already running again in these first seconds ago. So if we have done something like QTL, describe NGNX operator, what's the name of our operator again? So right now, okay, it's not returning any events for now, but then what we've done so far is that we can see that when we created our custom resource, right? We created, it's did our custom resource and we're able to create our objects. But then until we run the controller, none of the things, none of the things, the messages we sent in was actually implemented. And until we did it. So this is more like a typical example of a use case. Might not be a very good example, but then it's like an early world example of how we can use controllers in our daily activities or in applications. So yeah, but so yeah. So what we've covered today has just majorly been Kubernetes, custom resources, custom resource definitions, custom controllers, operators and custom schedulers. Yeah, so that's all for me. Thank you very much for having me. Well, thank you so much, Dipo Ajiye, for that excellent section. And that was a really informative one. If you were able to follow up on the demo, you must have cut up on that as well. Thank you so much for your introduction.


Today, we are building up 11 aircraft, so we've got two Apaches, three UH-60 Blackhawks, two Chinooks, and then three Medevac aircraft on here, support corps, and any air mission requests that they have. Moving our aircraft from port, so we took it off the boat here, and then we're flying it to Anderson Air Force Base, which is on the north side of the island. And that's where we're staging for any missions that we have. As far as preparation, we are taking the blades and putting them back on the aircraft, so we had to take off the blades in order to ship it from Alaska to here. So we are putting the blades back on, making sure that there's no corrosion from the seawater or anything like that, and just making sure that the aircraft's good to go before they fly to Anderson. I'd just like to highlight the hard work that our soldiers have been doing. It's pretty hot out here. It's way different than the temperatures we experienced in Alaska, but yesterday we were able to get almost all of our UH-60s ready to go in a very short amount of time. We have all of these aircraft off the port today, so just, again, just like to highlight their hard work and dedication in getting after it.


And welcome to episode scotaking yourself up against an opt that limits you into sharp ask yourself these questions from pursuing present ideas, a personal identity, cause of preconception as you investigate these questions. Cest when you explore process is something to experiment. There's a reason represent that's what you'll feel as your new awareness. Try some bubble wrap sound.


15% of the world's population is a part of the Rh-negative bloodline. This means that they don't have the rhesus factor in their blood. It also happens to be the bloodline of our royal families of Europe and some of our past and current presidents. As spooky as that may seem, this is not unfamiliar to our ancestors. You see, our ancestors believed in something called divine right, that these ruling elites had a particular bloodline that was special, and therefore they were sent by God to divinely rule over us. In the past video, we talked about King Charles I of England and his execution, and apparently a lot of the onlookers collected some of his blood and handkerchiefs, and his blood then went on to cause miracles all over the English countryside, developing a bit of a cult around the executed King Charles I. Well, something very similar happened in France to King Louis XVI, when he himself was executed by decapitation. Oddly enough, the execution of Louis XVI in 1793 might be the exact thing that proves to us if the head found in the attic of a Frenchman in 2008 is or is not the head of the late King Henry IV of France. And it all comes down to that magical bloodline. But before we go any further, you know what to do. Please hit that subscribe button and give us a like. Again, thank you so much to all of our patrons for your support. If you would like to join our Patreon community, there is a link down in the description box below. Welcome to Esoteric Atlanta. My name is Bryce, and today on Mystery Monday, we're going to go into part two of King Henry IV's decapitated head. If you are further into the story, you need to go back and watch part one if you have not done so. Part one aired on Friday. And in part one, we talked about, briefly talked about the life of King Henry IV. But just a bit of a recap for those who did see Friday's video. King Henry IV of France or King Henri IV of France died in 1610. He died because he was assassinated in a traffic jam. Now I find it kind of funny that they had traffic jams back in 1600s with buggies. I hate traffic so much, and I live in one of the worst congested cities in all of America for traffic. But anyway, just thought that was a little funny. But King Henry IV was in his carriage going to see a sick friend when his carriage got stopped in a traffic jam, when a man named François Ravelec jumped into the carriage and stabbed the king to death. Now François was a devout Catholic. And King Henry IV, his whole life had been involved in this France's war of religion between the Huguenots and the Catholics. And King Henry had been a Huguenot for most of his life and only converted to Catholicism when he actually took the throne of France. King Henry was the king to sign the Edict of Nauts that actually gave Protestants equal rights to Catholics. So even though he himself had converted to Catholicism, he pissed off a lot of Catholics by signing this edict. Now before he was assassinated in 1610, there had already been 17 attempts on his life. King Henry IV of France's decapitation happened, however, in 1793, well over 100 years after his assassination. His decapitation happened in the same year that his great-great-grandson, King Louis XVI himself, was executed during the French Revolution.  Now during the French Revolution, just to sum it up from our last video, a lot of the French people went and pulled up, dug up a lot of the bodies of deceased royal family members and basically tore apart their bodies and kind of threw their bodies around. The French people were freaking sick and tired of this divine right in the way that the monarchy had treated them. After King Henry IV's head was removed from his body post-mortem, just like Oliver Cromwell and Oliver Cromwell's traveling head as well, which that video was linked below too, his head ended up moving from private collector to private collector to private collector. By this point, his head was mummified, so it stayed together pretty well, way better than Oliver Cromwell's head stayed together. But nonetheless, by 2008, it ended up in the attic of a Frenchman. The Frenchman ended up turning the head over to determine whether or not this was actually Henry IV or not. In the meantime, another family had also inherited a very strange object. This family had inherited a jar that contained a handkerchief with the blood, the supposed blood of King Louis XVI. Apparently, this family's ancestor had been present for the execution of King Louis XVI, and once his head was chopped off and blood sprayed everywhere, their ancestor used his handkerchief to wipe up some of the blood. This is exactly the same thing that happened with King Charles I over in England, where people wiped up the blood with their handkerchiefs.  Anyway, the people still were indoctrinated to believe that the royal family had special blood. Therefore, collecting the blood was good luck. Well, a few years ago, the family that had collected this jar with this handkerchief, this bloody, dried up, gross handkerchief decided that they were going to send this jar and handkerchief to a geneticist in Barcelona to have the blood tested. At first, all the geneticists could tell was that this was the blood of a European man with blue eyes. Another note, something very interesting about the RH negative blood line that we spoke about in the intro is that a lot of people, majority people who carry the RH negative bloodline do have blue eyes and blonde reddish hair. As you'll know, I am RH negative as well. I do descend from the English royal family, which is also kind of the French family too because they intermarried and basically we're all the same family. At first, the geneticists could only tell the family that he knew Louis XVI had blue eyes and obviously was a male, so that was really the only conclusive stuff he could find. However, he was aware that someone had recently turned in a skull ahead that allegedly might possibly be the head of King Henry IV, which would have been King Louis XVI. Great, great grandfather. This geneticist from Barcelona requested to take some of the mummified head to try to find the Y chromosome, the male chromosome to see if he could match it with the blood sample he had retrieved from this handkerchief. And lo and behold, the mummified heads, DNA, and the blood were a match. You could tell that these two people were related just like a great, great grandfather and a great, great grandson would be related. Now before that, the people who had the head had done a genetic reconstruction of the head of the skull to try to figure out what this person would have looked like. They could tell that there was a mole on one of the nostrils and that the ear, the right ear, had been pierced. Both two things that were present on King Henry IV of France. So at this point, it was looking like the skull had verified that the blood was indeed the blood of King Louis XVI and the blood of King Louis XVI on the handkerchief proved that the skull was indeed the skull of King Henry IV. Then along came a French historian named Philippe Delorne. Have no idea if I'm saying his last name right or not. I apologize if I did not say that right. Again, I am not a French speaker. So we're just going to call him Philippe. Well, Philippe wasn't buying it. He did not think the skull or the handkerchief belonged to anybody in the royal family. He believed that because the handkerchief and the skull were so old that any genetic testing could not be conclusive. So he teamed up with another geneticist from Belgium to try to track down any descendants of the House of Bourbon to test their DNA against the DNA of the skull and of course the DNA of the handkerchief. They found three different descendants from different branches of the House of Bourbon, three different males, and they tested all their DNA together to find the same that the comparative Y chromosome to be the House of Bourbon Y chromosome that they were going to use to compare against these two old relics. And as it turned out, the DNA from the descendants did not match the skull or the handkerchief. So therefore, a lot of people believed that this skull and handkerchief had nothing to do with the royal family since the descendants did not match these relics that were alleged to belong to their ancestors. However, we have another twist in the story. We know that Louis the 16th and his wife Marie-Antoinette were obviously executed during the French Revolution. We don't know truly what happened to their children. However, we do know that at least one of their children survived and they ended up creating the Paysor family, which is one of the most crooked and controlling, ruling families of our shadow deep state today. If this French historian Philippe and this geneticist from Belgium had tested one of the Paysor's DNA, that DNA could have matched, possibly could have matched the skull of King Louis IV or this skull we have and this handkerchief. But the fact that they tested three other people, well, these three people, they come from the line of Philippe the 1st, who was the younger brother of King Louis the 14th, the Sun King, who possibly had a twin brother, who possibly was the man in the iron mask. Philippe was born in 1640. He was the son of King Louis the 13th and of Austria, again, as we spoke about in our episode on the man in the iron mask. That means that King Henry IV was Philippe's grandfather. That also means that Philippe was the great uncle of Louis the 16th. Now, Philippe was married twice and apparently had a lot of children between his two wives. These are the descendants that they tested that are alive today. However, Philippe the 1st was a homosexual. He was open about it. It's very interesting to read the history books to read about him as I did when I was studying this case. He was extremely open about his sexuality. In fact, his mother and of Austria encouraged his sexuality. She encouraged him to cross dress. She would dress him as a little girl when he was young. She was even quoted as calling him my little girl. Now, there's a lot to say about this. First of all, I don't think that these descendants that they tested were actually the descendants of the House of Bourbon, even though that's the house they're in today. I don't think that they were Philippe's descendants. Yes, he was married twice and yes, his wives were a noble blood, but I don't think he was able to actually create a baby with a woman and back in those days, they didn't have such thing as DNA testing. So as long as you got a serigant to impregnate your wife in order to carry on the nobility, and as long as that serigant maybe looked a little bit like you, then no harm, no foul. We talked about the idea of a serigant with the man in the iron mask that many people believed the man in the iron mask could have possibly been the serigant father of Louis XIV. However, to conclude with this little theory with Philippe actually goes back to the man in the iron mask. Many people believe that Anne of Austria encouraged Philippe's homosexuality and cross dressing because at that point he was not a threat to his brother, Louis XIV's reign. Yes, we know throughout history as we talked about with the War of the Roses over in England, families, cousins, brothers have always fought each other for the throne. However, with the idea that Louis XIV could have had his twin brother put in an iron mask as to not usurp his throne, the Navy Anne of Austria kind of knew that if her youngest son was homosexual, then her oldest son would not torture him in order to stop him from taking the throne from him.  I also find it interesting that with the blood on the handkerchief allegedly belonging to Louis XVI and the skull allegedly belonging to Henry IV and there's a DNA connection. This excludes one of our theories with the man in the iron mask. And again, that is the theory that the man in the iron mask was a serigant because Henry IV was Louis XIII's father. Louis XIII was then father to Louis XIV, who was then father to Louis XV, who was then father to Louis XVI. If Louis XIII got a serigant to impregnate Anne of Austria for Louis XIV to be born, then Henry IV's DNA on his skull would not match the blood on the handkerchief. So we've got in my opinion one theory in the man in the iron mask thrown out. It was not a serigant father, but going back to the skull and to the handkerchief in my opinion, in my uneducated, nonbiological, I'm not a scientist, I'm not a geneticist, and I'm not a historian in my just layman opinion. I believe that the descendants they tested for the House of Bourbon were only descendants in name. I don't believe Philippe actually sired any children. Again, I did a huge dive into Philippe on my own to try to come up with my own opinion. And even though I was not there at the time, it really just does not seem like Philippe was interested and women at all and could have gotten a woman pregnant. If you know what I mean. Again, this was the 1600s, so there was no intervitual fertilization or anything like that. They did not have that technology to get someone pregnant.  I just do not believe from what I read of Philippe, what I studied of him. I don't believe he had it in him. I don't think that was his cup of tea. So these descendants are not descendants of King Henry IV or related to Louis the 16th. I believe from my studies that the skull did belong to King Henry IV and the blood is the blood of Louis the 16th. They're connected. Their DNA is connected. This geneticist in Barcelona figured it out. They're connected. How what a coincidence, right? If they're not who they say they are, then out of all the millions of people that have been on this planet, how the hell would you the likelihood of finding some random skull and some random handkerchief of blood and do a DNA analysis and find that they are relatives of each other that I mean the possibilities of that happening just to some random people are so slim. But the fact that this skull was rumored to be King Henry IV and we know that the bodies were pulled apart in 1793. The fact that this other family was told generation after generation after generation after generation that this jar had a handkerchief with the blood of Louis the 16th. That makes all the sense to me. These objects prove each other legitimate. These descendants, however, only go to prove that they aren't actually descendants. Now again, to make it super conclusive, you would probably have to take the DNA of some of the Pesor people, but my hope as those people are probably already arrested for crimes against humanity. That's just my hope and prayer though, because the Pesors are not that great of people. But anyway, my opinion, allegedly they are not that great of people. But what are your thoughts? Do you have you heard of the head of King Henry IV of France and this bloodied cloth from Louis the 16th's execution? Excuse me. What are your thoughts? Do you think, do you believe the scientist from Barcelona, are you more inclined with the French to story and to think there's something more to the story? What do you think about Philippe I? Do you think that he could have sired children and that disproves these objects belong to the royal family? Thank you once again to Josh McKay for doing our music for this channel and thank you to Todd Roderick for helping me get this video out to you guys. Again, if you would like to purchase the opening song, there is a link down in the description box below. I hope you guys have a fantastic week ahead and I will talk to you soon. Bye.


how are you guys doing? Yes, you read the title correctly. I'm going to attempt to wrap my hair and we're going to do a good old chit chat. So this is a flat iron. The video for this is coming soon. This is a good old nasty old flat iron. Got my gray hair. I'm getting so much gray hair. I seriously I'm going to pluck that out. I know I know you're not supposed to pull on but I am this is this is ridiculous. Look at that. Look at that. This is a chit chat. Y'all know how we do this. I talk about what's going on my personal life, what I'm watching on YouTube, which is not a lot and what I'm watching on TV. So yes, this is Hall. This is the flat iron and I probably will never get my hair professionally flat iron. I say that now. I just put and so we're going to attempt to wrap my hair and maintain it so it can maintain it because it's going to be raining. This weather in Texas want to talk about it. We're going to talk about it. So I have a Hercules comb that I got from one of my subscribers is literally it's called the Hercules. I got a bristle brush and I have some large bobby pins and then I bought this new wrap scarf because I can't find this is real big. Let's open this up. I can't find my regular scarf. I mean, I have tons of them, but you know how you got that one favorite scarf. So I got this from Walmart today. This better work. All right, to try and wrap this. Let's talk about what's going on my personal life. Okay, so those you don't know, we moved to Texas in January. Girl, what is this doing? We moved to Texas in January. Let me hydrate it and slowly but surely we're settling in. One of the things that I have made it a priority to do is to see my family, meaning my aunts and uncles who are getting up there because you guys, my mom was the youngest out of her family. My mama will be six. Well, she's 62. She's still young in my opinion and then my dad is 64. So there are sisters and brothers, my aunts and uncles are up there. You know, they're in their 70s or in their 80s. Well, like a lot of traditional Southern families, there's a lot of them that were year by year, but year by year. My grandparents were having kids every year. That's what you did back then, girl. You didn't have YouTube. So making sure that I see all of my family members before because tomorrow's not guaranteed, right? So I'm seeing like two to three family members per weekend. And I go every two weeks so far. And I have a big family, big family. Mom is the youngest of 15. Dad is the middle of 10. Multiply that by cousins. It's crazy.  So I have cousins that are older than my mom. So it's funny to see that. But it's just a big family. And I would definitely be trying to attend some of that family gatherings, some of this stuff. I'm like, no, like they're having something in April where I'm like, no, I'm not, I'm not going. They're fishing. Yeah, I don't fish. Now I'm country. I know how to clean fish.  But I know how to do it. I actually do know how to catch fish, but I just don't like to do it. It's boring. Maybe I could go and drink something. Girl, no. So they're going to be camping and all that. No. I said, no, and I'm allergic to pine trees. They're going to be a lake of the pines, lake old pines, lake of the pines. I can't pronounce anything out in Longview, Texas. No, I'm not going to be able to do it. So I'm not doing that. But it's so good to see my family. What else? What else? What else? We're going to get into having a date night soon right now. It's family night, you know, since this is a new environment. And I will say it will be a good six months before I'm definitely settled in because there has been so many changes. Those of you who are not familiar, we have changed JB in different schools. My poor baby, you guys, we've been having issues with JB's behavior, which I think a lot of parents have noticed our children. And one thing that my husband was doing, let me close the door. JB went through with these crazy tantrums and my husband was like, oh, there's something wrong with him.  And I'm like, no, he's not.  And he's not the only one. So since he cannot hear me, what I did, the analytical part of me, what I did is I took a good three days and research the effects of the pandemic, specifically in other historical events and how that has an effect on not only childhood development, development, excuse me, but also behavior. I went, I went there. I created like an eight point slide presentation and presented to my husband the findings of my reasons. You're looking at me getting all, what do you call it, getting all corporate on y'all. But no, I had to, since he is that type of mindset too, I had to present with him like, no, he's not the only one, a large number of students or excuse me, of children or not only they are regressing, but they're also finding you guys that children even born during the pandemic or they're not developing as, as fast as other kids. You know, you see those little TikTok or Instagram, these pandemic kids are built differently. No, actually, on certain milestones, they are actually not at not advancing. They're not hitting their milestones like they should be. And that's just what the information I saw. What is another one I can tell y'all trigger, trigger the hospitals have noticed a 45, I think it's over 40% increase and self harm and suicides with children 18 and under when that is really, really sad. So I had to present this to my husband and show him children thrive on stability and predictability. That has gone off the door the past two years, right? And even so even, even so, even worse with Jebesa, JB our child, because so within two and a half years, JB has gone from charter school to home school, to private schools, no, no, no, no, to micro school, to public school, and not private school. That's five different types of schools within two and a half years and we moved three times. So yes, I think it's, I think it's a lot. I think now for me personally y'all, I'm doing a lot better for a while. Their anxiety was through the roof. I'm doing a lot better. I'm getting up early stretching. I'm sleeping. I'm drinking my water. I haven't gone on exercise yet, but if y'all could talk, I'm gonna put my hair up. I've lost weight. Look at that clavicle. It's not something I've done purposely. I have not been eating and I know that's bad. And so when I do eat, I don't want to eat because I've been so busy, but I'm going to get there. I worked on and I got myself a fourth means of income. I don't want to get into it a lot in detail, but I needed this because I have a goal.  So I think I briefly mentioned last year that my job had told me that I was up for a promotion. Well, that fell through. And when I tell you, I literally saw the email come through of the promotions and when was it? It was like like a week after we moved here. And I saw those emails when I tell you, I actually started crying. I started crying because not that my manager promised me it, but she said she, I'm not even going to get into that because you never know who's watching your video. But long story short, I for sure thought that the promotion was in the back for me. And so when that came through, didn't come through, I was devastated. What you have. So what can we do to make sure? Because look, I'm not struggling for money. We're not struggling for money, but I have a goal to pay off my debt within three years, two and a half years is what I want to do. Yeah, I'm growling my stomach. Excuse me. But if I could do it in two, three years, but if I could do it in two and a half years, even better, my credit score is slowly going up. It wasn't bad to begin with, but about what's in the news, not going to get a lot into it. Because let me tell you something. I do not, I do not dwell in the, in the, um, like the stuff that's going on with Kanye and Kim. No, I don't know. I don't even know what's going on. I know that she's dating already or they even legally divorced. See, I don't even know, but I am going to bring up the fact that Tracy Braxton, those of you who don't know, I think that's so sad. I didn't know she was sick. Let me back up. Tracy Braxton of the Braxton sisters passed away from, let me back up. Tracy Braxton from the Braxton sisters. Y'all know the Braxton's, um, Tony Braxton sister and Tamar Braxton sister and she was, was she a backup singer? I'm not sure, but unfortunately she has passed away of cancer at 50 years old. And I think that's so sad. I did not know she was sick. I had no idea what you, that is just devastating. You know, um, so prayers to her family. Um, besides that girl, we're not going to talk about this stuff going on in the Ukraine. I think it's, I think it's absolutely sad. We all know that when war comes, the only people that really, really, the civilians are the one that are going to suffer, but look, y'all, I was on somebody's channel, somebody, I'm looking, I'm sorry, I'm looking over there. I was on somebody's Instagram and they showed a video of a man who used to be a woman. He was trans, he had, was a transgender.  But some of the stuff, y'all, I'm like, what? Now I'm used to seeing the man-to-woman transition. You know, I'm used to seeing that, but I'm not used to seeing, I, this is the first time I've really seen one like this, right? So he's showing his before pictures, looking like he used to be on the usherboard. And then all of a sudden he goes through, he's showing all the pictures of him of, you know, from taking the hormones. And he looks like a fifth member of three, six months.  Let me tell you something. Gramps will be doing my hair. I will be, I'll be ready to beat somebody if I show up at a show place. You know, you taking me to Papa Dose. I'm getting a, you know, two fish, catfish with my red beans and rice. You give me a swamp thing. We go home to your place.  Like we got to smash pocket books.   You ain't looking where his titties used to be at. My husband said the food is here. I'm going to wrap it up y'all. This, this man looked like he was from Memphis and it looked like he saw weed on the side. But he also used to be on the usher board. I'm telling y'all. So y'all look, like I said, I have nothing against that. If you want to do that, baby, but just being honest, that's what pisses me off. Men are women when you'd be dishonest. And like I said, you taking me to Papa Dose and we going to hear your place. And I'm thinking you're going to sling it out and you got a pocket book like we both can't be making change. I'm just saying. All right, y'all, we're supposed to be doing my hair. So this time I'm going to, I'm going to try to wrap my hair. I'm going to comb this Ford and then girl and then what I'm going to do is wrap it this way. I'm looking like something from the grudge. Whoo, child. Now we can't do it. We just ain't gonna be able to do it. All right. Let me try to tell you what I'm watching. Girl, I have time.  His mama is back. Oh, uh, what do you call it? Spoiler. Mama is back. Y'all know what? I'm a stickler for accents, right? So when she came back into the apartment, she said hello. I didn't notice an accent. I was like, uh, cut. So I rewind it a few times. I'm like, oh, your accent slipped. So I went back and looked at her, um, bio and she's English. I'm like, all right. I'm gonna put this here because she didn't go on to act right. Um, killing Eve. I posted on my community tab our favorite cycle path fashion.  Y'all Villanella against spoiler alert on killing Eve. She I have AMC. That's how I'm watching it. She called herself wanting to get baptized, right? So that she can, you know, she can be good and see the Lord. She still got evil thoughts, right?  Y'all. So watching that killing Eve, watch a movie. Y'all.  I'm done. Look, I'm done. Watch a movie on Netflix. Jolt, Jolt's game.  Oh my God. I can't talk. Hold on. Shit. Everybody. I can't nobody help me. Are these our split ends? What? So this is, this is not how my hair used to look like when I was relaxed. Is that why it's looking like that?  You know, we're just going to wrap it up. Y'all, this is not good. This is not. Girl, looking at it ain't going to change a damn thing. Isn't there another way I could do this? Girl, I ain't no damn way out of the way. Okay. We're going to leave this, this is a style. We're going to leave this down for the rest of the video. All right. So on Netflix, I watched Jolt's game. You talk about, I loved it. I loved it.  Let me tell you something. Why they got, I told y'all, like on the community, why they got ghosts playing like a 60 year old man? He's playing like the stepfather and the girl is 30 years. Come on, come on now. I like the series. It was a little slow like episodes three and four. I felt like they could, I'm like, come on. Cause the first episode came out and I was like, Ooh, let me, let me continue to wash this. Hold on. I gotta wrap in my hair. Just really was disrespectful. So it was good. A lot of surprises. I finished it over the weekend.  Renee, Zilla, or whatever. Y'all this series, it's on piece notes. There's something about Pam is on Hulu and it's about a, it's based on a true crime and it's definitely giving me like Fargo vibes. There's the overall feel of it and it's based on a true crime incident in which a woman named Pam killed her supposedly best friend named Betsy for insurance money. Like some of the true crime YouTubers like Kendall have already done this, you know, done a story on it and this series is absolutely hilarious to me.   Very believable. Coming soon, which I'm excited to watch is P Valley and Bridgette now. Y'all know I can't pronounce anything. The Duke ain't gonna be on it this season. I'm a bit salty by that, but it's coming and I'm ready. Y'all, we're gonna figure out how to, we're not going to wrap it. I tried. It's a lot of hair. Look, all of this is one person's hair. This is one person's head, head of hair.  I'm going to go eat. All right, you guys, bye.


We're heading into Shannonville, Mohawk, Tindanega, Mohawk Territory in Ontario Do a video for Rich TV Live And the community, show them the future, glimpse into the future of what the legal market could be If Health Canada got out of the way and let them do their thing You guys can be making money like the free market here And I'll kind of show you how it's just grown and thriving It wasn't $5 grams, $100 ounces It was about $50 Probably a quarter for the first year But just like the legal market after a year, people dropped $5 grams Most places started as little dispensaries like that Little shacks Now they're turning in, actually that one is over there Just because they're building this, brand new, two places But Rich was right about the $5 grams The first place to get $5 grams was this little shit box trailer And it blew up and now they have this canik here It was the first place to put $5 grams A year into all these dispensaries had been open And you'd see $5 grams, $100 ounces They have drive-throughs at two of these places But that little shack, that's going to be their new one And there's their gas station they're putting They'll just keep making so much money They're opening gas stations, expanding, growing But Rich was right about the $5 grams, $100 ounces It really 10x'd this community, blew up Brought people by and coming in just to try a $5 gram Get an edible Now that's just one there, there's these better buds They're probably, you can get $50 ounces here And they have hundreds, like probably 200 strains But it's really a $5 gram place there Because they have about 30, 40 different $5 grams There's bee leaf here With a free-flow petroleum Gas is like 92 cents I'll turn into this pot shop here I'll show you, this place started as a little shack $5,000 trailer They got $100,000 signs, LEDs It's actually good in the summer The slushy machines and all that stuff But then they expanded to this place They have their own radio station Plays old school hip hop and advertises But yeah, the pot shop, it all started with this little place They sell thousands and thousands of clones in the spring But yeah, you can see they got things Strain specific, $5 pre-rolls CBD, 20% Charlotte's web available And they're pretty smart business people here I'll show you the next one that's coming I think it might be the Indigenous Roots Or just building a new one That was a Kronos actually funded on The Kronos Garden Baldurtham Here's the new one, Native Flower It's a beautiful place It looks just like any winery, wine-tasting VQA place No, that one's called Native Flower There's Smoke on the Water That's got lounge, pool tables, everything But the Indigenous Roots is something Maybe to look into the stock I think it's IRCC, Indigenous Roots Court Kronos bought a big stake in them And Kronos even said We're going with the Native people Because they don't have to deal with All the Health Canada crap and get to market Way sooner, that's Kronos Not just me saying it And they're smart business people here They're not just growing ditchweed And selling it for $5 and stuff They're doing so well I'm always at the racetrack here Just as a little story Will I turn up here to another one One fella was always at the track He went up to Toronto to buy a McLaren He went up to Fath McLaren Bought a McLaren Cache, $280,000 And like they're Indigenous They don't have to pay tax, right? But the shipping and all that stuff Is another crazy fee to get something Drop shipped over here So by him being on Native land And getting his McLaren drop shipped here Saved him $78,000 in cash And by the way, McLaren had to go to Fath To fill the dreams Or had to go to Ferrari to get a second money counter You can see how large Phil the dreams is It's just growing And they just built this even larger place here It's almost done I'll turn around, another $100,000 sign But it started, it was actually See that little shack on the end It started that big They built the one across the street here Built that They got all the crazy signs They're allowed to advertise They don't have to deal with all the health Canada crap And it's Phil the dreams That new one there opened up And there's keep expanding He's got a couple of them You know what I'm saying? They're smart business people Like I was saying The one guy who bought the McLaren Broke the money machine at Fath They had to go to get another one as well It's just kind of funny thing But you can advertise There's signs I don't know if this camera will pick it up But... Rich was right about the $5,000 These places are blowing up But it's not all $5,000 I know you can't sell for more Than $10,000 a gram You have to max your top stuff at $10,000 They're low stuff at around $420,000 Pun intended And then they're in the game They only got to work about quality And get rid of health Canada rules And all that crap This community is booming It used to be so poor Like so, so poor Like tar shacks Shit shacks The cars, res rides look like demolition derby cars I'm not even joking They were poor And in five years Every road's getting repaved I'm going up on This is the last road to get repaved They're out cleaning the streets It's the cleanest place that you've ever seen And it just keeps getting better and better They actually built schools And community centers And it's such a great thing that It keeps growing And it's just proof that Illegal There's potential in it Once the health Canada gets out of the way They can do it But I'll show you that $5 a gram isn't everything Pardon me The 2.0 stuff's big The place I'm going to now Is fully integrated Legacy 420 It does everything from seeds Growing They have farms Into an outdoor production They have Cookie factories Like whole bakery Commercial bakeries There's a little Another one Forever green There's about 60-70 dispensaries on the land I'm just on this little quarter mile stretch But 420 I'll show you That the It's not everything Then right beside it There's Peacemaker Across the street There's herbal Something or other Herbal healing there Peacemaker But 420 I'll show you Because They have everything And I'll show you They don't I think their cheapest gram is They have $100 ounces But their cheapest gram is $7 I'll go in I'll show you that They make their money A lot of the 2.0 Because it's so vertically integrated They make everything themselves In-house And I'll go in I'll shut it off Try to shoot another video Just inside for y'all