This issue appears only when the Kubernetes cluster dashboard is displayed from one site which has a “Distributed Monitoring” connector configured to reach the actual site running the Kubernetes monitoring.
The value required used in the dashboard is transmited only in “Distributed Monitoring” connections using LivestatusProxy, not using in Direct Connection.
For posterity: This is due to the fact, that the name comes from the HW/SW inventory, which is only replicated to the central site when using Liveproxyd.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.