Hi, Then Visor CMD should work fine. Please share your configs and logs for analysis.
As for the alternate UI tools, yes, you can deploy those in Docker. Just google for respective documentation. Denis On Thursday, August 6, 2020, bbweb <[email protected]> wrote: > Hi Denis, Actaully we are running visor CMD in the same container with > Ignite server, and using the same configuration file with > KubernetesIPFinder that ignite server use. Should this mode be supported? > And for the link provided, does it mean that web console can also be used? > Thanks! - Bright > > ----- 原始邮件 ----- > > *发件人：*Denis Magda<[email protected]> > > *发送时间：*2020-08-07 11:53:11 > > *收件人：*user<[email protected]> > > *主 题：*Re: run ignitevisorcmd in k8s and docker？ > > 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 aremeeting problem when we run ignitevisorcmd in K8S and docker > environment. Afterwe start a cluster in K8S and run ignitevisorcmd in the > node, it just can'tfind any node when running "top" in it, it just show > empty topology. > > Is thissupported 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> > > > > > > > <https://a.app.qq.com/o/simple.jsp?pkgname=com.sohu.mail.client.cordova> > > > > -- - Denis
