Epic Goal

Certificate Analyzer Script Execution:

1. Run the command as the kube-admin user.
2: Run the bash script located in this repository: https://github.com/racedo/openshift-certificate-analyzer/tree/main/Bash%20Script

Data Submission:

1. Use the certificate data gathered from the Live OCP environment via the script in step 2 (run bash script).
2. Provide the collected data (either as a .csv file or individual rows) for your specific operator into the designated spreadsheet: https://docs.google.com/spreadsheets/d/1ksDSGWS31IWh3qx8gXei6KZLslqPEFwMo6NwwfzFBNM/edit?gid=981328049#gid=981328049

Why is this important?

Per request of https://groups.google.com/a/redhat.com/g/operatorframework-pgm/c/XNBF19Tm9oY

Planning Done Checklist

The following items must be completed on the Epic prior to moving the Epic from Planning to the ToDo status

• Priority+ is set by engineering
• Epic must be Linked to a +Parent Feature
• Target version+ must be set
• Assignee+ must be set
• (Enhancement Proposal is Implementable
• (No outstanding questions about major work breakdown
• (Are all Stakeholders known? Have they all been notified about this item?
• Does this epic affect SD? {}Have they been notified{+}? (View plan definition for current suggested assignee)
  1. Please use the “Discussion Needed: Service Delivery Architecture Overview” checkbox to facilitate the conversation with SD Architects. The SD architecture team monitors this checkbox which should then spur the conversation between SD and epic stakeholders. Once the conversation has occurred, uncheck the “Discussion Needed: Service Delivery Architecture Overview” checkbox and record the outcome of the discussion in the epic description here.
  2. The guidance here is that unless it is very clear that your epic doesn’t have any managed services impact, default to use the Discussion Needed checkbox to facilitate that conversation.

Additional information on each of the above items can be found here: Networking Definition of Planned

Acceptance Criteria

No CI or Technical Enablement required.