Okay, very good. Well, we're just a couple of minutes after the hour. Let's go ahead and get started here. I'll say that, you know, I'm Lee Calcote, I'm the founder of Layer 5 and a CNCF Cloud Native Ambassador. I'll be moderating today's webinar, but we would like to welcome our presenter today, Julian Sobriet, head of product at Octorine. Just before we hand things over to Julian, we've got a couple of housekeeping items. Yes, the slides will be posted. Yes, we are recording today. And the recording of today's webinar should be up on the CNCF's webinar site a little later today. Now, we should note that during today's webinar, while you won't be able to speak, your questions are highly encouraged. There is a Q&A box at the bottom of your screen, so please feel free to drop your questions in there and we'll get to as many of those as we can. As a reminder, this is an official CNCF webinar. And so as such, it's the subject to the CNCF Code of Conduct. So please don't add anything to the chat or ask questions that would be in violation of that code of conduct.  And with that, it's time to hand things over to Julian. Julian, over to you. Thank you, Lee. Thank you for the introduction. So, yes, I'm a product of the Octarin and I'm just going to give you a few words about Octarin that explain why we created the ACTSS. So, at Octarin, we provide a security solution for communities. One part is covering the runtime with network ideas, data analysis, et cetera. And the second part is looking and enforcing the configuration of codes. One thing we used to show to our customers is look how many of them are running as raw, how many of them are running as privileged, how many of them are kept natural, et cetera. And the question we got from the customer is, okay, but out of all this customer with some risky configuration, out of all of these risky containers, which one I should look at first? Which one is most likely to put my whole cluster at risk? So, we realized that we needed a way to have a holistic security for containers, look at all the security settings of containers and give them a score that the users can use to figure out which one is the most dangerous, which one is the higher risk workload that they should address. The other thing that we understood is that they are about 30 different Kubernetes settings that directly affect the security of the workloads and understanding how these security settings change together to make the security better or worse is hard to understand. And in the end, it's hard to understand what is the actual risk that you are potentially facing. It's not just about best practices, not minimizing the number of work containers, it's really about a specific risk that you want to avoid or you want to remediate. And finally, the third thing we wanted to achieve is give them a solution to remediate the high risk because they might be a good reason why they need to run a container as a road or a privileged containers, but there are a number of other changes that they might be able to do to lower the risk short of being able to just turn off some of these settings. So, the first thing we did is look around at what are the existing security framework that maybe we could use for Kubernetes, the number of them and probably the most famous or the most used today is the CVSS, the Common Vulnerability Scoring System. You can already see the similarity in names between KCCSS and CVSS and that's because we took a lot of inspiration from CVSS. You're probably familiar with it if you are scanning your Docker images. The scanner will give you a list of vulnerabilities and the CVSS rating and explanation and CVSS is very good at describing the risk for these vulnerabilities. It shows what is the impact to confidentiality, integrity, availability of your application or server. It shows what is the potential scope of the vulnerability can it be used to compromise just the application or the entire server or get access to your entire data center. It also explains how easy it is to explore that vulnerability, is it a remote vulnerability or does it require local access, et cetera. So CVSS is very good at describing and measuring the risk associated with individual vulnerabilities. And from this, there is also the CCSS which is CVSS applied to configuration, the Common Configuration Scoring System. So when I first looked at that, so that's great that probably something we can use for Kubernetes configuration. Unfortunately, it's pretty much a dead project. It's based on the version 2.0 of CVSS. CVSS is now in version 3.1 with quite a lot of improvement between 2.0 and 3.0. So that's not something we can use directly but it's interesting to see, you know, the idea of applying CVSS to configuration is something that we definitely did. And the third project that we also looked at is the CC, the Common Configuration Enumeration. Unfortunately, it's also not an active project but what's interesting here is that it's a checklist of configuration settings where CVSS gives you a framework but not really data that are provided by other part of the nation or by vendors. CC is really a checklist that can go through one by one to check the security configuration of your application or server. So we decided that to take the best of these three frameworks to create a CCSS, so it's a framework that also comes with a list of rules just like CC. So we created rules that describe the risk for the different Kubernetes container settings. We describe the risk the same way as we do these CVSS and you'll see that in an instance. So we show what the impact for security are likely to be exploited, et cetera. And what we did is we made it more specific to Kubernetes. So for example, there is a scope in CVSS about what can you potentially impact and we know we change the scope to be the container, the node and the cluster. And probably the most important and probably the hardest as well is that we really in the end wanted to show a risk score for the workload and not for the individual security settings. So we created a new formula that take all of the risk into consideration and give a score for the entire workload. So we have two types of risk. Two types of rules, the risk, which is very similar to CVSS. So we describe what is the impact for the availability of your container or cluster or financiality. Is it likely to be to expose secrets, so I can get access to secrets and integrity. Can you make changes to your container or cluster or whatever scope? And for all of them, so it's rated from none, low, medium to high, again, just like CVSS. We also give a description, we try to make it very specific. So again, not about trying to enforce some best security standards, but really understanding what is the potential risk that you're facing. So in this example, that's the shared host network that's enabled for a container. So we explain that it potentially can expose the container to the internet by binding the container IP to the host IP. And that opens you to those attacks. If you don't have anything in front of it, it can be used to gain access to a container, to an application that's maybe not designed to be exposed to the internet. And also it allows you to do something quite different. Local this time is to be able to sniff the loopback interface on the container, which means give you access, let you see the traffic from other containers. That's why the impact to confidentiality is high, the impact to availability is high, but the impact to integrity is low. Then just like CVSS, we explain how easy it is to exploit it, whether it's something that's exploitable remotely or require local access and what the potential impact. So we do that for all the rules. I think we have about 25 to 30 risk rules today in KCCSS. And I think it's interesting just to read through them and hopefully you learn a few things about what is the actual risk associated with all of these settings. We also learned from a lot of users that maybe the first person who look at it might be a DevOps person who might be more familiar with risk and security, but when they want to share it with the developer, explaining why they need to address the way the particular container is configured, they need to really be able to convey what's the risk and why it should be taken care of. The other type of rule that doesn't exist in CVSS is mitigation. So there are security settings that make your security better. For example, having a service mail that encrypts all of the traffic means in the case before where you could sniff traffic from other containers or encrypted, then you know the risk of exposing CVSS right now. So the remediation are described the same way as risk. We show how they remediate the integrity, confidentiality and availability, whether they remediate local attacks or remote attacks and whether they protect the container or the node or the entire cluster. So the risk core is we first look at all the individual risk associated with the containers. We map the security settings of the container with the risk rule that we have. For each of them, we compute the score from zero, that's the lower risk to 10, and it's just like CVSS. At a high level, the risk has two components. One is based on the impact of the risk. Now if it's impacting, if it has high impact on availability, high impact on confidentiality, high impact on integrity and potentially can compromise your entire cluster, that part of the risk will be larger. But the other part, equally important is based on the exploitability. So how easy is it to take advantage of a misconfiguration or a risky configuration? And that's based on whether it's a local which is harder or remotely accessible and whether it's easy or not to exploit the issue. So we just add both of them and that gives you a risk for an individual risk role. So you might have a risk that has very high impact but very low exploitability and the overall score might be lower or the same as a risk that's medium but that's very easy to exploit. So the first step is we create a multiple risk core for each setting of one workload. Then from this risk, we compute the score for the entire workload. And the way we are doing it today, working on the version but what actually works was very well is we look at all the risk and the attack return scope. If two risks share the same attack return scope, we take the maximum score and we add them up and take the square root. So that give us the workload score again from zero to 10 based on the individual risk that we computed earlier. I've mentioned risk so far, right? I said that there's also remediation. So when we look at all the individual risk, we try to find a matching remediation and what we call matching today is remediation that has the same attack vector and the same scope as the risk. So the risk has cluster scope and remote, remotely exploitable. We look for remediation that have the same scope, cluster scope and remote remediation. So once we have the remediation, we basically lower the impact by the remediation. So if a risk was high for confidentiality and remediation was low for confidentiality, then we modify the risk to be medium one notch down. If we had high risk but higher remediation, we don't go all the way to none because typically remediation don't exclude one percent of the risk but lower it to a very low level. So we go from high to low. So we basically do risk minus remediation. We have this modified risk and that's the risk we use in our formula to step one and to be used for the workload. So KCCSS is a framework that comes with a list of rules but the idea is that you're not going to run it by yourself trying to manually map these rules to your clusters, manually run the formula, but instead that they're going to be tools that do the work for you. Scanner that will look at your workload configuration, map it to the KCCSS rules and give you this score. And along with KCCSS, we have open source cube scan which is container scanners that comes as a container itself that you install in your cluster. It scans the workload that are currently running in your clusters and show you the risk core and the risk details in a nice web UI. But the idea is that there could be other tools that are created later by us or by other people who can take advantage of KCCSS and show you the same type of results. Okay, so that's the theory. Let me show you how it looks like in practice and I'll do a demo and at the end of the demo I think I can answer some questions. Hopefully they will clarify anything that's shown so far and then I'll conclude with a couple of slides. So before I show you cube scan, let me show you the cube scan data page. Since it's public repository, you can Google for cube scan data, you cube scan October in and you'll probably find this page first. So this here is description of the project. It has a link to other KCCSS framework. I'll show you the data page in a minute. I'd explain how it works, what you're going to see with screenshots, but probably more important for you, it explains how to install it. So obviously you can always compile everything from source and create your own Docker file, but we've uploaded the container image in a repository. So you can take advantage of that and just do a cube CTL apply and install the containers in one comment. We have two ways of installing cube scan. The more secure way is to install the containers and do a cube CTL port forward to access the web UI from your computer. And for some reason, you want to expose it to colleagues or to other people. It's also possible to use the other type of installation that includes a load balancer. So it's exposed. The web UI can be exposed. Just be careful to not expose it to the internet. You don't want to give away too much information about your cluster. And when you're done, you can again with one cube CTL command, you can just delete the pod and the pod when you're done. So I was saying that there is also a link to the KCCSS. I just wanted to briefly show you the information we have here. So we have information about the project. Mostly what I've described in the slides. How you can create your own rules. We really made KCCS as easy to extend. So you can create both new risk rules, new remediation rules and really hope that we are going to have more rules that describe how open source solution or even proprietary solutions can improve your security posture or sometimes how some application that you install have additional risk associated to them. So I think the corresponding case is KCCS rules. So you have an exact understanding of your cluster. So I was mentioning the rules. I'm sorry, getting lost with the shortcuts. Okay, here we are. So under rules, we have risk accommodation, the whole YAML file, we have a couple of tools that can validate and so you don't have too much old information since the rates, the score are completed automatically. You just need to fill out the description and the impact if you want to create new rules. We have the same for aggregation and we are looking at adding more for specific tools. We have a wiki that's the last thing I wanted to show you on GitHub where we have more information. So specifically, if you're familiar with CVSS, we have a more in-depth comparison of KCCS and CVSS, more explanation about the different fields in rule and some information about how to contribute. Okay, so let me show you Qubescan. We have installed Qubescan in our demo environment. We have about 50 different workloads here. So when we install Qubescan, for the first time it's the configuration of all the workloads computing the risk and we can see that we have risk ranging from eight all the way to five. So we can already know that the most risky one is this echo A deployment. We have a couple of set or set to show you the type of commanding subject that it is and where it's located in which namespace and this is just for one cluster. So we don't show the cluster here but that's the question when you installed Qubescan. You can click on the score here and it will give you the list of all the risk and remediation and we can take a look at a couple of them. So we see that the highest risk here is that we are mounting some horse pass in the container with right permission and that the sensitive horse pass directory. So we can click on show more and it explained exactly why it's risky. So this is about mounting sensitive horse pass like slash, varran, docker, that's all. So one of these horse pass that we don't want to be mounting in a container because it can give the container access to docker, modify how docker is running, lets you maybe through socket file interact with application, read secrets, modify binaries on the host. So all of the different risk in the different categories are explained here. It's very easy to exploit like it's just about reading and writing to files once you get local access and you can potentially impact the entire note, not just the container. So you can go through a list. Again, it's very interesting as seen for education. If you have no team of developers who are not necessarily aware of the risk associated with the many different container setting that they have to set. Natural is another good example at the file that can craft any kind of packets. Means you can do man in the middle attack. So that's why the impact on confidentiality is high. So you can go through a list and we can see here that there are no remediation, sorry, only on your risk. If we look at some other workload that has a lower risk, like shoes here. So we see that there's also some risk but it has a couple of remediation that bring down the risk quite a lot. One is the fact that there's no listening port. So this service is not listening to any incoming traffic, which means it's remediating basically all kinds of remote attacks by not accepting traffic. So there's not actually any vulnerable, any risky configuration that has to do with remote access. But if we had any, that would be a very good remediation for all of this risk. Same thing, it has a service mesh. In this case, it's opt-in but could be Istio or anything else with encryption. So that means it's now much harder for any workload that can sniff traffic to get any content. So it remediates specifically the confidentiality and not so much the other types of risk. So again, that's very interesting, I think to really understand, if I install a service mesh and I do enable encryption, what kind of risk do I take care of and what kind of risk actually remains? So service mesh is not security answer for everything, it's a security answer for a specific type of risk. I think that's it for them. Oh, actually, no, I wanted to show you another thing that we see quite a lot in many users. So this one has a median risk. Actually, it should be high it's actually a bug that we're going to flip seven is supposed to be high. But what's interesting here is that it's a workload that's exposed for an external load balancer. So potentially accessible through the internet which by itself, again, is not necessarily a big deal. There are workload that are supposed to be exposed to the internet, but it does not have any CPU or memory limits. So what happens if you get a dose on this workload that's accessible from the internet and you don't have any kind of rate limit in front, then you potentially will be using too many resources on the pod and on the node, sorry, and the node is going to try to reschedule other pods on different nodes and you may have cascading failures. Also what's interesting with having something that's exposed to the internet is that you are potentially chaining local risk with remote access through the load balancer. So if you have any kind of vulnerability in your code, in your own application running in the container in the OS, that can be used to chain remote access with local vulnerability. So that's also something you want to pay attention to when you have a very large or a lot of privilege, local privileges, making sure that they are not accessible remotely. So I encourage everybody to download kubescan and try it in their own cluster. You can just remove it when you're done. It's open source, you can look at the code. You'll see that we don't export any information. So it doesn't connect to the internet. So you can even run it in a gap environment. Nothing is being sent out. It's running 100% locally without any internet access. The only thing is incoming traffic so you can actually access the web UI. So that's it for the demo. I have, I think, two slides to conclude, but I think that's a good time to answer some questions if there are any. So I can... Oh, awesome. Very good. So, Julian, if I heard you correctly there at the end, you're saying that this open source security project is in fact itself very secure, right, Ruth? Yes. Okay. Thank you. Okay, great. This is a fantastic presentation. We've got a few different questions that have come in in the time that you've been giving it. So very good. So a fair bit of interest here. Let me toss a couple of your way. And this first one came in a little bit earlier, but the question is asking how is it that the workloads are enumerated using Cubescan? Yes, so that's a very good question. So we often ask, what do you look at with Cubescan? Do you look at configuration files? What happened if I install my workload with hand charts or operators? So Cubescan look at the runtime configuration of your workload. It doesn't matter if your workload was installed with a YAML file or with hand chart or if operators are making any change. It's looking at the runtime configuration through Kubernetes. Makes sense. Very good. There are... We've got a couple of collection of questions that are somewhat related to one another. So I'm gonna conflate two of them and let's see if there's a difference. The first one's rather straightforward. It's a question about compatibility with OpenShift and whether or not Cubescan is compatible with OpenShift. So, yes, it works on any cloud provider also with OpenShift. It's using the standard Kubernetes API. So it will work with any Kubernetes distribution. Nice. On the topic of compatibility, and another question thrown in there is, is compatibility with AWS Fargate tasks or like Google Cloud Run instances? That's a good question. I don't know if you have tried it. I'll check. I'm not sure if we have tried it on Fargate or Google Run. Fair enough. Very good. Back to the... And I guess, like I said, we're gonna conflate two things. There's a couple of questions about pod security policies or PSP enabled Kubernetes clusters. Do you know if Cubescan has been used in that environment? Is there a compatibility there? So I don't know if the question is, how does it look like at the pod security policy or does the pod security policy with PreventCubescan from running? So the answer should be, it should work with many strict pod security policy, but also it really looks at the current code which will be enforced if you want by your pod security policy, but really it looks like it looks at how the containers are actually running, not the policy that's being said, but really how they are running at that time. Okay, got it. And I think some of the attendees are interested in just the further into the future. So I think we're gonna get into the furtherance of Cubescan and its compatibility with, or its cognizance of pod security policies. So very good. Another, just lots of questions coming through. So another question here is whether or not it's possible to restrict Cubescan to a specific namespace? So not yet. We have an issue open for that. So we are looking at doing something like that in the coming days or weeks. Right now it looks at your entire cluster. Oh, very good. Okay. You can, if you're only interested in namespace, you can do a filtering by namespace. So you can organize them by namespace and not by risk. But yeah, scanning, there's an issue open for just running it on specific namespace or namespaces. Okay, very good. Another question here has to deal with whether or not the configuration items align with CIS benchmarks. So that's interesting. So yes, we looked at CIS benchmark to make sure that we had rules that covered everything. That's one of the reasons why we added some of the RBAC rules. That's the reason I checked them in yesterday or Monday. So everything that you will see in CIS is covered and much more. So everything related, that should say everything related to containers. So in the latest CIS benchmark 1.5, if I remember correctly, it seems like 5.x, 5.3, 5.6, 5.7. That is part of it. We don't reference the CIS benchmark necessarily, but it is covered, yes. In the end, CIS benchmark is also about container settings, at least in section 5, and that's what we covered. Okay. A related question is that whether or not the attack vectors align with the MITRE attack framework, the ATT and CK framework? Yeah. So we used the attack vector from CVSS, and it's only local and remote. We are adding something that's a bit similar to one of the MITRE framework that classify the types of attacks. So again, we do it specifically for communities, and we are starting to add that kind of information, a better classification of the type of risk to improve the formula, especially to improve the way we match risk with remediation. So we are adding categories like secret exposure, lateral movement, Kubernetes, privileged escalation, this kind of thing. So that will allow us to have more granularity when we match the risk and remediation and for the workload formula. So it's the same spirit as the MITRE attack framework, but it's very specific to communities. So there will be fewer categories, and there will be a bit different than this framework. Okay. Understood. Very good. Well, there's just a couple of final questions and I think just some interest and feedback on plot security policies. And so the question here is, or the note here is that there may be multiple PSP policies in the environment. So some for infrastructure components, some for tenants. And the question being, you know, whether or not CubeScan ensures that the correct PSP policies are taken into account while evaluating risk. So. So I see again, because we're looking at what, how is the container running and not how it's being configured originally? You know, it includes any kind of change, whether it's for a policy or again, operators or anything. So in the end, what we're looking at is the current state of the workload, not how it was originally configured, but really how it's running right now. So that would include, know what policies are being enforced because it changed. It might change how the configure the workload is running, but really how it's running right now and not how it's being set up or configured. All right. Very good. I think we are, we hit the bottom of the bucket on our questions. So Julian, if you had had a couple of other slides, we're ready for those. Let me conclude. So I just wanted to talk about what's, what's next. So I already mentioned that we are looking at better ways to match remediation and risk. And that's mostly by introducing more categories. We're always looking at making the workload risk better. We want to add more rules. We just added a couple of on the back this week. And we're looking at a few more on secrets environment viable, for example, and we welcome any suggestion. I'm sure we are, we are missing some of them. The next big step will probably be to expand outside of Kubernetes. Because typically a Kubernetes cluster lives in the bigger environments where you have, they have other controls, especially on the network side. Seems like load balancer that are in front of all the ingress traffic, network policy, that also in the end, and change the risk profile of your, of your cluster. And finally more, more tool for KCCSS. So I think, you know, outside of cubes can just having a better understanding of the risk, how the risk interact with each other, what kind of remediation you can apply. I think that's very useful. So we wanted to make, make it easier to explore the KCCSS framework. So stay tuned. Next couple of weeks, we'll have more, more tools including online tool to do that. We just checked in again this week, a few basic tools to validate and start playing with this roles. So if you look for KCCSS, you should be able to do a simple search for Github, KCCSS, or OpenKCCSS. You'll find the Github homepage. You can also go to our website, openKCCSS.com. And at the very top, there is an open source tab. You can click on it and you'll get information about cubescan and KCCSS. If you have any questions that either I could answer here, I was not clear on, just a new question that comes up, but not hesitate to email me. My email address is here, Julian with the e-mail. Feel free also to open issues. We are looking for PRs and, you know, new roles. So I hope some of you will contribute to KCCSS and cubescan as well. This is a great presentation, Julian. We did have another question come through and just, I think, another Kubernetes engine user, just looking to affirm compatibility or just, I guess to sort of answer that same question again, does cubescan work in GKE? Yes. So I think the demo that we showed was actually in GKE. The demo environment is in GKE and the container was installed in GKE. So yes, AWS, Azure, Google, OpenShift, they work for sure. Bargate again, Google Run, we haven't tried. Specific environments, you can let me know. I think it doesn't work. Either open an issue directly on GitHub or send me an email. Nice. Okay. Very good. Another question was whether or not there's any plans to get this integrated to the community as an off the shelf product? So yes, we haven't engaged with anybody yet. We wanted to make sure that there's some maturity in the project and that we have enough feedback, no exactly what direction we want to go. But yes, we'll be looking at CNCF probably and see if we can put the project under that umbrella or some other open source organization. Very good. All right. I think that, you know, those are all the questions that we have today. Well, so thanks so much all for joining us on the CNCF webinar. The webinar recording and the slides will be online later today. And so we're looking forward to seeing you all at a future CNCF webinar. And thank you so much for telling us about KCSS, KCC SS Julian and cubes can. Thank you everybody. Thank you. All right. Very good. Have a good day everyone.


