Aias00 opened a new issue, #704: URL: https://github.com/apache/rocketmq-dashboard/issues/704
## Problem `InMemoryK8sCertRepository` seeds production-looking certificate records at startup. Evidence: - `server/src/main/java/org/apache/rocketmq/studio/cluster/k8s/InMemoryK8sCertRepository.java` calls `initStubData()` from the constructor. - The seeded records include names such as `rmq-proxy-tls`, `rmq-broker-mtls`, and `rmq-staging-sa`. ## Impact This is in the Studio Track 1 / HTTPS and deployment configuration scope. The cert management API should not return fake TLS/mTLS/service-account records in a fresh runtime, because users can mistake them for real cluster credentials. ## Expected The in-memory repository should start empty and only return certificates that were created or saved through the API. -- 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]
