Epic Goal*

oc precheck is a command that the customer can run pre-update in 4.16 and above clusters to check for a limited number of conditions that might cause issues in upgrading the cluster. 

this command will create a report that the customer can read before they start the upgrade. 

the command output will NOT make any decisions regarding to proceed with the upgrade or not. That decision should be taken by the customer after reading the report. 

Why is this important? (mandatory)

The customer requires a command that they can run on the cluster that prints a report of cluster conditions that might affect the upgrade process. 

Scenarios (mandatory) 

1. customer uses oc precheck command to check for cluster conditions that can hinder the upgrade process like strict pdb, etc

Dependencies (internal and external) (mandatory)

this is entirely an OTA team undertaking.

Contributing Teams(and contacts) (mandatory) 

Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

• Development - OTA
• Documentation - OTA docs team
• QE - OTA
• PX - 
• Others -

Acceptance Criteria (optional)

OTA team ships a `oc precheck` command to check for cluster conditions. 

Drawbacks or Risk (optional)

We can check for frequent conditions that cause issues with upgrades, but we cannot guarantee that the cluster upgrade will go smoothly even after the customer reads the report of this command as every cluster is different and there are lot of unknowns. 

Done - Checklist (mandatory)

The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

• CI Testing - Tests are merged and completing successfully
• Documentation - Content development is complete.
• QE - Test scenarios are written and executed successfully.
• Technical Enablement - Slides are complete (if requested by PLM)
• Other