• 安装部署

  • ks-apiserver启动异常，notification-manager-webhook 链接超时

创建部署问题时，请参考下面模板，你提供的信息越多，越容易及时获得解答。如果未按模板创建问题，管理员有权关闭问题。
确保帖子格式清晰易读，用 markdown code block 语法格式化代码块。
你只花一分钟创建的问题，不能指望别人花上半个小时给你解答。

操作系统信息
例如：虚拟机/物理机，Centos7.5/Ubuntu18.04，4C/8G

Kubernetes版本信息
将 kubectl version 命令执行结果贴在下方

容器运行时
将 docker version / crictl version / nerdctl version 结果贴在下方

KubeSphere版本信息
例如：v3.3.1。离线安装。使用kk安装。

问题：

集群崩溃重启后，ks-apiserver一直不断重启。查看日志后发现报错信息，Kind=Receiver failed: Post “https://notification-manager-webhook.kubesphere-monitoring-system.svc:443/convert?timeout=30s”: dial tcp 10.88.53.135:443: i/o timeout (Client.Timeout exceeded while awaiting headers)

检查notification-manager-opeartor，发现容器状态正常，svc endpoint也显示该容器的ip。但无法调通。

ks-apiserver无法启动导致kubesphere后台不可用

截图如下

ks-apiserver完整日志
W1113 15:33:27.048557       1 client_config.go:615] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
W1113 15:33:27.050432       1 client_config.go:615] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
W1113 15:33:27.060113       1 options.go:191] ks-apiserver starts without redis provided, it will use in memory cache. This may cause inconsistencies when running ks-apiserver with multiple replicas.
I1113 15:33:27.060246       1 interface.go:50] start helm repo informer
I1113 15:33:27.743931       1 apiserver.go:417] Start cache objects
I1113 15:34:00.271374       1 trace.go:201] Trace[289567734]: "Reflector ListAndWatch" name:pkg/client/informers/externalversions/factory.go:128 (13-Nov-2024 15:33:00.261) (total time: 30010ms):
Trace[289567734]: [30.010064535s] [30.010064535s] END
E1113 15:34:00.271406       1 reflector.go:138] pkg/client/informers/externalversions/factory.go:128: Failed to watch *v2beta1.Receiver: failed to list *v2beta1.Receiver: conversion webhook for notification.kubesphere.io/v2beta2, Kind=Receiver failed: Post "https://notification-manager-webhook.kubesphere-monitoring-system.svc:443/convert?timeout=30s": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
I1113 15:34:00.273251       1 trace.go:201] Trace[1456384835]: "Reflector ListAndWatch" name:pkg/client/informers/externalversions/factory.go:128 (13-Nov-2024 15:33:00.260) (total time: 30012ms):
Trace[1456384835]: [30.012536074s] [30.012536074s] END
E1113 15:34:00.273306       1 reflector.go:138] pkg/client/informers/externalversions/factory.go:128: Failed to watch *v2beta1.Config: failed to list *v2beta1.Config: conversion webhook for notification.kubesphere.io/v2beta2, Kind=Config failed: Post "https://notification-manager-webhook.kubesphere-monitoring-system.svc:443/convert?timeout=30s": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
I1113 15:34:31.323124       1 trace.go:201] Trace[517013151]: "Reflector ListAndWatch" name:pkg/client/informers/externalversions/factory.go:128 (13-Nov-2024 15:34:00.317) (total time: 30005ms):
Trace[517013151]: [30.005633505s] [30.005633505s] END
E1113 15:34:31.323184       1 reflector.go:138] pkg/client/informers/externalversions/factory.go:128: Failed to watch *v2beta1.Receiver: failed to list *v2beta1.Receiver: conversion webhook for notification.kubesphere.io/v2beta2, Kind=Receiver failed: Post "https://notification-manager-webhook.kubesphere-monitoring-system.svc:443/convert?timeout=30s": dial tcp 10.88.53.135:443: i/o timeout
I1113 15:34:31.799738       1 trace.go:201] Trace[1642798913]: "Reflector ListAndWatch" name:pkg/client/informers/externalversions/factory.go:128 (13-Nov-2024 15:34:00.794) (total time: 30005ms):
Trace[1642798913]: [30.005122226s] [30.005122226s] END
E1113 15:34:31.799788       1 reflector.go:138] pkg/client/informers/externalversions/factory.go:128: Failed to watch *v2beta1.Config: failed to list *v2beta1.Config: conversion webhook for notification.kubesphere.io/v2beta2, Kind=Config failed: Post "https://notification-manager-webhook.kubesphere-monitoring-system.svc:443/convert?timeout=30s": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

notification-manager-operator日志如下截图，没看到error，只有info和debug

ks-apiserver日志Post "https://notification-manager-webhook.kubesphere-monitoring-system.svc:443/convert?timeout=30s": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) 显示它到这个服务连接超时了。可以在console的kubectl终端上验证下到notification-manager-webhook.kubesphere-monitoring-system.svc:443

是否能够连通。如果是，再验证下 ks-apiserver到它是否能够连通

1 个月 后

遇到了同样的问题，怎么解决的？