Welcome everybody. Good morning. Good morning, KubeCon. Good morning, everyone. Today, we are here at OpenShift Coffee Break. Our morning shows in EMEA. Today, with a special edition for KubeCon Europe, we're kind of warming up KubeCon. And today, I'm very glad to have our super guest, which is Siamak, Saden Giafar is the PM for OpenShift Github and Pipelines. And I'm always together with my friend Tero here at OpenShift TV. So I'm gonna just give the word to Siamak just to kick off this early morning show, right? Let's have coffee first. Yeah, thanks. That's all. I have a coffee here as well. Good morning to you as well. And I appreciate having me here. I'm like I said, I'm a PM for like an OpenShift team at Red Hat. I look after CI, CD, areas, getups, one of them. And really happy to be like one of the starting shows of KubeCon. Exciting. It's a very different KubeCon than what we used to, but never the less excited. Yeah. So and today we have a full agenda here of OpenShift TV. We're kind of kicking off this full agenda. Let's say Githubs today is really the main topic and we will have this discussion today this morning. And then we will have an office hour, Githubs office hour in the afternoon, set afternoon. Always with Siamak and Giafar. And then we will have another office hours for OpenShift. But during the show we will give you also details about it. So today, Tero, we would like to wrap up also with Siamak. The great Githubs con that was streamed on Monday as a co-located zero day event at KubeCon. Do you have any feedback, Siamak? I heard there were 1000 people attend. That's a great number. Yeah. So it was really exciting to see. This is, I know like we talked to a lot of customers at Red Hat about the problems they have around Kubernetes, around managing OpenShift, deploying applications and Githubs has become an area of interest for many of our customers. But it's really interesting to see that the wider landscape of Kubernetes user base and community also reflects that. That there is a huge amount of interest in Githubs, not as something that is hyped really because it has been, it's nothing new. It has been around for a long time. But a lot of, like mines at different teams, different organizations, community had come to the same conclusion. And I was really happy to see the initiative taken by viewpoints around Githubs working group and the community that is formed there in CNCF. So we were like through to be part of that and see really all this excitement about coming up with best practices, sharing knowledge about like everyone is addressing more or less the same problems with Githubs to be able to share this knowledge and culmination of that in a conference at KubeCon. I think that was, for me personally, that was really exciting to see. And the level of participation was like beyond my expectations, obviously. KubeCon has this nature of a lot of different, more focused, like many conferences are really competing for attention. And it's interesting to see that so many people are dealing with the same challenge that Githubs talks about, trying to put as the high level of like the huge participation in this conference. Cool, cool. So there were lots of also of interesting talk. This was co-organized by Red Hat and WeaveWorks, right? It was a kind of a collaboration on that. That's correct, yeah. So the background is that WeaveWorks is really the folks behind by calling the word get up. So they have done an amazing work and making Githubs a known practice on their particular term. The practices in Githubs, as you can imagine, like most things in software and IT infrastructure are not completely new. Especially like I know both you and Tero personally and coming from like being more acquainted with developed software development and especially you, a lot of focus on software architecture and things like that. Practices in it are not new, really. They're known to a lot of us when you look closer at Githubs. But WeaveWorks had this great effort on bringing a name to the practice and more concrete to define what that practice means. And so they are like, I see them as one of the really influential actor within the Githubs space. And Red Hat, like we about seven, eight months ago started investing heavily in RPCD because it solved the Githubs problem like really well for a lot of our customers on Kubernetes. And so it felt like a really great chemistry between the two vendors to come together. Spend time to organize this conference. This is not really for us, this is for the larger community, but at least take the initiative to organize this. And that was really a fantastic journey. We have had discussions with WeaveWorks before where this was the first time that we together coordinated events. And I'm really pleased with the outcome and hoping that more of this is going to come over the following years as well. Awesome, awesome. And this is, I've read and I also heard that it's part of the Githubs working group, right? There's a working group inside the SIG, inside the structure of CNCF working group. This is interesting. Can you explain a little bit how it works in this part? Yes, exactly. So this was essentially the first conference or mini conference that represents that working group, the Githubs working group. The reason that Githubs working group was formed is to create a vendor neutral community to discuss, share ideas and come up with, I wanted to voice it to say best practices or rather guidelines of how these practices could be used, how do they need to change so that they can apply to a wide array of use cases that different organizations and different teams have. So without that, even before Githubs working group, you could see already a lot of vendors talk about Githubs and Githubs practices, but what was missing is that the discussion very quickly gets focused on a particular technology that one vendor has. So you could see this in Red Hat as well. We've worked in CodeFresh and others as well that when we talk about Githubs, it's a particular perhaps flavor of it that is a little more adjusted to the products that Red Hat offers or products that we've worked on. And that is useful for users of that product, but perhaps not as much accessible if you're using different types of products. There are a lot of different Kubernetes flavors also out there and there are nuances there. So the idea was to form this as a place that we talk about these practices, regardless of what technology is being used. And when this idea was raised, we saw a huge interest from a lot of vendors that have been active in the CI CD and Githubs space and a lot of names like the need of the form that that we took as a great sign that there is like sometimes when new concepts and new technologies or new movements become popular, you see vendors sometimes become very protective. They want to protect their territory and become the definition of that space and lead that space for their customers and you sometimes end up in multiple actors dividing really that space. You could see that in the beginning days of Kubernetes as well. Kubernetes was one container platform or container orchestration among others and every vendor was trying to push that forward and make that best for all the use cases. Eventually out of merits of Kubernetes that became the de facto, not because everyone in the beginning agreed. When it comes to the Githubs working group, it was like really pleasant to see that that territory seeking is not happening, that everyone is on board to come up with like collaborating, putting their own individual interests inside and collaborate on practices that would benefits everyone and every organization that would be a practitioner of Githubs. So that's how it was formed and like out of that there are actually some really interesting initiatives are being born. One of them is that was announced actually at the Githubs Kubernetes bill is the open Githubs project, which is a sandbox project in CNCF and the aim of that is to come up with the principles of Githubs. So we have a common way of talking about it. We come on set of practices. We conceptually know what Githubs is and all of us more or less think about the same with their nuances that are different. For example, some customers when they say Githubs it is they're almost religious about it that every change in a Github repository needs to automatically go into the production. So as soon as it is in Github it automatically gets deployed in Github and if you don't have that, they might like say that you're not really doing Githubs. There is that breakage there that Github is not in sync with your production environment. There are customers that are that this would be extremely scary for them that once you have something in Github that goes immediately in production. There need to be a lot of checks in place that prove all very rigid process of rolling out something to production because of regulation or other aspects. There are good reasons for that, but even that could be polarizing that are we doing Githubs or not doing Githubs and we're all technology. So, although in the grand scheme of work and application delivery, maybe this is not that significant, but it does become a polarizing issue for a lot of us and the discussions of what is part of the practice or not. So the aim of opening Githubs is to through collaboration come up with this well-defined principles. This is what we think is practice of Githubs. This is what all of us try to adhere to and if you're a practitioner, this is how this is what you follow to get benefits of Githubs. If you're a vendor, if you're building solutions, tooling, if you're a community project, building things around Githubs, these are the areas to focus on. These are the challenges to address for the user, for the organization, Githubs and Githubs. So I'm really excited about a working group and the work that is coming out of it. And this has been such a short time, like really since it was formed, it was a couple of months back and we already had Githubs con. So it's going to be an exciting year to watch and what else we will do through this working group. Wow, it's awesome. First, the collaboration across vendors. As you say, it's not a competition, it's a collaboration in the industry. And this brings the open source, driving through the open source this process. Githubs is also a question that I have, because as you mentioned, there is that that can be some ambiguity. So how can we position Githubs inside the DevOps methodology and how Githubs talk with the CI CD part? Or is Githubs part of the CI CD? This is interesting to understand. Sure. So that's definitely how I see it at least. That DevOps is really that the broader and compassing movements talking about collaboration. Like DevOps is not a specific thing. There is no checklist that is saying, if you're doing this and you have DevOps, if you don't, you don't have DevOps. I think it's always when you see DevOps teams separate from the rest of the organization or these types of approaches to DevOps, you usually see a lot of reactions to it. Because DevOps is that an encompassing movement with huge focus on the people part and process part. So people and culture is really the main ingredient that makes a whole difference when an organization is adopting DevOps practices. And then there is the process and workflow of doing things. Then there are technologies supporting this. But if you don't have the people part, if you don't focus on the culture bit, there is only so much that it can't do. DevOps is really highlighted this way of thinking that this is a cultural change, the way that you collaborate between various roles in software delivery. And the name is a little misleading, like when a couple of years back when DevOps was at the peak of its high, the height of its peak. You could see always this blogs or slides like putting DevOps on one side, ITOps on the other side, throwing stuff. But now that the height is behind us and the more the tire has hit the asphalt and a lot of organizations are like facing the reality of adopting DevOps, and it's recognized that that culture changes, of course, beyond the Dev and ITOps is about every role that is involved in software delivery. There are not only these two groups, there are many, many teams that are involved when a piece of code ends up at a customer in a production environment. And it's about a collaborative way of working with all of those. What DevOps was not is or is not is that descriptive concrete way of achieving that. So it's about values, it's about culture change, it's about process change. It doesn't give you, this is the specific way of you do DevOps. And if you're not doing this, you're not doing DevOps. When you look at organizations that are adopting DevOps and adoption is really high above like 70% and you look at different surveys, they all have different ways. The actual workflows and the ways and organization structure, all are a lot of them are unique to themselves, but they realize the values of DevOps. So that's how I define DevOps. GitOps is a concrete way for the process part of DevOps. So GitOps, the three areas of DevOps is that the people and culture is the process, the technology. GitOps doesn't do anything for, doesn't do much really about the culture. It doesn't change the organization structure. It doesn't like to really make it any more collaborative if the organization is not really designed that way. But it focuses on what kind of cross concrete process can be used to realize some of those values of DevOps. And since it already names Git, it talks a little bit about the technology, but the focus is really on the workflow and process and a lot less on the culture change and a lot less on the tooling. That's a way of, it's one of the ways that you realize the process part of DevOps. And it is related to CIC, like you mentioned. So continuous integration, continuous deployment, continuous delivery, those were all like practices advocated by DevOps with really under them, automation umbrella. So that like one of the practices of DevOps that you want to automate delivery of application infrastructure to a great extent. And CI and CD are one way of like performing those kind of automation. Again, it's at the like high level of concrete. GitOps is really one, it goes under CI CD that is a very concrete workflow of how do I, how do I perform. CI CD, because CI CD itself could be done in a lot of ways, but it provides a very concrete process of how, how one might do CI CD. Cool. Thanks for this explanation is very accurate, very precise. And I also were wondering, you know, that is a great DevOps. No. So that was the best. You were a great DevOps. I don't know what you're doing now, but you were, you are a great DevOps. So I would like to know, so from you, what do you think about the impact of these GitOps technology and approach through with that can be done with open shift to customers that will adopt this. This is not only the technology like CMAC say it's also a methodology. And it's part of the DevOps. So what do you think about it? That's a good question. Actually, one comment to the CMACs about the standards that I built. There are a lot of similarities that happened with the service mesh. So, like, there was several different services and then there was one leading contributor that like it was like started building some standardization, because like CMAC said that there might be battle of the like battleground that which is the leading way to do something. It's a good approach. But about the DevOps and we have seen like like CMAC said well that GitOps is a more it's not about that much about culture. It's a concrete way of describing how what what is happening. And it is something concrete. We have seen these different adoptions like some let's say some some companies are still using VMs. They are still in adoption of containers and then at the same time they live through the DevOps hype. And now like CMAC said there is no hype anymore. It's just it's just there same happened with Scrum. No one mentioned Scrum Masters or Scrum anymore. It's just there in the in the standard way of working. But I totally agree 100% with CMAC that DevOps is a cultural way and GitOps is a way of doing. And I think that it is easier for customers to adopt GitOps because they can see the value. It is something concrete. I have said to customers that because they ask about why what is this GitOps how do I do how do I how can I do it? What is there for me? And how do I need to have tooling? What is the best tool? I said that easiest way just put your code to Git and run it through Git. That's the simpler way of GitOps. So you don't have to have automation like CMAC said that it is scary that every commit, every boost goes to production. I would say that not many companies are ready for that. Not many companies are ready for deploying once a day. Not many companies are ready for deploying once a month. So having kind of GitOps way that there's this hard, I would say, religion. It's the same as there was in Scrum and DevOps that this is the only way of doing some use Git flow, some use different ways of using the Git. And like you can start with really small steps like using Git as the single source of truth. And it can be easy as Qubes CTL apply minus F. That's your GitOps. The GitOps automation tool is that developer ops person, but that's the easiest way. And that is kind of it doesn't have to be automatic. It can be manual, but as long as the flow is correct, then it's easier to get from there. And I think that this is a good thing that it's really easy to adopt. If you think about that CIO in a company has a target that you need to adopt DevOps. How do you measure that you have been adopted DevOps? You can't because it's a way of working. Every company has its own definition of DevOps, but with GitOps it's easier because you can more strictly define the targets that when we have achieved GitOps way of doing like we automate deployments or we run everything through Git. So I think that in these ways, the world is ready from the tooling point of view. There is flux, there is Argo CD, all the major Git providers are providing the GitOps tooling in there like GitHub, GitLab, BitPocket, all those have their tooling already. So it's just missing the part of you just to start using it. So I think that it makes really easy to start using GitOps and there is real value in there. Like famous Cia Max said in cloud native development slide that you cannot do proper containers and DevOps without automation. The automation needs to be there and the GitOps is a good way to provide the automation. Really long answer to your question. That's actually a great point. I wanted to mention that as well, but this is a question that you see asked a lot about DevOps. Where do we start from? Because it's so obscure, it's a set of values and practices not very concrete or descriptive. There is no single answer to that. One organization or team needs to start from. But you don't see that question get asked about GitOps because it's extremely descriptive. It's a very defined flow and how things to happen. So I do agree that it's much easier for adoption because a lot of those practices are predefined in GitOps and makes it much clearer for teams or organization what they need to do if they want to move toward that. And the other thing I picked up when Tara was talking is that this is exactly the value of GitOps. When teams start looking at GitOps practices, they notice that they are doing a lot of that already. Because a lot of what you don't want into that, there are like a majority of customers who talk to teams, talk to them, they are using Git. I wanted to say or some sort of version control, but even the some sort of version control is gradually diminishing and majority using Git in some format. It doesn't matter what they are doing, if they are creating, if they're using Terraform for provisioning infrastructure on Amazon or if they're using Ansible or doing something else, whatever they're doing, they are usually putting all of that in Git. They are versioning that they are using the pull request workflow. And this is about the operation part when it comes to the app dev that's the entire flow is really what has been used forever. So that makes it really accessible that it's not about really shaking the organization up with the whole new sets of technologies of working, but we were like picking things that people have been doing already and put them together on their like a concise practice on how they relate to each other. So I think that makes it extremely accessible to a lot of things. It makes it really simple for organizations to start with. And also one addition to that is that when Kubernetes started to get traction, the only thing that was treated as code was the actual source code. And now the Kubernetes manifest, actually, people see those also as source code. And like Siamak said, everything is already in Git. The way how they are just deployed may be a different. There is a lot of young files like some said that I don't know who it was that DevOps is equals to young files. That is kind of true because what you know if we take the standard you run Kubernetes, you run containers. And I can say the third hybrid cloud so that buzzword. But what you actually is common to all those young files. If you say Kubernetes native, it's a young file. So that is even though it's a text file, it's still a code. And when you treat it as a code, you are basically doing GitOps because it code is in the repository. It can be SVN ops. It can be CVS ops. It doesn't matter, but GitOps is kind of more trending. Yeah, yeah, I agree. I think as you were mentioning, most of the people were doing kind of GitOps before GitOps became a thing like having a manifest on Git. Also part of the infrastructure as a code part of it, right? Having everything in Git, but there wasn't this controller. So maybe we can talk about also about the open source project we are using in OpenShift with GitOps, which is argocity. In this case, there is a controller that keep everything in sync. So let's say we were kind of doing that manually, putting everything in Git and doing a kubectl apply or OC apply. Now we have also a tool, a controller that help doing that. And maybe we can also introduce that. I was looking in the while in the chat with some people in the chat that are waking up. Hello, Sebi. Hello, Dario. Dario is a friend which is having also talked to a kubectl. Hello everyone. There's one asking about Doge. I think it's another thing, but I don't know. Let's say GitOps and crypto maybe something like that. But yeah, I would like also now to interact and please use the chat to do any question about GitOps. We have today, this one is Siamac. So catch the opportunity to ask to him everything about GitOps, but that's also the strategy I would like to hear from you, Siamac. Also, what is our direction in OpenShift towards GitOps? We can, of course, we introduced and anticipated the talk about ARGO CD. So what is the strategy of GitOps? And I know there is a GitOps operator in OpenShift. What is OpenShift strategy for GitOps? So yeah, an OpenShift VR, the way we see the mode of operating Kubernetes and delivering application on it is that GitOps fits extremely well to that environment. And because of it, we are investing heavily in GitOps with CICs. There are two prominent add-ons on OpenShift that support this way of working. There's OpenShift pipelines based on the upstream Tecton project. And there is OpenShift GitOps that delivers ARGO CD on the platform for that controller, the GitOps loop that you were discussing. Tecton has its own merit, the CI part. I mean, the GitOps, we don't talk about CI much. It's an extremely interesting area and a lot of solutions out there. But one of the problems we had seen is that it's difficult to really, there is always a gap between the pipelines that do the CI for your application and the Kubernetes environment. And Tecton focuses on really building on top of Kubernetes constructs. And you define your pipelines in form of pods and config map and secrets and constructs that are Kubernetes native. So it makes it really simple to have CI that executes decentralized Kubernetes. And OpenShift GitOps, you have ARGO CD that focuses on using that. So even though we say CD, I think this is also a change that has recently happened. That CD before like four years, five years ago within DevOps, CD was used to always CI and CD were used to get it to refer to the entire delivery process. More recently, when we talk about CD, we mean the deployment phase. How do you roll out a deployment of application after it's the images, the applications released through the CI process? How do you roll it out to all the environments that it needs to run on? So that's why we focus on CD. And OpenShift GitOps focuses on this particular use case. And both of them are generally available now, like we announced at GitOpsCon. They're extremely excited about that piece as well. So we do see that as the general direction of what makes it simple to operate Kubernetes. This goes in handy now, like Kubernetes in general. This is what I want to get out to. If you take a step back, Kubernetes has been a huge enabler first for DevOps, like containers and Kubernetes, and now for GitOps. For DevOps, because of the level of automation that Kubernetes provided, you don't need Kubernetes to do CI CD. But with Kubernetes, it becomes extremely simple because it's super simple to provision a new instance of your application in your QE, versus doing the same on a virtual machine on your hypervisor might not be as simple. So that really pushed adoption of DevOps. But especially when it comes to GitOps, the reason I think this goes hand in hand with Kubernetes is that Kubernetes really made this controller pattern very well known and familiar. Like could the controller pattern that Kubernetes implements, or it's a core of how Kubernetes operates, was not invented by Kubernetes, but it's an extremely useful way to look at driving operation. You declare what you expect, what you want. And in form of YAML or JSON, you put it in its CD, and there are controllers that go and do the work to make it happen. Instead of you saying, first do this, then do that, then do this, then add memory, then add storage, and then I have what I need. You just say, I need something that has this much memory, does this, looks like this and that.  So this way of this mode of thinking really became extremely familiar because of Kubernetes, is exactly what GitOps is really, except that we are saying that expand that to everything about your application and infrastructure, not just what you expect from Kubernetes, not just those manifest. And in the case of Kubernetes, you put those things in its CD, in case of GitOps, you put them in Git, there is something missing in the middle, as the controller you were mentioning. So somebody got to look at this Git repo and do the same thing that Kubernetes does for its CD. Kubernetes console looks at its CD, and whatever it described there tries to bring the cluster up to that state. So in GitOps, you need to do someone to do this for your Git repository, and there are a lot of technologies that do this. Red Hat in general, if you look at how Red Hat operates, Red Hat brings really like open source projects that have a lot of potential, and they are very well built, and they have a very democratic community around them, with it community, makes them consumable for enterprise customers. Like that's what we do across everything, like any piece of software you look at Red Hat. So we started looking at the community around GitOps and what technology exists, and our CD sticks out as an extremely popular controller for GitOps, started by Intuit, or started by Intuit's Acquire. Intuit for like in Europe, maybe they're like known less, they have different type of tax applications and cloud-based services like TurboTax and things like that. So in North America, they're extremely popular, and they run hundreds of Kubernetes instances, and they're using Argos CD, they built Argos CD as a way to operate all these clusters. So it was an extremely battle-tested piece of software for the GitOps method used by the organization who created it. So it showed a lot of potential, and also we saw an extremely active community around it. When you look at the Argos CD project, there are more than 100 organizations that are publicly speaking about using Argos CD. There's a list on GitHub you could look at. So we saw a lot of puzzle pieces come into the right place as a project that is extremely successful, extremely well-adopted, and customers on Kubernetes and OpenShift could benefit heavily from this. So we started talking to Intuit and formed a partnership to invest more in it, and then bring it as a supported GitOps solution on top of OpenShift. And there are other technologies available, do the same, like ReWorks has as flocks and real-life technology. Those are also available as community software on OpenShift. But the value of Argos CD was that the community was extremely well-designed and active, and solves a problem extremely well, very native to Kubernetes, and fits really well with the rest of OpenShift and other technologies that work with it. So that was the initiation of our journey. And fast forward a couple of months is we have both of those pieces of software taken on Argos CD as the foundation of continuous integration and continuous delivery on OpenShift. I'm extremely happy about that. And what we're looking forward is we want to bring these technologies a lot more into the ecosystem of OpenShift. So OpenShift is a platform. It's not a single piece of software. It's a platform with a lot of, with an ecosystem of software from Red Hat, products from Red Hat, and products from Red Hat partners that run on it. So we want to make sure that these two pieces are really well integrated and can take advantage of other capabilities that come through these other pieces of software on OpenShift platform. As an example, the Red Hat has acquired recently StackRocks, and it is released as Red Hat Advanced Cluster Security, ACS, which is like a really nice solution focused on platform security, continuous security. You can get compliance, make sure that your platform is NIST compliance, for example, or HEPA compliant, and it can scan images and configuration and create a really nice compliance report and allow you to fix it. So we want to make sure, for example, that we can use that as to enable DevSecOps use cases within OpenShift pipeline, within OpenShift GitOps and tie that together as a CI-CD flow that not only it is a way approach to implementing GitOps, but also it has security built-in, it has security checks and security flows built-in into that process. There is, for example, another product on OpenShift, Red Hat Advanced Cluster Manager, which is really well designed for cluster lifecycle managers. You want to provision a cluster on Amazon or Azure or VMware or different platforms. You want to manage your fleet of clusters as a group and look at the workloads, look at different aspects of it, and you're looking at a very tight integration with Argo CD there so that in Argo CD, you can sync a particular Git repo to a set of your clusters that are defined in ACM, for example, based on a set of labels. We can say that in Argo CD and Argo CD, usually you say this Git repo needs to sync to that cluster, but we want to make it more dynamic through ACM, say right now, I know that this repo contains my application, but right now I don't know which clusters are the production clusters for this application. I know it because we have a very dynamic infrastructure and the production clusters today might be these 10 clusters and through two weeks later, there might be different 10 clusters. There are short-lived clusters, so I want Argo CD to, at the time that you're deploying the application to somehow figure out what are the production clusters at that point and sync the application to those clusters. So we are looking at tight integration with ACM because ACM manages that fleet of clusters for the customers and it knows which clusters are production clusters at that point, so Argo CD can talk to ACM, retrieve the list of clusters and start syncing to those as an example. So we are looking to integrate in a lot more and more these two technologies into ecosystem of OpenShift and other pieces of software from Red Hat and partners that run on OpenShift and make it a really seamless experience for customers to want to start with a GitOps workflow on OpenShift and be able to get a lot of value across the entire ecosystem of products and add-ons that are available on OpenShift. Wow, Seema, this is awesome and I'm sure also Tero is very excited about this news about integration between ACM, which is the multi-cloud, multi-cluster management. That's my new favorite term, hybrid cloud, multi-cluster DevSecOps. I think that's my new favorite. You sold it very good. Yeah, but now we have been talking about DevOps, GitOps, deploying applications, but what Seema can take on actually using GitOps to manage the OpenShift, basically, GitOps is just containers running everything you need to run your application and production. What's your take on using GitOps to maintain the platform, not just applications? That's a great question. Coordinated, like we discussed, it's made infrastructure really declarative, but configuration of Kubernetes itself is not necessarily bad declarative. When you look at OpenShift, OpenShift adds a lot of peripheral components to Kubernetes to make it useful. If you want to use Kubernetes, you need a registry, you need Ingress controller, you need all these pieces around this so that you can actually deploy an application and use it. We spent a great deal of effort in OpenShift 4 to make sure that configuration of platform itself is also declarative, so that if you want to configure a particular Azure AD as the auth provider for OpenShift, for example, you have to go run commands, say, add this and that, and that, and at the end, you have Azure AD as the item to provider of OpenShift. Rather than that, you can describe that in YAML, the beloved, hated YAML, and you apply that to the cluster and cluster configures itself based on that description, that declarative description of the configuration. And that has been an extreme effort. We spent one and a half year almost on making the entire platform configuration declared in this manner. The advantage of the fruit that we get, one of the fruits of that effort is that you could point, you could put the entire configuration of the platform in a directory from YAML and run a kubectl apply, and the cluster comes to that baseline configuration that you specifically wanted and change all the knobs that you would like. And if you're running a lot of clusters, you could just use the GitOps flow similarly to automatically sync all those changes to the clusters that are connected to V3. So we see almost every customer on OpenShift that we see uses Argo CD. They start with this use case that they are using the GitOps workflow for configuring the cluster itself. So if they want, there's usually a platform owner, a platform group that manages the OpenShift cluster for other teams within the organizations. And they own a Git repository that contains a configuration of the platform. And if other teams need a change, they could also, they could even send a pull request. They would ask for a change themselves, modify the config, send the PR to that repo. The owner of the repo really used that. And for example, they want to enable a particular function in the internal image registry of OpenShift. So they send the PR that contains that change in that config YAML of registry. The platform owner team really used that. They merged it. As soon as it's merged, Argo CD picks up that change and sync it to all the clusters that the config relates to. And automatically it's applied there. So the platform owners, they have like the advantage of this way is that the wider organization has a way to request changes. It's not ticket based.  But at the same time, the platform owners have a gate and they are the gatekeeper. They have an opportunity to review, discuss, maybe reach back to the request there. Why do you need this? There are other ways to handle it. And once there is agreement, apply that and rolling it out to the cluster. And with that, like the advantage of this is that the visibility that you get on those changes, right? Every change that goes into those clusters, you can always come back into the history of the Git repo and see what conversations happen. And this is actually like, it's really important. I wanted to mention about majoring. You talked about majoring, like how much DevOps or GitOps we're doing. That's extremely actually important point that why do we do all of this? Why would we even start with GitOps? Sure, it's a little cool now and the automation hails. But what we really want to get to is a set of metrics that are important for the organization. So you hear a lot, like within DevOps, there are a common set of metrics that we talk about, like the lead time for rolling out a change. How long it takes for the change to go into production? Or how long, once we have a failure, how long it takes to restore our state to a function like restore? Like the mean time to restoring the service or recovering the service from the failure. And the GitOps workflow that we talked about for rolling out configuration to the cluster. So let's say there is a problem in the ingress control. The problem with the ingress control is not functioning the way you expected. The way to, like the GitOps workflow, it's a huge help to be able to connect that when was the, what are the list of changes that are applied to the ingress control controller. In the last, like over that time window from when it was working fine till now it's not working fine anymore. So let's trace that back to what was the specific changing Git that was causing this change on the cluster? Who issued it? Who reviewed it? What discussions were happening on it? What was the state before that? So all of that information you get immediately in case of Argo CD, we really a click from the SHA idea of the commit back to the Git repo and what change. We had extremely like provides a lot of information, useful information to reduce the time to recover it because you get all that contextual information at one place for you to be able to analyze and figure out what was wrong and go correct the situation. Awesome. Helpful for like improving those kind of metrics within the organization. The most important for the auditing part, right? Many users ask about what about the auditing, who makes what, how to roll back, how to roll forward. So this is very cool. And also another question I would like to know from you is there will be more integration between OpenShift web console and Argo or GitOps. At the moment, you can install OpenShift GitOps operator, you have Argo CD running. Will there be like pipeline, like tecton with more integration in OpenShift console? What is the future for this integration? Yes. So that's a great question. So like one of the good thing about Argo CD that it comes to the really nice dashboard that gives you a lot of like contextual information on what Argo CD is doing and how it's syncing and what's the status right now. So we are working on is to grab this information from Argo CD, combining the information we have about the runtime of the application on OpenShift, combining the information we get from Git, and come up with dashboards that show more the life cycle of application from the application point of view. So in Argo CD dashboard, you see the entire fleet of clusters and applications from Argo CD point of view. In OpenShift, you're working on views that kind of trim down that information to a single application view. So we have an application called payroll and it has four different environments. There is dev, there is stage and acceptance testing and prod. And I can see how application flows between these environment. And I can see that it was deployed on the stage. And for example, what was the change? What's the status of application on that environment? And the history of this flow from a single application perspective. So an application dashboard, if you will. Definitely working on those kind of areas to augment what you have already in the Argo CD dashboard with other mashup of information that you can't get by just looking at Git or just looking at Argo CD or just looking at OpenShift. Awesome. Thanks for this update on this integration, which is very cool to have all these tools integrated in OpenShift. Also with OpenShift, we have more and more tool in OpenShift integrated with OpenShift authentication. So there's single control plane, right? We're seeing auditing place where you can track everything. So this is a very cool. And we have somebody in the, let's say, let's see the chat. So somebody brought it's own coffee. Welcome. This is an OpenShift coffee bread. We enjoy and coffee with you and talking about such awesome tech discussion, right? And yeah, I shared also in the chat the Cata Coda learning path that we just published on learn, OpenShift.com. So all the people can start trying OpenShift, GitOps operator, trying user using Argo CD and doing everything you said, right? Going implementing the tool, looking at the dashboard. Yeah. So this could be also useful. And we shared also this lab in GitOps.com. And we would like to hear from you any feedback about that. And this is not the only place where to start with GitOps, right? We have more and more tutorial guide session coming. Yeah, definitely. Like the Cata Coda one, the one you shared, what I like about that is that you don't have to, you don't really need anything. You just need a browser, right? That's all you need. You don't have to get into the maturity of like running an OpenShift instance locally or getting a cluster and so on. It's not that difficult to do that, but with Cata Coda you're just having a browser. So definitely recommend to start with that. And even if you can get creative, like there are multiple tutorials and guides that you see in the blog post on OpenShift blog and Red Hat developer. And even outside on Medium and Elsevier on Argo CD and Tecton, you could actually use the Cata Coda environment to run a lot of those as well if you don't want an OpenShift, if you don't have access to an OpenShift environment right now. Yeah, a lot of content comes out in the coming weeks on OpenShift from Red Hat developer blog, but also keep an eye on the Argo CD content. The community is extremely active, so we see a lot of content popping up about different ways to use different parts of Argo CD and Tecton. I can tell like both of these projects grow like really fast, both deep and on the breadth there are new areas that are coming along in those and we're happy to see there's so much like guides and instructions coming also alongside it to advise users how to use different part of it. Awesome, awesome. And we have a lot of content. Yeah, this is a big ask to all the listeners, if you do something cool with KIDOPS, please share it. You do work in the companies, you might have to do top secret things, but I hope that you can share something. Like write a blog post, write a Twitter tweet, LinkedIn, something that, what are you doing with KIDOPS, what are you doing with Argo CD, so that everybody else knows that what cool things can be done.  Sharing is scary as we say in Red Hat, so please share what you do. And yeah, it was a pleasure. It's always a pleasure with Siamak, because the broad knowlets about the ways of working around DevOps, KIDOPS pipeline, so it's a, it's a, it was a pleasant, pleasant chat with you. Thank you. It was a pleasure for me. I really appreciated having me here. Like, it could call like early in the morning for the pandemic and people don't have to get off to go to work. It was, it was really fun talking to both of you. It was a pleasure, Siamak. Actually, Tero, we learned so much this morning. We should invite Siamak each, each episode. So we will learn more about KIDOPS pipeline. It was a very, very cool discussion. Thanks, Siamak, for joining us. And before closing folks, I need to have some reminder. So first I would like to share in the chat that we have the DevNation deep dive. So those are kind of vertical workshop to a certain technology. And we will, we have also one ARGO CD deep dive. So please register to the Red Hat developer and stay tuned because we will publish more and more deep dives also about about KIDOPS. And I want also to share also the agenda for today because today at KubeCon Red Hat is present at KubeCon. And we will have our agenda and don't miss, don't miss Clayton Coleman and 1045 a.m. says time talking about Kubernetes of the control plane for the hybrid cloud on the keynote session. Very, very interesting, cool session. And before closing, I would like to remind you our schedule that we have today at OpenShiftTV. If you go to the calendar today, we have the office hour about service mesh, KIDOPS office hour, together always with Siamak and Jafar, we will have the KIDOPS office hour this afternoon from 3 and 4 p.m. And then we will have another office hour for OpenShift for that set. So full day here at KubeCon. Very excited to be here at KubeCon. Very excited to have you, Siamak, today talking about KIDOPS. So I think we shared everything we had. And we can close this wonderful episode of OpenShift Coffee Break about KIDOPS. Thank you, Siamak, for joining us. It's been really a pleasure. And yeah, see you in OpenShiftTV later. This is a full agenda of today. Thank you, everyone. Bye-bye.


We do it again. What would it look like? I'm part of the customer support team in MCD division. We bring technical support to our customers whenever an issue arises in the use of our products. Solving a customer problem clearly has an immediate impact on ST business and it also helps bringing a stronger image of ST as a valuable partner for all of our customers. I would say that a solid technical background is necessary together with curiosity, resilience and good communication capabilities. I work with all the ST colleagues that are involved in customer support from regional teams to development teams. I may be in direct contact with our customers whenever is needed. It's the wide spectrum of customer requests that makes every day a different day that I find is quite satisfactory and stimulating. My first day in ST it was a long time ago. I was still a university student at that time and that was my first experience in a big company. I was even expecting a much more formal and strict environment but of course it wasn't like that. My tutor introduced me to all the team from the director to the other student. It was nice and friendly with only one regret. At the end of such an intense day I failed completely remembering everybody's name. Drawing it I would say a labyrinth because every day we must connect a customer problem with a solution and such a connection seldom follows a straight line. It's really like going through a labyrinth with different directions, dead end path and a various exit. Choosing the right exit is an everyday game to play. It's both challenging and funny, isn't it?


Hello and welcome to the session. Let us understand the following question which says 200 logs are stacked in the following manner. 20 logs in the bottom row, 19 in the next row, 18 in the row next to it and so on. See figure 5.5. In how many rows are the 200 logs placed and how many logs are there in the top row? Now let us see the figure. There is the figure where there are 20 logs in the first row and then 19 in the next row, then 18 in the next to it and then 17 logs and so on. The number of logs in a row is 1 less than the number of logs in the preceding row. So in this row there are 19 logs and in this row there are 20 logs. So this row has 1 less than this row. So let us write the solution. The number of logs in the rows form an AP that is 20, then 19, 18, 17, so on. Here A is equal to 20, D is equal to 19 minus 20 which is equal to minus 1 and it is given to us as there are 200 logs. So SN is equal to 200. Therefore SN is equal to N by 2 multiplied by 2A plus N minus 1 multiplied by D which implies SN is equal to 200 is equal to N is equal to unknown. So we write here N alt is divided by 2 multiplied by 2 multiplied by A is equal to 20 plus N minus 1 D is equal to minus 1. Taking 2 on the left hand side which implies 400 is equal to N multiplied by 40 plus N minus 1 multiplied by minus 1 which implies 400 is equal to N multiplied by 40 minus N plus 1 which implies 400 is equal to N multiplied by 40 plus 1 is equal to 41 minus N which implies 400 is equal to 41 N minus N square which implies N square minus 41 N minus 400 is equal to 0. Now spreading the middle term we get N square minus 25 N minus 16 N plus 400 is equal to 0 which implies taking N common from this 2 term we get N multiplied by N minus 25 minus 16 common so we get here N minus 25 equal to 0 which implies N minus 16 multiplied by N minus 25 is equal to 0 which implies N minus 16 is equal to 0 or N minus 25 is equal to 0 which implies N is equal to 16 or N is equal to 25. Now case one when N is equal to 16 then number of logs in the 16th row is equal to the 16th term of an AP with first term that is A is equal to 20 and common difference D is equal to minus 1. Therefore number of logs in the 16th row is equal to A plus 15 D which is equal to 20 plus 15 multiplied by minus 1 which is equal to 20 minus 15 which is equal to 5. Now case two when N is equal to 25 then number of logs in the 25th row is equal to 25th term of AP whose first term is equal to 20 and common difference D is equal to minus 1. Therefore number of logs in the 25th row is equal to A plus 24 D which is equal to 20 plus 24 multiplied by minus 1 which is equal to 20 minus 24 which is equal to minus 4 and number of logs cannot be negative. Therefore N is not equal to 25 hence number of rows is equal to 16 and number of logs in top row is equal to 5 which is the required answer. I hope you understood the question that's all for the session. Bye and take care.


Yeah, pigs are really intelligent like dogs and here we we'll give you this booklet on here if you go to cubertruth.com we just advocate that people don't eat animals or use animals or wear them because this is what they have to go through so you can do like a 22-day vegan challenge it's it's on the website 22-day vegan challenge and you get assigned a mentor and they help you Yeah respect animals that's what we're about respecting them like I used to eat meat, dairy eggs only three and a half years ago bacon and eggs for breakfast big massive T-bones every night I thought it was really macho but I was like wait a second like I might not love animals but I don't want to see them get hurt you know like I love my dogs and I care for animals and put the doggy here you know we love our dogs we love our pets but these animals they've got the capacity to be just like our pets they feel pain they suffer they want live in peace they don't want to be hurt you know and we just we're relentless and we show them no mercy we just kill them you know you know what you're looking at or are your farmers that doesn't necessarily mean you I don't want to sell the go vegan message but I can see what that's not the way to do things yeah for the end of the day we can't control what happens in the slaughter house to them can we I think I choose we said that that is that's not what I want to be part of I still want to be part of I want to be very much part of a meat industry but I don't want to be part of that that's not that's easy they come hand-in-hand though we can't avoid it like we got how many billions of people we've got on there if we're going to treat every animal kindly and caress them before we slip that throat open like I don't know if it's possible like it's not possible yeah it means nothing for the animal though making it better like this at the end of the day they still got a bolt gun in the head we would have not get ready even at all so you have that they actually not get bread so there's no well well then we keep them in your allies that we send we grow them to for two years and we send them to a slaughter house we don't agree with that just breeding them for to make money off their backs we would say is like there's a lot of other lucrative industries for farmers like plants or like soy beans or soy milk and they're taking over now like they started to take over this new industries that we could have a land with no animals on but you could cultivate some type of crop where there's because now that this plant-based industry is getting bigger people aren't don't want to buy animals that have gone to a slaughterhouse like no matter how you guys don't dispute that you guys treat animals well but when they say we put them on that truck we send them to the slaughterhouse you know me there's no controlling what happens to them they get chopped up into a million pieces we think the animals deserve a life without like a dog if we put dogs in there you know you know that animals are intelligent yeah you know how smart they are and when we take their children away from them when they're when they're so dairy farmers they take that they cough away the cows bellow out for months it's so we know there's a sentient animal inside there's there's someone inside there we never we're never going to agree but I don't want that I don't I don't want that then it's not you don't you still agree with killing them is okay I don't know but in your heart do you think taking their life no matter how we do it is okay like it's our job to take their life away from them it's okay for us if we're gonna eat their bodies when we don't necessarily need to there's no necessity for me in our diet like we can live happy healthy without it you can't be happy without me yeah I used to love the taste of it too I'm not gonna say I didn't I used to have really big t-bones nearly every night but like I think like it does my taste outweigh their life like I think it's pretty it was it I felt like I was being a bit I don't know like like selfish in the way that my taste buds meant more than their their whole life that the only one they get and you know we sort of give them their own destiny don't we we're like I know you want to say something you've got something that you really want to say but we can agree that it's wrong to take their life we can agree on that we can agree wrong to take their life they're away that a practical and that are painful like not in front of each other like not showing it in front of each other so we could do this practically on a huge scale like seven billion people want me you think we did this is why we've got factory farms yeah even the chicken industry so allow 40 to 60 thousand in the shed but even the chicken industry now that allowed their free range chickens but free range chickens get to do and from the countryside and still lay eggs and still be killed for me but you know there's no um there's no legal framework as to that pertains to what free range actually is I know they're so that they can call it free range and it's not free range that's something we need to fix there things we need to fix I think there's one there's a solution that fixes all of it which is leave them alone like we're trying to find animals so then either you have no animals because they're going to die eventually like they're going to die so they're still going to die of old age well then it's better than breeding like if they were better than breeding them into existence for this fate that they have I think that that what we're doing is morally wrong we're playing God we're genetically modifying these animals we're breeding them into existence so we can slit their throats and eat their bodies others think that from the animal standpoint we are there we are the oppressor like think of it from the cow's perspective you know how intelligent they are yeah they're like big puppy dogs I've known farmers boom go vegan and then try out something try farming something else because it's going to be a big soy milk industry that the plant-based industry is getting huge I would I would I grow I don't grow soybeans yeah I don't grow them yeah what I know about soybeans I would worry more about feeding my child soy than I would feeding them meat we know we've brought it up we've loved it so health wise yes we've fed it we know what we fed it and then we kill it for our children at a reasonable age not a view it's not as a lamb but at a reasonable age it's lived a good life on our farm it's lived a happy life on our farm and the meat tastes better because of all of that the meat tastes better yeah absolutely because of the way that you do meat if you treat meat well you treat it animal well treat the animal well so what do your children like seeing an animal get slaughtered do that or they they wouldn't like it so we're saying like we don't see what think it's it's against our nature is kind compassionate human beings to do this to animals and we're doing it because we've been programmed over time to like to taste the meat to think that you know killing them is okay because it's obviously ingrained into our culture isn't it like I mean as a farmer you'd know it's been passed down through tradition and through our family comes very much through the respect side you've got it you've got to respect but yeah and yeah do you think a knife in the throat is respect or there's not an animal that we kill yeah that doesn't what we shoot them they don't know about it I know that you don't I know you don't agree with animal cruelty that's obvious by the way that you're watching this but 99% of people don't get their meat from your happy cows you would you agree with that yeah I I wish somebody would fight to sell the argument factory when you do anything and that that's our capacity the factory farm so wrong I could yeah we have to we can I could I could quite happily feed a hundred families when I do it but but the system doesn't matter to me it says I've got to feed a thousand and for me to feed a thousand I can't do I cannot do it you can't if you want to be 10,000 you have you have an animal has to be how much land how much water that I drink you know how much resources you know how much cows drink how much fresh water they drink yeah we got 56 billion land animals on earth at the moment they're drinking our resources that we're feeding all the 50% of the grain is going to feed livestock we can't have grass-fed cattle for everyone you know what I'm saying so like this industry is causing problems in all areas livestock only drink the water that falls on our property all the water they drink falls on our property we don't describe anybody of water but I just the argument that I wish people would push much more is we need to farm animals it I want to farm animals there's people that want to buy meat for me there's people that I honestly don't believe that we can feed the planet just on grains why not because not on just grains we've got grains fruits vegetables seeds nuts we can cultivate them we're cultivating enough to feed 56 billion land animals we can feed the world 10 times over I honestly believe that cultivation cultivating the soil is significantly worse for the earth livestock are eating the grains that's what we're saying so without livestock a lot of cultivation wouldn't have to happen we just have enough for us they're chopping down the rainforest to go soybeans to feed to cattle that's because we eat meat it's not because you know you've got a farm where you do things differently that's fine it might be a little bit I've heard grass-fed cattle produces more methane gas so it's worse for the ozone I've heard that the catamara gives that is catalytic grass grass turns carbon dioxide we are from as far as we can establish we're more than carbon neutral what we produce is offset by what the way we farm our land we don't burn any residuals on it we try to do things properly so you're the exception not the rule no there are a lot of farms yeah but you're the exception not the rule if somebody could argue and you would do it very patiently that doing it as a factory farm that is not the way we have done things but they weren't in cakes where did they go afterwards they had to go to a commercial they go to a slaughterhouse most of that I could see in there is actually in the breeding site but a lot of that is the cruelty that happens in the housing in farming and that is so not on you don't agree that my position is the most humane way not stabbing them in the throat, not bolt gunning them in the head not shooting them just letting them be or not breeding them into existence not playing God with these animals' lives humane? the most humane method is not eating them or things that come out of them just leaving them be like I don't think you can humanely take someone's life who wants to live if they've got a good life on your farm to rob them of their life is even more of an injustice but from the cow's perspective you've got to see it from their eyes we don't look at it from our eyes it's different things look differently from our eyes we're eating them, they taste good from the cow's perspective they don't want to be eaten they don't want to be killed put a gun to their head they will be scared is it not a cow on their farm that I can pat? will everyone come to me when I call it? no they must love you we don't drive cattle and I have had so it must hurt you to take their life from them to shoot them in the head it does not make me happy it's telling you something but that makes it a good thing if it doesn't make him happy because that means that it's actually where the animal to do the right thing I don't think it's a good thing I think it's a moral dilemma for you it's a bit of a moral dilemma for you no, that is I so you don't eat meat from anywhere else only the cows that you shoot in the head yourself you won't go anywhere that's what we're saying it's not practical for people to always eat meat and just eat from the one cow that they shot in the head I could we could make it so much better I don't think we can on the scale that we're eating meat I don't think there's a possible way we can produce as much meat as we want to eat in a humane way and I don't think you can take an animal's life from them humanely we've got to think about different life we've got to think differently now you are obviously very passionate man you wouldn't be giving up your time for colour but I would just be so cautious of believing that soy is an alternative protein to be there is so much there is a lot of evidence of the manipulation that's happened to soy I would say what about beans lentils we grow beans and lentils I don't think there is a corruption in those that there is so soy is not an argument against what we're saying if you don't want to eat soy you don't have to but there's alternatives there are alternatives soy should not I will definitely not feed it I haven't seen the science behind that pooling all the results soy food intake after breast cancer diagnosis was associated with reduced mortality meaning a longer life span and reduced recurrence so less likely the cancer comes back anyone who says otherwise hasn't cracked a journal open in seven years most of the soy is used to fed to cattle that people eat there is a lot of soy used beans and lentils there's a documentary called if you go on there you might not want to see anything else but if you go on there there's a documentary called what the health I recommend watching it and what they do is they basically present the science so it's basically scientific consensus now that saturated fat and cholesterol cause heart disease this isn't a hidden thing in the scientific community and that cholesterol is only found in animal products grass fed organic animal products still contain saturated fat and cholesterol so you're obviously a very intelligent man and there are studies that say that human development has only happened since we've been eating more calories through meat we ate more calories because we could scavenge for meat there but that doesn't mean we need to do that now in this day and age we've got supermarkets they're the enemy thanks so much for your chat thanks for looking after these cows but I just say at the end of the line don't shoot them in the head please


