Aias00 opened a new issue, #3128: URL: https://github.com/apache/rocketmq-dashboard/issues/3128
### Background The Studio K8s certificate page stores local configuration and metadata only. It is not connected to Kubernetes Secrets, cert-manager `Certificate` resources, or any Kubernetes client. Maintainer review concluded that Kubernetes certificate lifecycle management is outside the RocketMQ dashboard scope. The current `/api/k8s-certs/renew` implementation only advances locally stored validity dates and can therefore imply a renewal that never happened in Kubernetes. Separate enhancement branches add PEM replacement and mTLS key matching, but consolidating more certificate lifecycle logic would move the dashboard further away from RocketMQ operations. ### Scope - Remove the local certificate renewal endpoint, DTO, service behavior, web API/service wrapper, mocks, tests, and audit presentation entries. - Remove documentation claims that Studio renews Kubernetes certificates. - Retire the proposed Kubernetes certificate provider/lifecycle design. - Keep the existing Studio-local certificate configuration surface: list, create, update, delete, PEM metadata parsing, expiry/status display, and NameServer `k8sId` selection. - Keep the UI explicit that these records are Studio-local configuration and do not modify Kubernetes resources. ### Non-goals - Removing the pre-existing K8s certificate page or database table; that can be handled by a separate cleanup proposal. - Adding a Kubernetes client, cert-manager integration, Secret inventory, renewal, or deletion. - Changing NameServer K8s metadata fields. ### Acceptance criteria - `POST /api/k8s-certs/renew` is no longer exposed. - No frontend or mock service exports a certificate renewal operation. - No K8s certificate renewal audit label remains. - README, API documentation, and page messaging describe local configuration only. - The provider lifecycle proposal is removed so it is not mistaken for an active roadmap. - Targeted server and web tests pass. -- 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]