Rwy'n meddwl, a edrych chi'n meddwl gyda'r rôl, ac yna yw'r anodau ar y cyd-dymian? Oe, yn cyd-dymian drwng yn fawr, mae'r anodau'r anodau ar y pwg yn fawr y gorfod yw'r bufnwys gafroed. Mae'n gweithio'r anodau ar dda i, mae'r hyn sy'n cael ei bwg honno. Mae hyn yn ystod dw i'w gwaith yw sy'n gweithio'r anodau, ac mae'n gweithio'r anodau a'r anodau. Yn tans ynghylch arnynt mwy o'r cydwn i'ch bod ni'n cael ei sgol o ti. Mae wedi meddwl o'ch ystaflifth digwydd bwyd yn un o'r cydwn, a nidEM cadw i 알�ud y cydwn i gwasanaeth gwybethрwyd yr Yn Llywodraeth i ddechrau. Mae'n amlwgol i'r cydwn i ddim â'u rhai, ond rydyn ni yn ddau ddechrau. So dwy'r cydwn i'n ddiolch gynnig ar y newydd ac o'r cydwn i'n ddorol. Fe yw'r cydwn i'r cyllid yma mewn chyrnodd mmhwyng, Mae ydych chi eisiau graddair iawn nad oedd dweud gwneud LBC 2.3.6 a yr unrhyw i 3.4 Jau, ac wnaeth rhaid gweithio newydd ABI sydd wedi cael newydd LBC 2.4.0, LBC 2.4, LBC 2.7 a'r LBC 2.7 a'r LBC 2.6 a'r LBC 2.16 a'r LBC 2.8. Mae'r cyhoedd o'r tîm rhwng yn ddeifyddio'r ffordd. Felly, mae'r ffordd yn rhaid i'r ffordd yn dod o'r ffordd, yn ddechrau'n dda i fy ysgrifennu. Rwy'n meddwl, mae'r ddechrau'n ddechrau'n ddechrau'n ddweud, wrth gwrs, yn fawr, i'n meddwl i'r ffordd. Mae'r ddweud yn dda i'r ddechrau'n ddechrau'n ddechrau'n ddweud, ac mae'r ddechrau'n ddechrau'n ddweud. Mae'r ddweud yn ddweud, felly mae'n gyd yn hi'n meddwl. Beth yna ni'n mwynhau beth dyma eich bod yn dweud. Mae'r Ymgellfa Rhynghwll sy'n dweud. Mae'r Ymgellfa Rhynghwll. Mae'n rhaid i'n meddwl, yn ymdrygu. Mae'n rhaid i'n meddwl. Mae'n meddwl, mae'n byw'n gwybod i'r AJ. Mae'n ddysgu'r hyn o ran i'n meddwl yng Nghymru. yn myth ymdweud i wneud hanfodd ddiddordeb i'r unig hearth i'r halu, godiwn ni'n ddiddordeb i'r hun... Yn myth i gael y rhai gyda hwn o'i gymryd trwy'r gymryd, nid oedd rwy'n dod i ddeudgoi'r hyfforddi'r argenig ac mae'n gydw i ddwybu'r hyfforddi'r gweld a pwysig i'r hyfforddi'r amddiffynu gwneud? Felly mae'r argrig oherwydd yma pob yw! Ebydd pawr i gael armaedd ymddiffynu gweld am ddif Teams i wneud Ac mae'n gweithio hynny ddim yn unrhyw gwahol i'r ddafod o fewn i ddweud o ddweud y Swinellau, a ddim yn ddweud o ddweud o unrhyw gwahol, a wedi'i gwahol iddyn nhw'n leddigoladau yw rhai gwahol, ac codi'n moddol ychydig, a'n dod i chi ddweud eich ymgondol ac mur o cerdd o'i ddweud. I gael y'r gwylltyn yn y byw, enwedad, mae dyma'n gwybod. Dwy ddifrif yma, roi'n cael eu bod yn edrych. Mae'n edrych yn ni'n fwy o'r gweithio i gyd ystafell o ddarparu. Ond mae'n ymweld yn ymweld y gweithio i gyd yn ddefnyddio. Yn ymwyaf, maen nhw'n gwneud, rwy'n rhai o gyflawni swyddi, ac wedi allan'n llwythol. Fel ydwod y gallwch chi dweud ei fod y pwg llei, a wedi cael y morhefyd i'r bobl. Mae'r rhaid i'r If you don't, that's not good. No, so we get the basis to meet some characters that got it up. Yeah, so we have to find... Right. Yeah, so we can then just put that in each route. Yes, if you have a basis, you can just put it in the loop, right? Well, I think I would. I think so. It's also because of all the data that you can see in the other person. It needs... It needs the effect of visiting a month. It calls once, so to have it. And if they don't, it depends on the week. It's xdfr. Yeah, so... So you have to leave by hand. Imagine if you're a lot of nodocs. It's just a lot of sushi. So the model is looking... Yeah, you could put that up. A 21-bill next route is here. Oh, amla roots, but that's true. That's true. That's why this route is running already. The big end, yeah. And what's the wynches? I'm sorry, the big end. The big end, yeah. Yeah, that's right. Yeah, it's perfect. Yeah, that's right. It's very long tool, actually. I think we want a box. A box with an interface. An interface? Yeah. So I think that I need to get a new big build. Is there anything else? No, you're going to have to schedule it with you by then. Yes. At least there's some point. Compiling is important. It's quite a trilogy. I don't know, I'll try. If we haven't built it, I'm not sure how many things are going to break. There's only one thing that will break 4.1. And then there will be all the things we've fixed specifically for, aren't we at the third point here? What? In CSF, because now we're getting back to it. It doesn't have a mix of anything. The application will do it properly. I don't know. Exactly. Years ago, when everyone did this, they just said easy on. So now we need to do easy on, not the FP. It's the correct room. So there are all different things that we actually have to go around and do. But apart from that, and the structure of the things which might have been wrong again, because it says it's going to be fixed for this arm in general, I think they might not be able to break the game. Although I mentioned that people just put... I think generally just put whatever it is that's a good attribute packed, which I think will still work. That's a stretch of the answer. But it's going to be fine. The app doesn't keep the mess down, so it will be said, oh, I'm going to shoot with a collage around. Let's see which is a reality. I hope you know who did that. Thank you. I think we should all mess about this today. It's going to be a build. Is there anything to ask? What is it getting to do with? I mean, you've talked with Ajay about the mark, and you don't think that's the main issue. Yeah. So I'm probably all talking about this. You didn't all talk about how they feel about all the mark, having that break out of the shoe. Right. We went over the upgrade thing a bit, but it's within the exotic, because you have to boot into which media you're at, and then change the place system, and then remove a new kernel, and then for the rest of the year, the chance of that working seems to be pretty low. I'm looking back at his list. Backup. Backup. It's much more likely to work for boxes. This one should go on, because there's a lot of stuff going on. It is. It's possible. There's all your stuff. I was talking with the production. We should do that. We'll see how it works for both. I don't know the kernel. No, the kernel can, I believe, it can use around from the old ABL to the old ABL. That's what we want. Either. Right at the same time, right? Yeah. Once they're all coming on by the flag, then I think it should be able to use them both. Yeah. It has, you can't find the kernel. Oh, well, there's a flag in the front. And then it has the old ABL. Yeah, okay. How does it kind of work? I suppose, it is a lot of forcing. Semi. Slightly. It's my young queen. Yeah. It's a big time difference. Yeah. The new kernel is not actually tightly coupled to the ABL change. They're just going to do it at the same time because they're operating stuff anyway. Yeah, it makes sense. Also, the ABL changes between the four system changes. Which is more than the top way out for the old kernel. It was 2.6.8 to 30. So you can't split the two things. Yeah. What I'm thinking right now is like change rule is not possible. But if there is a way to run UML Linux on that, that will do it. But that will be like not very elegant. That's the only way. What was your idea? I know. It's kind of an interesting project just to see how it works. I think we've got better things to do. This moment is on my desk. Well, yeah. I mean, what person will work on that? Yeah. It's much better. Yeah. I'm not quite sure what's going on with this point. I kind of said I'm going to grab it. So, you know, we're just doing projects from the moment that's closed until December. And then there's a maintenance period of six months or something like that. I mean, we should be able to persuade them that they're going to be great. But that's not the only guarantee I need to pay the band with. It's on the end of DSL at the moment. Well, I don't know what to expect. It depends on the ratio of building I think I want to do that and also at least start with a few people to be able to go to the table here should be somewhere better. I think I'll leave my boxes. I'm sure not here to use them to build stuff. If you go, this is a simple fast on the way. What are we doing? There used to be a scratchbench 0.96. Co-construction is to change compact as it was from 0.96. Okay. So you have not actually used any native building? As I never tried to build a GCSE for that. Okay. So what was that? A native GCSE has been compiled in that system. Okay. Stop.


