search

kubemq-io / kubemqctl

Kubemqctl is a command line interface (CLI) for KubeMQ , Kubernetes Message Broker
https://kubemq.io
Apache License 2.0
22 stars 9 forks source link

Kubemqctl will not 'get dashboard' after following quickstart #19

Closed invidious9000 closed 3 years ago

invidious9000 commented 3 years ago

Environment: minikube v1.16.0 on Microsoft Windows 10 Pro 10.0.19041 Build 19041 Kubernetes v1.20.0 on Docker 20.10.0

Approaches attempted: kubectl deployment + kubemqctl create dashboard helm operator + helm dashboard deployment

For both approaches kubemqctl get dashboard produces this output (namespace is default/ for helm):

Current Kubernetes cluster context connection: minikube
Connecting to kubernetes cluster...Current Kubernetes cluster context connection: minikube
error: no running pods available in kubemq/kubemq-dashboard.

When I examine the service using kubectl or kubernetes dashboard the service appears to be healthy, the pod is up and running in the expected namespace; I can connect to KubeMQ dashboard by port-forwarding Grafana port (3000).

kubemq commented 3 years ago

Hi, Please join our slack channel so we can support you instantly. Lior,

On Thu, Jan 14, 2021 at 3:19 AM invidious9000 notifications@github.com wrote:

Environment: minikube v1.16.0 on Microsoft Windows 10 Pro 10.0.19041 Build 19041 Kubernetes v1.20.0 on Docker 20.10.0

Approaches attempted: kubectl deployment + kubemqctl create dashboard helm operator + helm dashboard deployment

For both approaches kubemqctl get dashboard produces this output (namespace is default/ for helm):

Current Kubernetes cluster context connection: minikube Connecting to kubernetes cluster...Current Kubernetes cluster context connection: minikube error: no running pods available in kubemq/kubemq-dashboard.

When I examine the service using kubectl or kubernetes dashboard the service appears to be healthy, the pod is up and running in the expected namespace; I can connect to KubeMQ dashboard by port-forwarding Grafana port (3000).

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kubemq-io/kubemqctl/issues/19, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK5WGXCSQ3RDBRZ37QSPJIDSZZBBDANCNFSM4WBVWZJQ .

kubemq commented 3 years ago

I'll look into it

kubemq commented 3 years ago

@invidious9000 , This was fix at version v3.5.1 Thank you for reporting the issue