Epic Goal*

Add probes to OCP storage operators + operands:

• livenessprobe
• readinessprobe
• startup probe

Part of this epic is to figure out which probes make sense.

Consider all storage operators, such as:

• cluster-storage-operator
• local-storage-operator (+ diskmaker pods)
• all CSI driver operators (both CVO and OLM based)
  • CSI drivers should already have livenessprobes, consider adding readiness
• vsphere-problem-detector

Why is this important? (mandatory)

The probes could detect stale containers and restart them, making OCP more robust to random hiccups.

Scenarios (mandatory) 

Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  

1. As OCP cluster admin, I don't need to worry about a stuck LSO / diskmaker pods, because Kubernetes will restart them when they get stuck.
2. OCP operators satisfy the same criteria we impose on 3rd party operator vendors and pass "Red Hat Operator Certification Program" tests.

 Dependencies (internal and external) (mandatory)

None

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 - 
• QE - 

Acceptance Criteria (optional)

Consider running "Red Hat Operator Certification Program" for the OLM based operators - it should catch these issues.

Drawbacks or Risk (optional)

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 -  Basic e2e automationTests 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)
• Engineering Stories Merged
• All associated work items with the Epic are closed
• Epic status should be "Release Pending"