ECK Expose Kibana Service

[Adriann (Adrian)]

Hello,

I am building ELK Stack solutions using ECK and minikube. The working solution will be uploaded to GCK. I am able to connect to kibana after I do this command from documentation
kubectl port-forward service/quickstart-kb-http 5601
But this solution is temporary because works only if the command is run in the console.

How Can I permanently "expose" kibana services to be available on specific IP and DNS name?

[stephenb (Stephen Brown)]

Perhaps you need an ingress controller if you mean you are goin to deploy on GKE (not sure what GCK is)

Here is a post I wrote on that.

Is Kibana supported on GKE through default google ingress ? doesn't seem so

Apologies I have had some other items on my plate. Remember I did this via ECK not Helm, I am an expert in neither, but I did this all very vanilla. So basically following at the steps above here is what I deployed. I did notice sometimes seems like perhaps there is a race condition or something so I deployed the elasticsearch and kibana separate and let it all come up first. Then I applied the the ingress so. kubectl -f es-kb.yml # elasticsearch kibana deploy with ECK apiVersion: elasticse…

[Adriann (Adrian)]

The problem was in my minor understanding of Kubernetes services' architecture. Thank you for your help