RockteMQ-AI commented on issue #1314: URL: https://github.com/apache/rocketmq-dashboard/issues/1314#issuecomment-5231954038
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** **Feasibility:** feasible (but requires significant new infrastructure) **Scope:** New Kubernetes provider module, certificate lifecycle management, instance credential integration **Compatibility:** No breaking changes — this is additive This is a well-structured design proposal. The current codebase has no Kubernetes integration or cert-manager connectivity — the K8s certificate screen persists records locally in Studio only. Key considerations: 1. **Provider abstraction** — A new `KubernetesCertificateProvider` interface would be needed, with implementations for direct K8s API and cert-manager CRD operations. 2. **Instance credential binding** — The provider would need to resolve K8s cluster credentials from the selected instance configuration. 3. **UI transparency** — The suggestion to clearly surface "Studio-local vs. cluster-applied" state is important for user trust. 4. **Gradual rollout** — Consider implementing a "read-only inventory" phase first (list certs from cluster) before adding create/renew/delete operations. This would benefit from a design document or RFC before implementation. --- *Automated evaluation by github-manager-bot* -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
