我已经将基班纳部署到kubernetes集群,作为StatefulSet。但是,当我的浏览器指向kibana时,它会返回{"statusCode":404,"error":"Not“,"message":"Not”}。任何建议和洞察力都将受到赞赏。下面是我在浏览器上使用http://app.domain.io/kibana访问应用程序时在荚中看到的日志
{"type":"response","@timestamp":"2019-01-29T04:18:50Z","tags":[],"pid":1,"method":"get","statusCode":404,"req":{"url":"/kibana","method":"get","headers":{"x-forwarded-for":"[IP]","x-forwarded-proto":"https","x-forwarded-port":"443","host":"[host]","x-amzn-trace-id":"Root=1-5c4fd42a-1261c1e0474144902a2d6840","cache-control":"max-age=0","upgrade-insecure-requests":"1","user-agent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36","accept":"text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8","accept-encoding":"gzip, deflate, br","accept-language":"en-US,en;q=0.9,zh-CN;q=0.8,zh-TW;q=0.7,zh;q=0.6,ko;q=0.5"},"remoteAddress":"[IP]","userAgent":"10.0.2.185"},"res":{"statusCode":404,"responseTime":19,"contentLength":9},"message":"GET /kibana 404 19ms - 9.0B"}apiVersion: v1
kind: Service
metadata:
name: svc-kibana
labels:
app: app-kibana
spec:
selector:
app: app-kibana
# tier: database
ports:
- name: kibana
protocol: TCP
port: 8080
targetPort: 5601
clusterIP: None # Headless
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: kibana
spec:
serviceName: "svc-kibana"
podManagementPolicy: "Parallel" # Default is OrderedReady
replicas: 1 # Default is 1
selector:
matchLabels:
app: app-kibana # Has to match .spec.template.metadata.labels
template:
metadata:
labels:
app: app-kibana # Has to match .spec.selector.matchLabels
spec:
terminationGracePeriodSeconds: 10
containers:
- name: kibana
securityContext:
capabilities:
add:
- IPC_LOCK
- SYS_RESOURCE
image: kibana:6.5.4
imagePullPolicy: Always
env:
- name: ELASTICSEARCH_URL
value: http://svc-elasticsearch:9200
- name: SERVER_BASEPATH
value: /api/v1/namespaces/default/services/svc-kibana/proxy
ports:
- containerPort: 5601
name: kibana
protocol: TCP以下是AWS ALB的健康检查:
{"type":"response","@timestamp":"2019-01-29T06:30:53Z","tags":[],"pid":1,"method":"get","statusCode":200,"req":{"url":"/app/kibana","method":"get","headers":{"host":"[IP]:5601","connection":"close","user-agent":"ELB-HealthChecker/2.0","accept-encoding":"gzip, compressed"},"remoteAddress":"[IP]","userAgent":"[IP]"},"res":{"statusCode":200,"responseTime":27,"contentLength":9},"message":"GET /app/kibana 200 27ms - 9.0B"}我尝试删除ENV值,并使用安装在/etc/kibana/kibana.yml上的ConfigMap,配置如下,但没有效果:
apiVersion: v1
kind: ConfigMap
metadata:
creationTimestamp: "2019-01-29T02:12:55Z"
name: kibana-config
namespace: default
resourceVersion: "4178388"
selfLink: /api/v1/namespaces/default/configmaps/kibana-config
uid: 63b10866-236b-11e9-a14d-482ae31e6a94
data:
kibana.yml: |+
server.port: 5601
server.host: "0.0.0.0"
elasticsearch.url: "http://svc-elasticsearch:9200"
kibana.index: ".kibana"
logging.silent: false
logging.quiet: false
logging.verbose: true发布于 2019-01-29 08:10:20
在我将以下内容添加到Kibana配置之后,它现在可以工作了:
server.basePath: "/my-kibana"
server.rewriteBasePath: true多亏了马修·L·丹尼尔,我把健康检查换成了/my-kibana/api/status
发布于 2019-01-29 07:22:18
- name: SERVER_BASEPATH
value: /api/v1/namespaces/default/services/svc-kibana/proxy是导致问题的错误设置吗?因为server.basePath被记录为
使您能够指定一个路径,如果您正在运行在代理后面,则可以在该路径上挂载Kibana。使用
server.rewriteBasePath设置告诉Kibana它是否应该从接收到的请求中删除basePath,并防止在启动时发出弃用警告。此设置不能以斜杠(/)结尾。
因此,您必须使用/api/v1/namespaces/default/services/svc-kibana/proxy/app/kibana,因为您没有覆盖server.defaultRoute: /app/kibana。我不知道为什么ELB健康检查只返回9字节的内容,但您可能还是希望使用/api/status作为它的健康检查。
发布于 2020-02-18 10:23:27
我在kubernetes集群中也面临着同样的问题,在这个集群中,kibana运行在nginx代理之后。
DNS: https://my-url/dashboard
Nginx conf:
location /dashboard/ {
rewrite ^/dashboard/(.*) /$1 break;
proxy_pass http://kibana:5601/;在按角添加上述建议的参数后,如何在kibana.yml中使用
kibana.yml:
server.name: kibana
server.host: "0"
elasticsearch.url: http://elasticsearch:9200
server.basePath: "/dashboard" #this line解决了重定向问题。
https://stackoverflow.com/questions/54413885
复制相似问题