This epic tracks the cert-manager review of x/crypto usage for FIPS 140 compliance per doc here.

Identify any usage of x/crypto in cert-manager codebase and document it here: https://docs.google.com/spreadsheets/d/13q6v7ULwh6JDLma40pWgrbf9HR8cJ9psvTVqn3ECfU0/edit?usp=sharing

NOTE: all x/crypto package usage should be PER TEAM. OAPE Team will have one tab on the spreadsheet

Additionally, consider necessary code changes the ensure FIPS compliance

See doc: OpenShift x/crypto Usage and Recommendations

Why: because changes are ongoing with the main go1/crypto module, and (some of the) FIPS-level algorithms in x/crypto might move to the core crypto module, which upstream version will undergo FIPS validation testing. Until we have clarity on this ongoing work (hopefully by the end of Q1 2025), steps to remediate would be premature.

Knowing we have a problem is the first step to remediation. Please do that first step. Layered product teams must create a Jira in their respective Jira projects and link it (“blocks”) to this card.