We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aug 23 23:00:50 k8s-master-ns-t2 kube-scheduler[93576]: I0823 23:00:50.139248 93576 leaderelection.go:248] attempting to acquire leader lease kube-system/kube-scheduler... Aug 23 23:01:08 k8s-master-ns-t2 kube-scheduler[93576]: I0823 23:01:08.614476 93576 leaderelection.go:258] successfully acquired lease kube-system/kube-scheduler Aug 23 23:01:13 k8s-master-ns-t2 kube-scheduler[93576]: E0823 23:01:13.615229 93576 leaderelection.go:330] error retrieving resource lock kube-system/kube-scheduler: Get "https://127.0.0.1:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
证书平滑更新
调度更新地很慢,然后kube-scheduler.service反复重启
No response
# On Linux: $ cat /etc/os-release # paste output here $ uname -a # paste output here ```centos7.9 </details> ### Related plugins (CNI, CSI, ...) and versions (if applicable) 其他网络插件等需要说明的情况 <details> flannel </details>
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open for 30 days with no activity.
Sorry, something went wrong.
This issue was closed because it has been inactive for 14 days since being marked as stale.
No branches or pull requests
What happened? 发生了什么问题?
Aug 23 23:00:50 k8s-master-ns-t2 kube-scheduler[93576]: I0823 23:00:50.139248 93576 leaderelection.go:248] attempting to acquire leader lease kube-system/kube-scheduler...
Aug 23 23:01:08 k8s-master-ns-t2 kube-scheduler[93576]: I0823 23:01:08.614476 93576 leaderelection.go:258] successfully acquired lease kube-system/kube-scheduler
Aug 23 23:01:13 k8s-master-ns-t2 kube-scheduler[93576]: E0823 23:01:13.615229 93576 leaderelection.go:330] error retrieving resource lock kube-system/kube-scheduler: Get "https://127.0.0.1:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
What did you expect to happen? 期望的结果是什么?
证书平滑更新
How can we reproduce it (as minimally and precisely as possible)? 尽可能最小化、精确地描述如何复现问题
调度更新地很慢,然后kube-scheduler.service反复重启
Anything else we need to know? 其他需要说明的情况
No response
Kubernetes version k8s 版本
Kubeasz version
OS version 操作系统版本
The text was updated successfully, but these errors were encountered: