 Hey everyone! Today I'm going to introduce you to a new feature of OpenShift cluster manager, Insights for OpenShift. Red Hat Insights has been around for more than four years and for Red Hat Enterprise Linux customers it practically identifies potential issues and also offers remediation steps. Today we're expanding this and offering this functionality to OpenShift for customers as well. The Insights extension is part of OpenShift cluster manager that you will find on CloudStreet.com where you login with your standard Red Hat Access Port credentials. After logging into OpenShift cluster manager you will see the list of clusters that you ever installed or subscribed. As you probably know OpenShift cluster manager is used to provision new clusters but also to review subscriptions, do a basic management of clusters including updates and you will also have an overview of audio installed clusters. I'm gonna search for my cluster and the first one is a cluster that I installed a couple days ago. It's a cluster running on the AWS. It's one of the recent OpenShift versions and the new feature that is just added to OpenShift cluster manager is this new Insights tab. In this case the Insights is telling me that there is one potential issue identified but this is a testing issue and it's only telling you what kind of notifications you'll be getting here once a potential problem is identified by Insights. So let's look at a cluster that actually has some Insights problem identified and for that I have this demo cluster here. I really hope that you will never have a cluster this broken. This cluster has seven potential issues identified and as you can see these issues have different severity and also the health checks identified or performed by Insights are spread into different categories. So let's look at the important ones first. The important health checks are something you should pay special attention to as they often may result in degraded or failing cluster for our first issue here. A wrong configuration of secure context constraints may actually prevent this cluster from being upgraded. Let's look at the details here and here are all the information that you can find if you wish to see in more details. You can always go to Red Hat Access Portal and review the associated knowledge based article but I'm actually curious about the remediation steps and in this case it's actually fairly easy. The OpenShift Support Team has verified that course upgrading this cluster to this version will actually solve the problem for you. All right let's see and I can run this command and guess this if it fits. Well let's look at some other issues identified by Insights. What else do I have here? I actually have some moderate issue that I should pay attention to as well. Why is this OCP node potentially behaving as expected? Oh apparently there are minimum requirements that my node is not needed. Let's look at the details. So in this case I'm presented with this very node that doesn't have the requested amount of CPUs. Well I guess the remediation steps are here. Just get the CPUs up. So that is why it was easy but it's basically showing me that I did something wrong by installing the cluster and this node might not behave as expected. The Insights expansion allows me to filter issues by different categories as well. I can look at security issues and there's one related to authentication upgrade. Again I can look at very details of this. In this case a cluster write works a second might actually break the authentication upgrade. I can filter this year and search for issues that are related to cluster upgrades. All these health checks are continuously added by Red Hat support engineers and verified by Red Hat product engineers working on their future. I hope you'll find this new feature helpful and hopefully this goal helps you to prevent some of the issues that your cluster might encounter. We would love to hear your feedback and thanks for watching.