If you want to make more money as an insurance agent and you want to understand the numbers behind making $400k, then keep watching this video. We just had a recent YouTube comment. Someone said, how would I make $400,000 as a life insurance agent? So I'm going to walk you through this. I've done videos on $100k. I've done videos on a million bucks. I don't think I've ever addressed $400,000, which is a good amount of money. $400k is $8,000 per week. That's 50 weeks. I'm giving you two weeks vacation. How would you do that? Well, the first thing you need to think about is, yes, it's $8,000 per week, but what is your average? I would say, what is your average commission per sell? I want you to think through, what is your average commission per sell? I'm going to use, there's a lot of different life insurance products. I'm going to use something, I'm going to use $1,000 for simplicity and for a lot of people that may be high, some people that may be low. I'm going to use for general math sake, keep it really simple. I'm going to use $1,000 per sell. Now I'm going to keep it very, very simple. If you take $400,000 divided by $1,000, you need 400 policies. This doesn't account for people not paying their first payment or charge back or canceling later. Again, we're going to keep it very simple and then you can do the math and add some of these extra things in later. So $400,000 divided by $1,000 commission per policy, that's $400,000 policies. $400,000 policies divided by 50 weeks is eight apps per week. Now again, I'm going to be very conservative and say that you need 16 sits per week to get eight sales. That's extremely conservative because that's a 50% close rate and that doesn't even account for the fact that some, maybe a double sell or a couple sell or you get maybe three or four apps out of a home. We're just going to assume that you close half and then you only get one. Ultra conservative, most salespeople are doing a little better than this. But in this example, 16 sits eight sales. How many people do you need to set appointments with to get that many sits? Well, to be conservative, typically about two thirds, but I'm going to use 60%. If 60% actually keep the appointment, then you need about 27 appointments, 26 and two thirds per week. So then you've got to figure out, well, how can I set 27 appointments per week? And I want you to wrap your mind around that, sort of think about that and how you believe that you could set 27 appointments per week. Because if the math is in this example, I need to set 27 and to sit with 16 to sell eight to do this, then how do you get to this number? So let's just say that out of every 27 appointments that you set, half the people you talk to book an appointment. And I think that's very conservative as well. So in that case, you need to speak to 54 people. And let's just say that you get a hold of about 60% of those individuals. And I'm using crazy conservative numbers. These are not real, but you need 90 dials per week of a combination of new and aged leads. If you can get all 90 from new leads, more power to you. But in this example, with ultra conservative numbers to equal 400k, you would need 90 or maybe this is leads because maybe you have to dial more than once. Because 60% is not going to be the immediate answer rate. Maybe after three dials, maybe you do get a 60% answer rate. You talk to that many people. Sometimes you can talk to more. So I feel like I'm being ultra conservative. Speak to 54, set 27 appointments, sit with 16 and sell eight. 8 times 1,000 is 8,000 bucks. 8,000 equals 400k per week. Now, the things that this doesn't account for that you need to think through really quick. The things you need to think through is, yes, we know the numbers of what you need to do. Maybe you need about 90 leads to call on. Now again, they don't all have to be brand new every single week. You could say, well, I need about 50 leads a week, 60 leads a week, whatever. I can continue to repeat those calls because let's just say you had 50 leads one week, 50 leads the next week, 50 leads, 50 leads, just say five weeks in a row.  Let's just call it a quarter. OK, that means 50, you can't set anymore. But even they said no before, so you still have 200 leads. That you can call continuously over the course of the next several weeks. So that's where that's where the main things to think about. OK, the main things to think about is, yes, yes, you need to do the math so that you can actually know your numbers. But the things that hurt people is they typically don't buy enough leads because you don't have enough leads. You're not going to talk to enough people. If you don't talk to enough people, you're not going to set enough appointments. You don't set up appointments. You're going to set up enough people. You don't set up enough people. You're going to make enough sales. You're going to make enough sales. You're going to make enough money. Right. So you don't buy enough leads. The third step after buying enough leads is that most people aren't consistent with with several things. When I'm talking about consistency, I'm talking about consistency in actual marketing. Right. I need leads every single week and I need to be consistent about it or it's never going to work. OK, so marketing, I need to be consistent with the amount of money I spend. I need to be consistent with it. I can't I can't buy what leads one week, buy leads three weeks later and expect to have consistent results. It's impossible. It doesn't work. That's the recipe for disaster and why 92% of interest agents fail. Okay. The next thing is you have to be consistent about your schedule. You got to be consistent about the time that you put in. You got to be consistent about the dials. You got to be consistent about your script. You got to be consistent. If you have an appointment center, you got to be consistent with your appointment center. You need to think through this is the main things that can hurt people. Everyone can do this. Everyone can do this at least once. Most agents never do this. They are not consistent enough over the course of a long period of time. And when you're trying to hit 400 K like this, the key is long obedience in the same direction, which is consistency because 400 K, even though it sounds like a ton of money over the course of a whole year, it's only $100,000 per quarter. It's only, let's just do the math and say it's only $35,000 per month. Okay. Or it's about $8,000 per week and work day wise. Or just over that, it's literally about 11, we'll round up and call it $1,200 per day. When you start doing the math and you break it down like this, it doesn't seem as big and as complex. Anyone can make 400 K. If they do the math, they have enough marketing and they're consistent about it week in and week out. I was a new agent not too long ago. I started as an intern, calling on the phone book before I knew you're not really supposed to be doing that. I feel like I get and understand new struggling insurance agents. Most people in our business are not the dude making seven figures, rolling in it and traveling the world. Most of the people in our industry are struggling. Some even have part-time jobs. I want to be the guy that they can go to, to really learn some knowledge and really help them. I was very fortunate or in 117,361 dollars and 13 cents in my first eight months. I thought if I can do that, working for one company, selling one product, I can probably help some other people, too. What is up? Welcome to Phone Phenom. If you love this, I got a video you have to watch. It's How to Sell Life Insurance. It's amazing and it's right there. See you there. They say life insurance is the hardest product to sell in the insurance industry. If you think so, I can make it real easy if you keep watching this video. All right, so I'm going to teach you how to sell life insurance. My name's Cody Askins.


