>
> *发件人：*Denis Magda
>
> *发送时间：*2020-08-07 11:53:11
>
> *收件人：*user
>
> *主 题：*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 star
!
-
Bright- 原始邮件 -发件人：Denis Magda发送时间：2020-08-07 11:53:11收件人：user主 题：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
Hi
bbweb wrote:
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.
Do you have any error log?
Ar
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 wrote:
> Hi,
>
> we are meeting problem when we run ignitevisorcmd in K8S and docker
> environment. After we start a cl
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
