Cannot access Kiali UI on GKE via Ingreess or port-forward.

[Rukeith Tseng]

I use Kiali Operator to install Kiali on GKE.

After run script 

bash <(curl -L https://git.io/getLatestKialiOperator)

I run this and open browser

kubectl port-forward svc/kiali 20001:20001 -n istio-system

I got this page.

Then I saw the ingress cannot be create 

Pod and service is created and status is OK.

[Joel Takvorian]

Isn't Kiali deployed under "/kiali" path here? I guess you should append it to the URL

--
You received this message because you are subscribed to the Google Groups "kiali-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kiali-dev+...@googlegroups.com.
To post to this group, send email to kial...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kiali-dev/76a63d39-542f-4b90-94ae-a3a0bd8b3bcc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Joel Takvorian]

PS: is the pod in a correct (running) state, and is there any error on logs?

[Lucas Ponce]

Also keep in mind that by default, Kiali is https traffic.

So, using port-forward the URL should something like:

https://localhost:20001/kiali

To view this discussion on the web visit https://groups.google.com/d/msgid/kiali-dev/CAJo5TF%3DNrw-mEHYx5LJBwNZE0Mv3jt%2BpM0EgfzNTK1ahXGMQJg%40mail.gmail.com.

[Rukeith Tseng]

Hi Joel and Lucas,

    Pod is in a correct state and the service is at same state. Only ingress is unhealthy.

I have used https://localhost:20001/kiali, but I will got the error chrome will block the website. Because the ssl key cannot resolve on localhost.

So I edit `/etc/hosts` give a fake domain to localhost, and got the nginx error page.

Rukeith Tseng於 2019年7月9日星期二 UTC+8下午3時59分27秒寫道：

[Rukeith Tseng]

I got error from Browser when I open https://localhost:20001/kiali

Rukeith Tseng於 2019年7月9日星期二 UTC+8下午3時59分27秒寫道：

[Lucas Ponce]

On Tue, Jul 9, 2019 at 10:34 AM Rukeith Tseng <fenglan.c...@gmail.com> wrote:

Hi Joel and Lucas,

    Pod is in a correct state and the service is at same state. Only ingress is unhealthy.

I have used https://localhost:20001/kiali, but I will got the error chrome will block the website. Because the ssl key cannot resolve on localhost.

So I edit `/etc/hosts` give a fake domain to localhost, and got the nginx error page.

Yes, you need to add an exception, an alternative way is to expose Kiali with ingress.

https://istio.io/docs/tasks/telemetry/gateways/

Then you can also to control better your certificates.

Or alternative, you can also to expose Kiali via HTTP, if you are using it for demos/development.

I have a tutorial about it under this link:

https://lucasponce.github.io/presentations/install-istio-kiali.html

 

Rukeith Tseng於 2019年7月9日星期二 UTC+8下午3時59分27秒寫道：

I use Kiali Operator to install Kiali on GKE.

After run script 

bash <(curl -L https://git.io/getLatestKialiOperator)

I run this and open browser

kubectl port-forward svc/kiali 20001:20001 -n istio-system

I got this page.

Then I saw the ingress cannot be create 

Pod and service is created and status is OK.

--
You received this message because you are subscribed to the Google Groups "kiali-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kiali-dev+...@googlegroups.com.
To post to this group, send email to kial...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/kiali-dev/b7193b45-510e-4c65-ac3d-367e4afc380a%40googlegroups.com.