Hello, beautiful souls. This is Christy with Art of Awakening and just a quick daily meeting for you here. This is, I'm recording this on April 10th, 2019. So this will be for this day through the 11th or whatever day you happen to land here because time is less linear than we think. And I have a little audience set up here. My birthday was last February, but my birthday happened to be the day where we had like the biggest snowfall of the decade. And so a little family party that got delayed and I was just giving these beautiful little candles.  And I thought I'd bring in Ganesh, the remover of obstacles just because it feels like a lot of obstacles are being removed right now. And let's just keep that trend going. So this is the card of the day. This is salmon, right? Salmon. It has been coming up a lot lately, just a lot, a lot for me and the readings that I've been doing over the past year. And I always associate salmon with Ascension. They do, you know, they're an interesting animal because they live in both fresh and salt water and they have to adapt to those. But they come up, you know, to spawn at the end of their lives. And so for the salmon, you know, this process of creation is also a process of death because they're hatched up in the streams and they have to go down to the ocean and there's a transformation process that happens so that they can handle the salt water.  And what this is kind of saying is that the message that salmon is bringing right now is that there are a lot of changes. There's a lot of Ascension, like the whole planet is ascending and we're part of that. But when we do have changes, there's like, there's a death that happens and often like many, many little deaths because it's like it's that process of letting go. It is a type of death that's the whole resurrection, the resurrection kind of archetype. You know, the Christ archetype is the letting go, the shedding, the releasing of the old in order for the new to be born. So, and that process can be painful. I mean, it's not hard or it's not easy for the salmon to swim against this really strong, really strong current. And, you know, you get the same thing with the snake, the shedding of the skin. There's all sorts of like the butterfly moving into the the chrysalis and experiencing sort of a death. So I think the encouragement today is to acknowledge, just acknowledge that there's some pain that goes with it. And without getting sucked into victimhood, because it's really easy to be feeling this pain and oh, you know, it's poor me, whatever, like, and I'm not trying to make fun of anybody because it's like, I'm totally speaking for myself too, right? It's easy to kind of wallow in that feeling. And sometimes that we go through phases where it actually feels good to be miserable, right? But hopefully, most of us are, you know, have moved out of that or in the process of moving out of that. And but in order to really let go, it's also, it's also easy to go into like when we start moving out of victimhood, we go into the opposite of extreme like, oh, I can handle this, and it's okay. And, you know, I'm a survivor, which is it's also a really good phase to go through, right? But then if you can move through that too, to actually honestly looking at whatever happened to you or whatever, you know, whatever you've had to go through and acknowledge the pain without getting sucked into it. So it's sort of like this dispassionate observation of the pain. And sometimes that can help to actually finally release it. And then move on, move on to the next phase, move on to the, you know, in the case of the Sam and the next generation, you know, a rebirth. And because life is just a lot easier on the other side, be downhill once, you know, whatever it is, and we're all constantly moving through these things that we have to release, it's just part of the journey. You know, and once we've released a few things, then more things come up to be released. And just part of this is just sort of an appreciation of observing this whole process. And, you know, doing so without getting caught up in it, just sort of observing and releasing letting go. So I encourage you to just be in a phase of observation this day and enjoying the moment as well, because there's so much joy to be had in life. And, you know, this process of releasing what it does, it just helps us to open to that joy. So enjoy your day. If you are not familiar with what I do, the Art of Awakening, it's, I offer ascension coaching, spiritual coaching, and healing work, as well as artwork. This is my deck that I created with the animal cards. So I've got a link to that below, link to, you know, signing the possessions. And I encourage you to subscribe if you haven't yet, and be sure to hit that bell to be notified of new videos. I am uploading videos all through the month of April on a daily basis. So thank you so much. I love you all.  Just have a great time today. Find something in today that is joyful to your heart.


