Aias00 opened a new issue, #1314: URL: https://github.com/apache/rocketmq-dashboard/issues/1314
## Problem The current K8s certificate screen persists certificate records in Studio. Create, renew, and delete operations do not read or mutate certificates in a Kubernetes cluster or cert-manager. The UI needs an explicit provider boundary before it is presented as cluster runtime management. ## Scope Track 1 / Control Plane: K8s operational view and provider abstraction. ## Proposed direction 1. Define an instance-scoped Kubernetes certificate provider capability. 2. Resolve the provider from the selected instance and its credentials. 3. Implement inventory, renewal, and deletion through Kubernetes APIs or cert-manager. 4. Preserve Studio-local metadata only as explicit configuration/cache data, and surface unsupported capability states clearly. ## Immediate behavior Until a provider exists, the UI should state that the current records are Studio-local and are not applied to a Kubernetes cluster. -- 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]
