Hi there, Visor CMD uses a legacy connection mode (daemon node) that might be tricky to deal with in K8S environments. Try to start it inside the same K8S network with your cluster and use a configuration with KubernetesIPFinder you used for the server nodes.
Alternatively, go for an alternate monitoring tool that is better suited for K8S: https://ignite.apache.org/features/management-and-monitoring.html - Denis On Thu, Aug 6, 2020 at 6:43 PM bbweb <[email protected]> wrote: > Hi, > > we are meeting problem when we run ignitevisorcmd in K8S and docker > environment. After we start a cluster in K8S and run ignitevisorcmd in the > node, it just can't find any node when running "top" in it, it just show > empty topology. > > Is this supported in K8S and docker? Or are there some configurations > should be done? > > Thanks for any response! > > > > > > <https://a.app.qq.com/o/simple.jsp?pkgname=com.sohu.mail.client.cordova> > > > >