12 o'clock in this position, you've got a prominent saddle, that saddle there is our axis for the gunman. What we'll do is we'll take some shots at the snow bank and then we'll walk down and we'll see what damage it's done. This position is burning in the field, hard packed snow, it's pretty much your only option. Your target is up and hold! Exercise cold response is an amazing opportunity for key NATO partners to come together in the most challenging environment of the high north and prepare for contingencies and learn to work together. And what we'll see is a strong maritime task group, task force, airplay and then some land exercises. And we'll see many, many nations coming together from the UK to the Norwegians, the French, the Germans and the Italians. So it's going to be an incredible opportunity and I'm certainly looking forward to it. NATO as an alliance needs to be ready for anything, ready for all environments. And it's essential for us to support Norwegian partners to be able to operate in the Arctic and that's why we train here so often. The Marines in the UK are one of two very high-readness formations and we really are the tip of the spear for the conventional UK force. And we take that responsibility really clearly because we need to exploit the maritime flank, we need to open theatres for others, be out there gaining understanding and intelligence, being ready for crisis and then ready to contribute to the fight. And that's something that we take seriously every day. The temperature and the weather, obviously the biggest challenge out here. Facted in with everything else as well, but that specifically, especially out on the water because we've got the wind chill as well as obviously the water that freezes instantly as well. And if we're heading off down the fjord at a boat group at like 30 knots into a 30-knot wind, it can quickly become down to minus 60 plus. So we've got to take that into consideration as well. Training here and always just brings the best out of people as well. Pulling together, you've got to check each other off constantly, call it the buddy-buddy system. Everything you do, you constantly check it, make sure no one's got any skin showing so there's no potential cold weather injuries there. But just being resilient out here, you've got to have mental toughness to sort of carry on with the task as well as dealing with all the conditions out here. You'll deal with it the same way we deal with any situation. You just adapt to make the best of what you've got and get on with it and everyone pulls together to achieve what they need to achieve.


