Market Problem 

1. Improving openshift stability by adding new feature in openshift core components like kubelet , scheduler , API server, CRI-O that will improve openshift uptime or enable Red Hat to debug customer problem faster 
2. Improving openshift performance by adding new feature in openshift core component like kubelet , scheduler , API server, CRI-O  that will enable customer to start and run their  workload faster on openshift
3. Improving openshift performance by adding new feature in openshift core component like kubelet , scheduler , API server, CRI-O  that will enable customer to improve pod density or number pods on a bare metal server 
4. Adding features in core openshift like kubelet , scheduler , API server , CRI-O to support new platforms like Service Mesh, Kata and Kubevirt and any future components 
5. Adding feature in core openshift like kubelet , scheduler , API server , CRI-O to specialized workloads Telco, AI/ML, kubevirt and any new future platforms 

Why it matters 

1. As an openshift admin who is running production workload on openshift i want to make sure maximum uptime of my workload or faster recovery of the platform so that there is least disruption in running business critical application on openshift 
2. As a openshift admin who is running production workload on openshift i want to improve performance of my workload so that i can run my workload faster on openshift 
3. As a openshift admin who is running openshift on bare metal hosts i want to improve number of pods that i can provision on a bare metal host so that i don't have to buy new servers or use virtualization .