Add retirement notice and cert-manager migration plan#187
Open
mathianasj wants to merge 1 commit into
Open
Conversation
**Changes:** 1. Added retirement notice to README.md - Clearly states project is no longer in active development - Links to comprehensive migration plan - Positioned prominently at top of README 2. Added CERT_MANAGER_MIGRATION_PLAN.md - Comprehensive migration analysis (85% of features can migrate) - Historical context: cert-utils designed as cert-manager companion - Feature-by-feature comparison with migration steps - Three migration strategies with timeline and effort estimates - Recommendation: migrate to cert-manager ecosystem **Migration Feasibility: 85%** ✅ PKCS12 keystores → cert-manager native keystores.pkcs12 (v1.7+) ✅ JKS truststores → trust-manager with JKS format ✅ OpenShift Routes → openshift-routes controller ✅ Webhook CA injection → ca-injector (direct replacement) ✅ ConfigMap CA injection → trust-manager Bundle CR pattern ✅ Certificate expiry metrics → cert-manager native metrics 🛑 Secret-to-Secret CA injection → NO EQUIVALENT (workaround: projected volumes) 🛑 Human-readable cert info → NO EQUIVALENT (workaround: external tools) **Rationale:** cert-manager ecosystem has evolved significantly since 2019-2020 when cert-utils-operator was created. Most gaps that cert-utils filled now have native cert-manager solutions. Benefits of consolidating on CNCF standard tooling (active development, large community, enterprise support) outweigh costs (2 missing features with documented workarounds). Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After careful consideration, and analysis of what features are now part of cert-manager that we initially covered in the OpenShift ecosystem are now part of the proper cert-manager project. It is now time to retire this operator and document the migration path to other projects.
Changes:
Added retirement notice to README.md
Added CERT_MANAGER_MIGRATION_PLAN.md
Migration Feasibility: 85%
✅ PKCS12 keystores → cert-manager native keystores.pkcs12 (v1.7+) ✅ JKS truststores → trust-manager with JKS format
✅ OpenShift Routes → openshift-routes controller
✅ Webhook CA injection → ca-injector (direct replacement) ✅ ConfigMap CA injection → trust-manager Bundle CR pattern ✅ Certificate expiry metrics → cert-manager native metrics 🛑 Secret-to-Secret CA injection → NO EQUIVALENT (workaround: projected volumes) 🛑 Human-readable cert info → NO EQUIVALENT (workaround: external tools)
Rationale:
cert-manager ecosystem has evolved significantly since 2019-2020 when cert-utils-operator was created. Most gaps that cert-utils filled now have native cert-manager solutions. Benefits of consolidating on CNCF standard tooling (active development, large community, enterprise support) outweigh costs (2 missing features with documented workarounds).