Studying the Merchant of Venice, here's how you can analyse the second half of Act 4 scene 1. Portia comes in dressed up in disguise, she's dressed up as Balthazar and we can see that even if she is in front of the entire court she's quiet commanding and authoritative and even Sherlock respects her. Portia at first tries to convince Sherlock to have mercy on Antonio, nevertheless Sherlock stays firm and he refuses. Portia then speaks to Zero to say that she agrees that Sherlock has the right to have his contract enforced and respected. Sherlock is elated to see that Portia has agreed to the terms of the contract and he speaks in these acclamatory sentences to say that she's a really good lawyer. Portia then speaks using alliteration to remind Sherlock that he still doesn't have to go through with taking a pound of the flesh, he can take three times the original loan amount. Yet Sherlock responds using hyperforo to say he doesn't care he wants a pound of Antonio's flesh, the money doesn't matter to him anymore. Antonio then grows impatient, he wants to know the court's decision and Portia then tells him using this imperative sentence that the court has decided to honor Sherlock's contract. Sherlock is really excited to hear that he's going to be getting a pound of Antonio's flesh and he speaks using these acclamatory sentences congratulating Portia for being such an excellent lawyer. Remember that Portia is still a man in this case and Sherlock is congratulating Balthazar for being so good at making this judgment. Antonio has completely resigned himself to his fate and he speaks using i'm a contender to tell Bassanio that he is still happy to die because he knows that Bassanio got what he wanted, he got a marriage out of this horrible agreement and he's happy to die knowing that Bassanio will be happy. As Sherlock prepares to take a pound of Antonio's flesh from his heart Portia speaks using caesura to ask him to pause for a second. She speaks using assonance to say that Sherlock can have a pound of Antonio's flesh from even close to his heart but he must not shed a drop of blood.  Upon hearing this Sherlock changes his mind and asks for his loan back yet Portia is incredibly harsh and she tells Sherlock that he's not going to have any of his money back. Portia then speaks in these declarative sentences telling Sherlock that because of his crime of trying to shed Antonio's blood he now has to give up all of his possessions to the state as well as Antonio. Antonio then shows Sherlock what he thinks is kindness when he says he's going to take half of Sherlock's possessions and the other half will go to Lorenzo once Sherlock dies. Sherlock is devastated and he speaks using this simple sentence to show that he has no choice but to accept these conditions from Antonio. Bassanio is so grateful to the lawyer and he speaks using this imperative sentence to say that he must give the lawyer a gift. Portia then decides to test his love and she takes the ring which she had given Bassanio as a gift. Although Bassanio refuses, Antonio his friend reminds him of what the lawyer has done for them and he convinces Bassanio to give both his eyes ring.


