Aias00 opened a new pull request, #3133: URL: https://github.com/apache/rocketmq-dashboard/pull/3133
### Summary - add an administrator-triggered, namespace-scoped Kubernetes NameServer discovery API using Fabric8 7.8.0 - discover candidates in order: Service port/name hints, ready EndpointSlices, component/name label Pod queries, then a bounded full Pod image fallback - require ready endpoints before reporting normal Service DNS candidates and aggregate multi-slice IPv4/IPv6 addresses - return source, confidence and stability metadata without mutating Kubernetes or the Studio registry - add a NameServer management flow that lets users review a candidate and prefill the existing create form before saving - add default-off configuration, Docker environment passthrough, minimum namespace RBAC and connectivity documentation ### Safety boundaries - no `inAnyNamespace()` or ClusterRole requirement - no Secret/certificate access and no Kubernetes mutations - no background watch or automatic registry synchronization - ServiceAccount/kubeconfig material stays server-side through Fabric8 auto-configuration - stale frontend discovery responses are ignored after close/reopen ### Verification - `JAVA_HOME=/Users/aias/Library/Java/JavaVirtualMachines/openjdk-21.0.2/Contents/Home mvn -Dtest=KubernetesNameServerDiscoveryServiceTest,NameServerControllerTest test` (27 passed) - `NODE_ENV=test npm test -- src/api/cluster.test.ts src/pages/cluster/__tests__/ClusterPage.test.tsx` (38 passed) - `NODE_ENV=test npm test` (115 files, 925 tests passed) - `npm run lint` (0 errors; 10 existing warnings) - `npm run build` - `git diff --check` Full Maven suite note: 2043/2046 tests passed. The three failures are existing unrelated assertions in `AuthCorsIntegrationTest` (2) and `AliyunInstanceProviderTest` (1), reproducible on the base branch and previously tracked in adjacent Studio work. Closes #3132 -- 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]