Welcome to our all-day movie workshop. I'm Peter and Today we're joined by friends from our tabula rasa online retreat weekend and also just our regular Movie workshop attendance. So welcome to you all and so we've got a big group here today And so I can just let you know about the day. So we'll start with a movie with David Then we're going to have a 10 minute break Then we'll have our breakout rooms where we will have a chance to get in touch with any of emotions or themes that came up for us and Afterwards we'll have a 45 minute break and then we'll have a closing session, which I'll be holding today So thanks so much. I'll I'll cross it over to David now Hi, hi everyone So beautiful to see you all all your smiling faces and We have our mystery school Participants there. I see them all in the room and we've got our living miracles monastery cozy there You've heard of couch potatoes. We are the couch community. We are always in soft cushy couches and chairs Maybe it was lifetimes of being monks and nuns and sitting on hardwood Boarded pews and now we are going for the soft route to God We're still into mysticism, but we we have cushy chairs and couches for our bottoms So I'm so glad you're with us I see a large arena and her little boy from Peru Joining in brand new today. I sent you a link to the arena on For the discounted South America so you could come and join us more often and We always love to see the new ones that are there others Daniella Patricia I See you all it's just so beautiful We have Spanish translation for those of you who who want to hear today's Talk and and and see the movie with Spanish subtitles. So you just have to go to the the Spanish Icon the language icon interpretation icon and click on Spanish if you would rather hear it in Spanish If you want to hear it in English, make sure you click on on the English Well today we it's very exciting because I'm playing a classic movie This is the kind of movie that is like a can opener for your mind if you feel like your progress on of on the inward journey has been slow and Methodical This one is going to be a celestial speed-up today. You will be smiling from ear to ear Today after today's workshop because We will go deeply into an unraveling and an undoing of the ego and The ego has made a lot of beliefs to protect itself It's just like a little tiny puff of nothingness. It's a tiny mad idea Jesus calls it and He says in a course in miracles Into eternity where all is one there crept a tiny mad idea At which the son of God remembered not to laugh So our only mistake was taking serious The idea of separation from God the idea from separation from our source and yet Even though it's a tiny mad idea and it's just a tiny puff of nothingness. I Want to tell you that it's an ingenious Tiny puff of nothingness. What does that even mean? It means that our mind is so powerful that if we believe in it We can seem to make up hell We can make up we can make up Conflict war disease We can make up Delay we can make up sorrow. We can make up guilt and shame and pain and Today's movie is going to help us start to Step by step go into our mind and go through a dismantling of the ego It's unwinding your mind back to God and winding your mind away from the ego and toward the light Now two of the things that are the strongest ego defenses against love eternal love and light Our linear time, which is an entire projection in eternity. There is no linear time It's just all pure bliss and love forever and ever and ever And Some of you maybe even are familiar with the Bible. I know some of you enjoy the Bible. Some of you hate the Bible I I would say that everything that you need to know about spiritual awakening is actually in the Bible, too So let's not cross that off our list too fast Some of you might remember in Corinthians in the Bible. It says that which is temporary will pass away But that which is eternal will last forever Well, that's no different than saying nothing real can be threatened and nothing unreal exists Herein lies the peace of God. It's right there in the Bible you know, it's it's been there for thousands of years and and yet we have to be ready to Open our hearts to God's love and and to the healing power of forgiveness So linear time is a construct of the ego and you may notice that most of your thoughts during the day Relate to the past and the future if you wonder why you're not happy all the time It's just thoughts of the past and future that are still hanging around in the unconscious mind And you get little flitters and floaters During the day. Oh, what am I going to have to eat for lunch? Well, what will I have for dinner? Is it going to rain today? Is it going to be a sunny day? Will I be able to go out and take a walk? Listen, these are thoughts of the past and future These are not from Monah Maharshi thoughts. These are not Jesus Christ thoughts These are not Parma Hansa Yogananda thoughts. These are thoughts of the ego of linear time and yet we have to allow Jesus and the Holy Spirit to use the symbols of time to undo the belief in linear time See how practical Jesus and the Holy Spirit are they don't they don't try to hurl you into eternity They don't just hurl you screaming into the light They actually Common massage your mind with beautiful movies like today Which this is a mind massage no doubt this is a mind massage And it's got a lot of classic lines The main character is Joel Johnal Joel bearish who's played by Jim Cary Jim Cary and Kate Winslet is going to play Clementine. Those are our main characters But at one point Joel is having Clementine erased from his memory and he says to the doctor whose name is Howard Isn't there a risk of brain damage and the doctor answers well to some extent this whole procedure is brain damage But it's on the par with a heavy night of drinking. So don't don't worry We're not interested in brain damage. We're interested in freeing the mind of attack thoughts Freeing the mind of judgments Freeing the mind of opinions. That's where we come to the stillness of the present moment Now this movie is as I said is a classic it's in our movie watchers guide to enlightenment and When I first saw this movie in a movie theater, yeah, there was a man an elderly man who basically Said it was the worst movie he had ever seen in his life and Why am I showing you this movie is because it uses a technique That is very uncommon in movies and I'm talking about the general mainstream movies This is a it's a very unusual technique Not in a lot of our movies like like next or You know Momento or there's so many movies we have that use the same technique. I I checked it out on Google The technique is called non-linear narrative It's also called disjointed narrative or Disrupted narrative. So just those words should let you know that this is not your every day average movie If it's if it's non-linear narrative disjointed and disrupted What is it disrupting? It's disrupting the ego But that this movie is using a technique that is excellent For your meditation practice. It's excellent for your open-eyed meditation You may even consider today's movie an open-eyed meditation Where the spirit is helping you? detangle false linear memories and detangle these Special relationship memories that were made by the ego to be a substitute for light so we have a precious opportunity to really start to potentially move through what Jesus calls special love hate relationships Why is that important if we're going to wake up to eternity is that? that Jesus describes this ego construct of special relationships as the egos most boasted gift and He describes it as as the egos chief weapon it's major weapon against the Holy Spirit is is special love relationships special hate relationship and It's also the egos greatest gift. So if I go into a little bit of metaphysics to give you a background When the separation from God seemed to occur when the fall from grace That the Bible talks about seemed to occur not just the Bible all religious traditions talk about the fall from grace When this seeming fall from grace seemed to occur The Holy Spirit was given as the answer the immediate answer to this crazy mad idea So it was already over There was no Historical war to be fought it wasn't like legions of angels fell away and turned to the dark side and Lucifer rose up with a big group of Dark angels and then the light angels had a big fight. No Holy Spirit is like nah That's how long it took For for God to answer the Holy Spirit is the answer simultaneous So in other words It's that's your only purpose now is to accept the correction accept the Holy Spirit in your in your mind Accept the atonement That's your only responsibility. Do you have responsibility for houses? No Cars no cities countries politicians. No, no, no not another Do you have responsibility for children? No parents? No kitty cats No birdies Tweety birds. No You are not responsible for anything in form. You are responsible in your mind for accepting the correction of the Holy Spirit And that's why today's movie will take you light years Light years ahead in your spiritual awakening. You're not going to be Cruising along like a snail here. You're hopping into super supersonic jet today Hold on Hold on to your hat. The G's can be pretty strong, but you're gonna love it because This the corrections already occurred and and now all you have to do is accept it So it doesn't you don't have to make something happen You don't even have to figure something out all you have to do is accept your perfection And that's what the Holy Spirit's correction shows is is you're perfect Not you as a body, but your mind your spirit your divine mind is perfect So what do I like about this movie? Well, it's it's using this disjunctive a narrative approach to To undo the belief in guilt It's like if guilt was like an iceberg This movie is like a blowtorch.  That's just a projection of this Iceberg of guilt and today we're going with the blowtorch this movie uses the the technique of seemingly deleting painful Memories, but it not only deletes the painful memories it it actually deletes the positive memories and the negative memories and I know some of you are saying I Don't like that. I went the Holy Spirit to delete all the negative memories and Leave the positive memories leave my My little scrapbook of positive memories, but what Jesus says is the negative thoughts in your mind are very dark and The positive thoughts in the mind are shadows of your real thoughts. Oh my you mean my positive thoughts Ice cream is is just a shadow of my real thoughts in heaven. Yes, that's right There's no ice cream in heaven. It's it's much better than ice than ice cream in heaven But it doesn't melt Eternity doesn't melt it just lasts forever and ever and ever So so we have to allow the Holy Spirit to wash away the negative wash away the positive and leave us with the eternal thoughts and If this seems radical just read workbook less than 133 for example from the workbook. I will not value. What is valueless? Where Jesus says if it won't last forever It has no value whatsoever And if it will last forever it has complete total value. So What has value is is the everlasting? What does not have value at all is the passing this is a temporal world of time and space. It's a trick It's a sleight of hand It's a it's a it's a big trick to try to fool the mind from From going back to heaven from experiencing and remembering heaven Now I say remembering that's an important word for this movie because this movie is all about memory and If you have Egoic false memories in your mind that you are giving belief to That you're giving value to that's where the the upset emotions the upsetting emotions are coming from believing in the impossible Jesus talks about this. He starts his mind training program pretty strong there unless the number five in the workbook I'm never upset for the reason. I think I'm upset number six because I see something that's not there Number seven. I see only the past Yeah, that's a that's a perceptual problem for sure and then number eight is my mind is preoccupied with past thoughts So anytime you get upset you might as well just do a five six seven eight You know, you want a new exercise routine five six seven eight never upset for the reason I think that because I see something that's not there. I See only the past and my mind is preoccupied with past thoughts five six seven eight five six seven eight Ego tries to sneak in and upset five six seven eight Work it work those thighs work those Arms in a good way five six seven eight You're not going to mess around with this ego.  You're out You're out of there So this movie is is good because it shows the egos greatest defense against the present moment or the holy instant and that is its use of artificial relationships to attempt to gain a sense of intimacy and Jesus says that the miracle will bring about true intimacy That's sometimes sub for in interpersonal relationships So why do these romantic escapades keep crashing? Why even Cinderella, you know, she finally gets the prince in the end But in the end they both die, you know, if you go far enough into the future all All fairy tales and in death That's not exactly a happy ending sickness and death how about eternity as your Your goal Why not aim beyond the stars because the stars are just burning gases Why not aim for the eternal nature of the love and light of God? That's beyond time and space beyond the stars and planets and black holes. Oh There's Rohit I see from India Ha ha ha His dad used to beat him when he was young He would watch movies and his dad would beat him and beat him And so he developed a huge aversion to movies and let there's Rohit is showing up today He's had enough of the ego. He's gonna wash away those dead memories of the beatings We're going after the whole thing today Rohit. I Love it We're going for the homerun of spiritual awakening so What are some of the characters in the movie? Well There's a company in the movie that is is called lacuna and this company if you have Too many painful memories in a relationship This company will offer to map your brain And go in your brain to this is all just a metaphor But the brain to find your most painful memories and to eliminate the painful relationship from your mind by deleting zapping the memories of the relationship so this is the company that That that first clementine goes to when she just can't take any more of her boyfriend Joel She goes in to have Joel Deleted from her memories and then when Joel finds out about it He is so hurt that of course he goes into the same company to strike back and delete Clementine now This is a great premise you won't find a movie like this you could search For decades you're not going to find a movie like this, but this is just symbolic of the Holy Spirit Clearing the mind of all the positive and negative memories of linear time and space To come back to a state of silence a state of stillness and a state of absolute gratitude Who works for Lacuna? We have Patrick Stan Mary and Howard Patrick and Stan are kind of like you're they're the ones that that Really do the procedure Mary is the receptionist and Howard is the doctor that's in charge of the whole thing Who ever wrote this movie? What a movie you Are Holy Spirit you are giving us the most enjoyable way to wake up from linear time. I have ever Imagined this it doesn't get any better than this and then there's some friends Carrie and Rob that are our friends of Joel and They were With they invited him to a party on the beach and then that's where he met Clementine and then he mentions Naomi which is his ex girlfriend and You know, we all know that thing when you when you feel a heartbreak then the mind ego jumps right in What about the X go back to the X, you know go back to the past To try to find the intimacy. That's a nice symbol for us to see that we never will find True intimacy by going back to the past. We have to go to the holy instant with Jesus Now there's a poem in this movie that is so good It's a quote from Alexander Pope and I'm gonna read it for you because I Love it when movies are just based on something really deep and I think you know I love Solaris the Solaris movie the Dylan Thomas poem though lovers be lost Love shall not And death shall have no dominion. Whoo That is a smoking quote That is that's coming right from the light. Here's our quote for today From Alexander Pope How happy is the blameless vestal lot The world forgetting By the world for God Eternal sunshine of the spotless mind each prayer accepted and each wish resigned that That says it all that quote Is is the teachings of a course of miracles each prayer accepted each wish Resigned each ego wish resigned There's also a phrase that is so important in this movie because At the beginning of the movie we're going to see how How Joel and Clementine met Joel was on his way to work He was just ready to catch the train to go to his methodical repetitive Workday just like the Beatles song another day It's just another day. He's he's he's in his loop He's in his Groundhog Day loop and yet when he gets to the train station He decides not to go to work He bolts away and he races to barely squeeze into another train and he decides to go to Montauk Which is a very small place on the coast Up in in New England and it's it's actually a beach. He goes on a winter's day. He goes to a beach and in Montauk Why is Montauk important in this movie? It's because He needs to take a spontaneous out of pattern change To break out of the routine of his linear life To open his mind to the guidance of spirit and and he does he Breaks away from his routine. He goes to Montauk He calls in sick and he goes on on a wintry day He goes to this cold windswept beach in Montauk And that's where he meets Clementine. Why is this important? It's because We need to have the miracle of God's love Come as an out of pattern experience in our mind That we recognize and we say yes to God What's that song we like so much running for the light What's his name Brendan Brendan Lake. Oh my gosh run into the light. That's what Montauk is he Decides that he just needs to do something different. He can't do the same old routine That he's accustomed to he needs to break free and Spontaneously he goes takes a train to Montauk where he meets Clementine This is how spiritual awakening happens you you feel this strong feeling inside and You feel something that you're really called to do that's so important and As soon as you think at the egos, are you crazy? You've got to go to work today You've got to you've got to do your duties. You've got to fulfill your obligations. You've got to meet the the criteria of the day which the ego set up and You're called to be open to be shown that there is another way just like Helen Shuckman and Bill Thedford had that meeting in Bill's office and And where Bill just poured out his heart there has to be another way and and surprisingly for him Helen Shuckman said to Bill you're right Bill and I'll help you find it and that's how the prayer of the heart The collaboration that brought forth the course of miracles just started with one human being Pouring their heart out and another person saying I'll join you I will join with you in finding that better way better way to live I've had people over the years believe it or not. They send me an email and they go Dear David Meet me in Montauk How's that for an email? You you go and that's all the email says is just as David meet me in Montauk Somebody has seen this movie and it's impacted them and they got it They know they've got to go for God They've been futzing around too long with this ego time space construct It's time to go for the holy instant. It's time to go for God and Of course our closing song. Please stay around When the movie ends and the credits roll do not touch that dial Do not do not touch that off button We have a song we're gonna listen to maybe of Astanza and a chorus of the song Because that song is going to be the Holy Spirit singing to us Calling us out of the world of time and space into the eternal present so Sit back enjoy the movie. I will come in at certain points for for commentary What a fun ride we've got today this it doesn't get any more fun than having an internal dismantling of the ego that you actually enjoy and Enjoy the ride because Joel and Clementine are doing it for all of us And we're just going to behold the glory of Seeing that we can allow time and space to to be erased from our mind by the Holy Spirit We can do it Voluntarily we can do it willingly when we realize that that this is our opportunity to remember God and eternal love So enjoy the movie See you soon