目前apiserver上的日志分别为
host
E1016 01:31:09.607227 1 backend.go:172] send audit events error, Post “https://kube-auditing-webhook-svc.kubesphere-logging-system.svc:443/audit/webhook/event”: dial tcp: lookup kube-auditing-webhook-svc.kubesphere-logging-system.svc on 172.21.0.10:53: no such host
E1016 01:31:18.608242 1 backend.go:172] send audit events error, Post “https://kube-auditing-webhook-svc.kubesphere-logging-system.svc:443/audit/webhook/event”: dial tcp: lookup kube-auditing-webhook-svc.kubesphere-logging-system.svc on 172.21.0.10:53: no such host
E1016 01:31:30.610386 1 backend.go:172] send audit events error, Post “https://kube-auditing-webhook-svc.kubesphere-logging-system.svc:443/audit/webhook/event”: dial tcp: lookup kube-auditing-webhook-svc.kubesphere-logging-system.svc on 172.21.0.10:53: no such host
E1016 01:31:36.611542 1 backend.go:172] send audit events error, Post “https://kube-auditing-webhook-svc.kubesphere-logging-system.svc:443/audit/webhook/event”: dial tcp: lookup kube-auditing-webhook-svc.kubesphere-logging-system.svc on 172.21.0.10:53: no such host
E1016 01:31:39.611800 1 backend.go:172] send audit events error, Post “https://kube-auditing-webhook-svc.kubesphere-logging-system.svc:443/audit/webhook/event”: dial tcp: lookup kube-auditing-webhook-svc.kubesphere-logging-system.svc on 172.21.0.10:53: no such host
E1016 01:31:48.613553 1 backend.go:172] send audit events error, Post “https://kube-auditing-webhook-svc.kubesphere-logging-system.svc:443/audit/webhook/event”: dial tcp: lookup kube-auditing-webhook-svc.kubesphere-logging-system.svc on 172.21.0.10:53: no such host
E1016 01:32:00.615192 1 backend.go:172] send audit events error, Post “https://kube-auditing-webhook-svc.kubesphere-logging-system.svc:443/audit/webhook/event”: dial tcp: lookup kube-auditing-webhook-svc.kubesphere-logging-system.svc on 172.21.0.10:53: no such host
E1016 01:32:09.617652 1 backend.go:172] send audit events error, Post “https://kube-auditing-webhook-svc.kubesphere-logging-system.svc:443/audit/webhook/event”: dial tcp: lookup kube-auditing-webhook-svc.kubesphere-logging-system.svc on 172.21.0.10:53: no such host
member
W1016 01:26:05.445163 1 client_config.go:552] Neither –kubeconfig nor –master was specified. Using the inClusterConfig. This might not work.
W1016 01:26:05.446707 1 client_config.go:552] Neither –kubeconfig nor –master was specified. Using the inClusterConfig. This might not work.
W1016 01:26:05.462552 1 options.go:180] ks-apiserver starts without redis provided, it will use in memory cache. This may cause inconsistencies when running ks-apiserver with multiple replicas.
I1016 01:26:05.480173 1 interface.go:60] start helm repo informer
I1016 01:26:05.494075 1 apiserver.go:372] Start cache objects
I1016 01:26:06.361266 1 apiserver.go:576] Finished caching objects
I1016 01:26:06.361286 1 apiserver.go:297] Start listening on :9090
已知直接连接member的dashboard是可以使用的
求大佬给一些排查思路
