@Rocky does starocks any UI that can be enabled using starrocks helm chart. ?

StarRocks does not have a separate "Management UI" or "Manager" component included in the community Helm chart. However, it provides two primary ways to access a UI for your cluster: 1. Built-in FE Web Console (Port 8030) Each StarRocks Frontend (FE) node has a built-in web-based console. You can use it to view cluster status, node information, and query metadata. * Default Port:

8030

* Requirements: You must have the

cluster_admin

role to log in. * How to access using Helm: * By default, the FE service is internal (

ClusterIP

). To access the UI from outside the cluster, change the service type to

LoadBalancer

or

NodePort

in your `values.yaml`:

yaml
        starrocks:
          starrocksFESpec:
            service:
              type: LoadBalancer

* Once deployed, get the external IP and visit

http://<EXTERNAL_IP>:8030

. 2. FE Proxy (Port 8080) The Helm chart includes an optional FE Proxy (Nginx-based) that can be enabled. While its primary purpose is to handle HTTP 307 redirections for data loading (Stream Load), it also acts as a reverse proxy to the FE Web UI. * To enable in `values.yaml`:

yaml
    starrocks:
      starrocksFeProxySpec:
        enabled: true
        service:
          type: LoadBalancer

* Access: Visit

http://<PROXY_IP>:8080

to reach the FE console. 3. Monitoring Dashboards (Grafana) For performance monitoring and visualization, StarRocks provides a community-supported Grafana Dashboard. * This is not "enabled" in the StarRocks Helm chart itself. * Instead, you deploy the Prometheus and Grafana Helm charts and import the official StarRocks dashboard template (ID:

22909

). Summary * FE Web UI: Built-in to every FE; just needs to be exposed via Service or Ingress. * StarRocks Manager: This is typically a commercial/enterprise feature (from CelerData) and is not part of the open-source community Helm chart. * Monitoring UI: Recommended via Prometheus/Grafana integration. References • administration/management/FE_configuration.md • administration/user_privs/authorization/privilege_faq.md • administration/http_interface.md • sql-reference/sql-statements/cluster-management/nodes_processes/SHOW_FRONTENDS.md • developers/development-environment/IDEA.md

can I use root creds to login to fe UI .? what creds should I use .? @Rocky

Yes, you can use the

root

user to log in to the FE Web UI. Default Credentials If you have just deployed the cluster and haven't changed the password: * Username:

root

* Password: (Leave blank/empty) Requirements to Log In To access the FE Web UI (

http://<FE_IP>:8030

), the user must have the

cluster_admin

role. * The

root

user has this role by default as it possesses all privileges in the cluster. * If you create a custom user, you must grant them the

cluster_admin

role (e.g.,

GRANT cluster_admin TO USER 'your_user';

) to allow them to access the UI. How to Access (Helm) 1. Find the Service: If you are using the StarRocks Helm chart, locate the FE service. If it's a

ClusterIP

, you'll need to port-forward:

bash
    kubectl port-forward svc/<release-name>-starrocks-fe 8030:8030

2. Open Browser: Go to

<http://localhost:8030>

. 3. Login: Enter

root

and your password (empty by default). Security Note It is highly recommended to set a password for the

root

user immediately after deployment using a MySQL client:

sql
SET PASSWORD FOR 'root' = PASSWORD('your_new_password');

References • administration/user_privs/authorization/privilege_faq.md • deployment/post_deployment_setup.md • deployment/deploy_manually.md References • administration/user_privs/authentication/native_authentication.md • deployment/deploy_manually.md • administration/user_privs/authorization/privilege_faq.md • administration/management/FE_configuration.md • faq/Deploy_faq.md • deployment/post_deployment_setup.md