You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "Aias00 (via GitHub)" <gi...@apache.org> on 2026/09/15 14:19:50 UTC
[I] [Studio][UX] Clarify supported NameServer address formats [rocketmq-dashboard]
Aias00 opened a new issue, #4346:
URL: https://github.com/apache/rocketmq-dashboard/issues/4346
## Problem
Studio intentionally connects to operator-provided NameServer addresses, but the cluster configuration form does not explain which address forms are supported. Operators deploying RocketMQ behind a load balancer or in Kubernetes may incorrectly assume Studio requires a Pod IP or a Kubernetes discovery integration.
The configured address can already be any address reachable from Studio, including an SLB/VIP, a headless Service DNS name, or a comma-separated NameServer list. This capability is not discoverable in the current form.
## Expected behavior
- Explain that Studio connects directly to the configured NameServer address.
- Document supported examples: SLB/VIP, headless Service DNS, and comma-separated addresses.
- Keep the guidance visible near the existing cluster/NameServer form.
- Use the existing `InfoBanner` and localized Chinese/English text.
- Do not add Kubernetes API access, automatic discovery, background synchronization, RBAC, or new backend configuration.
## Acceptance criteria
- The cluster form shows the address guidance in Chinese and English.
- The guidance makes the connectivity boundary clear: the address must be reachable from the Studio server.
- Existing cluster creation and update behavior is unchanged.
- Focused form tests, the frontend build, lint, and formatting checks pass.
## Context
This is the scoped UX follow-up requested by the maintainer when closing the Kubernetes discovery direction in #3133. The broader Kubernetes integration issue #3132 is closed as not planned.
--
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: commits-unsubscribe@rocketmq.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Studio][UX] Clarify supported NameServer address formats [rocketmq-dashboard]
Posted by "lizhimins (via GitHub)" <gi...@apache.org>.
lizhimins closed issue #4346: [Studio][UX] Clarify supported NameServer address formats
URL: https://github.com/apache/rocketmq-dashboard/issues/4346
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Studio][UX] Clarify supported NameServer address formats [rocketmq-dashboard]
Posted by "RockteMQ-AI (via GitHub)" <gi...@apache.org>.
RockteMQ-AI commented on issue #4346:
URL: https://github.com/apache/rocketmq-dashboard/issues/4346#issuecomment-5683609944
**Issue Evaluation**
Category: `enhancement` | Status: **Evaluated**
**Feasibility:** Feasible — straightforward frontend UX improvement
**Scope:** Studio Ops page (connection form) + NameServer address parsing utility
**Compatibility:** No breaking changes
The issue correctly identifies a UX gap: users are unsure about supported NameServer address formats (host:port, multiple addresses separated by semicolons, etc.). Adding inline format hints, validation feedback, and a link to the documentation would reduce connection configuration errors.
**Suggested approach:**
1. Add a placeholder/hint text in the NameServer address input field showing the expected format (e.g., `host1:9876;host2:9876`)
2. Add real-time validation with a clear error message when the format is invalid
3. Link to the relevant documentation page for detailed format specification
This is a low-effort, high-value UX improvement.
---
*Automated evaluation by RockteMQ-AI*
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Studio][UX] Clarify supported NameServer address formats [rocketmq-dashboard]
Posted by "lizhimins (via GitHub)" <gi...@apache.org>.
lizhimins commented on issue #4346:
URL: https://github.com/apache/rocketmq-dashboard/issues/4346#issuecomment-5755109499
Resolved by #4383, merged into `rocketmq-studio` as 40a8f6a.
The NameServer create/edit dialog and the connection-test dialog now carry a
neutral InfoBanner stating that Studio connects to the address from the server
side (so it must be reachable from the Studio server) and listing the supported
forms: SLB/VIP, headless Service DNS such as
`namesrv.mq.svc.cluster.local:9876`, and a comma-separated NameServer list such
as `ns1:9876,ns2:9876`. Both zh and en strings are provided and covered by
ClusterPage tests.
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Studio][UX] Clarify supported NameServer address formats [rocketmq-dashboard]
Posted by "Yanghanrui666 (via GitHub)" <gi...@apache.org>.
Yanghanrui666 commented on issue #4346:
URL: https://github.com/apache/rocketmq-dashboard/issues/4346#issuecomment-5695741481
I would like to claim this issue. I will add localized NameServer address guidance to the Cluster/NameServer forms with the existing InfoBanner, covering SLB/VIP, headless Service DNS, comma-separated addresses, and the requirement that the address be reachable from the Studio server. I will include focused Chinese/English regression tests.
/assign
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org