Serving: Kibana UI not accessible

Created on 28 May 2019 · 7Comments · Source: knative/serving

In what area(s)?

knative-monitoring kibana-logging deployment

What version of Knative?

0.6.0

Expected Behavior

access the url: http://xxx.xxx.xxx:5601 kibana UI will be shown, seems caused by the deployment with SERVER_BASEPATH configured

Actual Behavior

redirected: http://xxx.xxx.xxx:5601/api/v1/namespaces/knative-monitoring/services/kibana-logging/proxy/app/kibana, and complains: {"statusCode":404,"error":"Not Found","message":"Not Found"}

Steps to Reproduce the Problem

after installation and changed the kibana-logging svc type from nodeport to loadbalancer
access the url with external ip and port 5601

aremonitoring kinbug lifecyclrotten

Source

jeffcai

Most helpful comment

By default, Kibana shouldn't be publicly exposed and it is not exposed.
You can change that of course, but then you are responsible for the change.
What we provide by default works.

Anyway, this is outside of Knative scope, it is standard Kibana stuff.
I'll submit a PR to add a comment to third_party/config/monitoring/logging/elasticsearch/elasticsearch.yaml about SERVER_BASEPATH.

JRBANCEL on 5 Jun 2019

👍2

All 7 comments

kubectl edit deployments -n knative-monitoring kibana-logging

Remove:

 - name: SERVER_BASEPATH
   value: /api/v1/namespaces/knative-monitoring/services/kibana-logging/proxy

kubectl edit services -n knative-monitoring kibana-logging

Change the NodePort to LoadBalancer.

Then:

curl -v http://$(kubectl get services -n knative-monitoring kibana-logging -o go-template='{{ index (index .status.loadBalancer.ingress 0) "ip"}}'):5601/app/kibana | head

Returns:

GET /app/kibana HTTP/1.1
...
HTTP/1.1 200 OK

Does this not work?

JRBANCEL on 4 Jun 2019

it works, what I meant is that by default if we need make it work, or something else considered by adding the config.

jeffcai on 5 Jun 2019

By default, Kibana shouldn't be publicly exposed and it is not exposed.
You can change that of course, but then you are responsible for the change.
What we provide by default works.

JRBANCEL on 5 Jun 2019

👍2

Issues go stale after 90 days of inactivity.
Mark the issue as fresh by adding the comment /remove-lifecycle stale.
Stale issues rot after an additional 30 days of inactivity and eventually close.
If this issue is safe to close now please do so by adding the comment /close.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/lifecycle stale

knative-housekeeping-robot on 23 Dec 2019

Stale issues rot after 30 days of inactivity.
Mark the issue as fresh by adding the comment /remove-lifecycle rotten.
Rotten issues close after an additional 30 days of inactivity.
If this issue is safe to close now please do so by adding the comment /close.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/lifecycle rotten

knative-housekeeping-robot on 22 Jan 2020

Rotten issues close after 30 days of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh by adding the comment /remove-lifecycle rotten.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/close

knative-housekeeping-robot on 21 Feb 2020

@knative-housekeeping-robot: Closing this issue.

In response to this:

Rotten issues close after 30 days of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh by adding the comment /remove-lifecycle rotten.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.