Live from Boston, Massachusetts extracting the signal from the noise. It's the Cube Covering Red Hat Summit 2015 brought to you by Red Hat Hi everyone, I'm Sam Cahane with Stu Miniman. You're watching the Cube We're here at the Heinz Convention Center at Red Hat Summit We're gonna wrap it up for you. This is the end of the spring tour and it has been a Fantastic conference so far great energy in this place. They're Red Hat tattoos They're giving out clam chowder in Boston our favorite city giving away go pros We had some great interviews Jim Whitehurst came on Stu. How many years have you been here? So it's my second year of the show Sam. Did you win the GoPro? I entered four raffles They're not all over yet, but so far no GoPro All right, well it is my second year at the show and I really like this show first of all You know we got great guests on the Cube So first of all the executive team very open as you would expect with Red Hat Really good discussion on and you know it's just Jim Whitehurst said in his book and on the Cube They're really helping to catalyze communities. So it's not all about pushing a product It's about helping with the open-source vision and therefore the you know the various things that they're helping to do Broad partnerships pulling in their customers had a couple of really good You know partner and customer sessions here as to where they're doing, you know really interesting things Whether it just be you know on Red Hat Enterprise Linux going up to the virtualization Open stack open shift all the things they're doing in container I mean, you know we started the week at DockerCon and come back and you know Red Hatch like oh, yeah You know behind Docker who's the number two contributor in the open-source space? It's Red Hat Kubernetes from Google number two is Red Hat So, you know nobody ever would doubt you know the open-source credibility nor do we doubt at this point that open-source is a hugely important piece of IT and open-source is ubiquitous and people aren't just saying oh, it's okay If I do open-source they're asking for open-source and therefore Red Hat has a seat at the table for a loss of discussions Great Stu. I couldn't agree with you more and you know like you said So many great guests on if you're gonna pick out a couple must watch You know interviews for our guests or for yourself to rewatch who would you say yeah? So, you know it's a little easy for me sometimes because I say I want to start with the user case studies because that's the best way To understand how this technology works and how it can transform our business. So deep Mar from Amadeus was a great segment yesterday Really that the travel industry is one that is you know mission critical That has to help a lot of environments gone through a ton of changes, you know over the last couple of decades and They are you know an early, you know really lighthouse account for open shift You know lots of open shift customers out there But you know the one that they have front and center and you can understand why they are really passionate about what they're doing At OpenShift and I think he did a really good job of articulating what it did for it from the executive standpoint both Paul Cormier And Jim Whitehurst, I mean phenomenal guests so much experience so much knowledge Paul has been there since the early days of red hat And Jim it was like it reminded me of one of my MBA classes and kind of go through I do recommend reading his book because you know there are things that we learned as to you know How the hierarchy is changing and how we can get all get involved in a lot of topics the last thing We just had with Sarah Novotny You know personally what one of my favorites just because as somebody I've known for a bunch of years But to get down and really share some of the conversations that like I like having in the hallways in the back corners of these events and Online to bring that to our audience so so many good interviews here It's tough to pick a few because lots of really smart people and lots of good content throughout the two days of coverage Absolutely, and I think we had our youngest guest ever come on Jim Jim's son came on for a little bit. We took some group pictures. So that was always fun as well Yeah, you know it really highlights, you know, Jim Jim White her CEO had had his son here And it's about culture, you know red hat one of their differentiated out there is the culture of the company They say that you know culture will conquer all and you know, how does that drive? You know, you know natively innovation How does that keep them from being disrupted? Because we know that the pace of change, you know is happening so fast There's a great line from Doug Baylog and his keynote this morning said, you know, if you're afraid of change You know, you probably don't want to be in the IT industry because as we all know the only thing that's constant IT is the the rapid pace of change Absolutely and speaking of change do so you've been coming to this event for a long time. How is the actual event changed? What was the topic like last year? How's it shifted? What do you expect in the future? So Sam actually this is one one event that you know, it's only been two years for me But I've tracked red hat now, you know, I was a partner with red hat, you know, 15 years ago And in some ways a lot of things change but a lot of ways they don't may change all that fast Jim Whitehurst actually said and the reason that is is because they're not the ones just Necessarily coming up with an idea. They're looking for what the users in the communities get things started and then they're getting heavily involved So, you know red hat comes and says, oh, yeah this container thing It's not like this caught them by surprise Alex C's been around for I think almost a decade now. They got involved very early. They were there It's great to hear, you know red hat and Microsoft got together to help where we get Docker and core West to get OCP the open compute project Not so sorry not open computer container project too many OCP's You know going so In many ways, you know, there are some shows that are always like oh, you know We got 5,000 more people and we're growing this much from a revenue standpoint red hat is growing Dave allotted He'd a real good job breaking down, you know, if company they're their core product lines growing I think it's about 12 to 14 percent year-over-year. That's phenomenal growth If I look at, you know, the server industry the storage industry the networking industry, you know Low single digits is a good growth company and red hat is is is still growing at a tight rate At a good pace their newer areas are growing more fit 40 to 50 percent obviously opportunities in cloud opportunities in you know modern applications and the developers world and You know red hat being a public company is really the poster child for so much of you know, this open-source adoption I'm a real interest see over the next couple of years. I don't necessarily expect, you know more billion-dollar open source companies I do expect lots of companies that will be built on open source leveraging open source put the product in and that leaves red hat with lots of opportunity to You know get into a lot of environments Right and Jim Whitehurst was saying his big goal right now like you said is just gain that market share, you know Take away from the competition and keep growing So it's dude. It's been a crazy spring tour, you know, finally we'll have a little break a little time to rest You could you summarize what we've done so far this year and then tell us what you're excited for in the future All right, so for the next hour we're going to go through all of the very shows we did boy Sam We we've been at so many shows. Yeah, I tell this spring really appreciate everybody that's been watching this program You know, I can't even think of where the show, you know started I had a checklist on my whiteboard just for a segment of the like hyperconvergence stuff that I cover in that space not to mention It's cloud big data and infrastructure wikibon research everything going on in the cube so many shows You know, you know, I need some time to just reflect on it because you know We I think it's been like 19 or 20 live events. We've done we've been averaging two events a week I said three this week. So, you know real shout out to the whole team as to you know So many moving pieces, you know, we love going out of these events extracting signal from the noise And bringing all of this takes a lot of work behind the scenes So, you know, maybe say I'm a you know the wrap-up at this point, you know, thanks Sam for you You know, you're new to the team, you know, thanks to any any quick, you know takes You know, you joined us at the beginning of this spring tour, you know from the new new view What what what's your take so far? It's it's exciting, you know There's so much energy at these events and you come in you get the smartest people in the room the executives Interview them and it's a community, you know, it's that's what I rose. It's such a small it community and everyone's so connected It's nice to you know, have cube alumni as well who keep coming on and develop those relationships It's been great. We have a great team that's fun to work with. Yeah, I tell you and it is you know We are very much committed to the community here if you go to crowd chat net slash our age summit You see all the chats that we have here when we're going to events if there's people that we should have on Hit us up and let us know the cube has a Twitter account. I'm stew diva lontae furrier the whole team We're on Twitter. We're really easy to get in touch with there were people that I got on the program at docker con at this show Many of the other shows open stack Where you know people came and they said oh, hey wait, there's a practitioner that should get on Here's a thought leader should get on and you know, we really enjoy the platform that we have here But it's all about right the content and the audience that we can help love to go out to new events If there's an event that we should be at that's not yet on silicon angle dot TV You know hit us up We'd love to work to figure out how it makes sense to go so you know for Dave Vellante who is here co-hosting I'm Stu Miniman want to thank you know Luke Sam Andy Brendan back at the ranch Bert and John been hitting up on the the crowd chat the rest of the team that have been making everything happen You know throughout the spring tour in here and Sam bring us on home Thank you, and I also want to give a shout out to Andy. It's his birthday today. Happy 29th Andy Luke Thanks for everything. You're doing Brendan and Matt Cowling. We couldn't do this without you and a big shout out to red hat Thank you so much for having us. It's been a lot of fun and great content here in the Cube Yeah, look forward to San Francisco next year. They're gonna be back. It's bicoastal show They do Boston one year San Francisco the next year So it's the end of June right bullet before July 4th next year gonna be back in Moscone and I would love to be there Can't wait. So cube nation. Thank you for watching We'll see you soon