Skip to content
New issue

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

kubeasz 3.1.1 版本问题反馈 #1084

Closed
piano-wow opened this issue Oct 28, 2021 · 8 comments
Closed

kubeasz 3.1.1 版本问题反馈 #1084

piano-wow opened this issue Oct 28, 2021 · 8 comments
Labels

Comments

@piano-wow
Copy link
Contributor

kubectl get componentstatuses
报错:
controller-manager Unhealthy Get "https://127.0.0.1:10257/healthz": dial tcp 127.0.0.1:10257: connect: connection refused

截图:
image

@muziriyueliming
Copy link

[root@k8s-aio ~]# kubectl get cs
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME STATUS MESSAGE ERROR
scheduler Healthy ok
controller-manager Healthy ok
etcd-0 Healthy {"health":"true","reason":""}

image

/etc/systemd/system/kube-controller-manager.service
[Unit]
Description=Kubernetes Controller Manager
Documentation=https://github.com/GoogleCloudPlatform/kubernetes

[Service]
ExecStart=/opt/kube/bin/kube-controller-manager
--bind-address=127.0.0.1 \ 替换ip这个就好了
--allocate-node-cidrs=true
--cluster-cidr=172.20.0.0/16
--cluster-name=kubernetes
--cluster-signing-cert-file=/etc/kubernetes/ssl/ca.pem
--cluster-signing-key-file=/etc/kubernetes/ssl/ca-key.pem
--kubeconfig=/etc/kubernetes/kube-controller-manager.kubeconfig
--leader-elect=true
--node-cidr-mask-size=24
--root-ca-file=/etc/kubernetes/ssl/ca.pem
--service-account-private-key-file=/etc/kubernetes/ssl/ca-key.pem
--service-cluster-ip-range=10.68.0.0/16
--use-service-account-credentials=true
--v=2
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target

@muziriyueliming
Copy link

muziriyueliming commented Nov 3, 2021

image

journalctl -xefu kubelet
image

https://www.cnblogs.com/lajiao/p/15044705.html 看这个就好了.

@github-actions
Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Nov 12, 2022
@piano-wow
Copy link
Contributor Author

piano-wow commented Nov 12, 2022 via email

@github-actions github-actions bot removed the stale label Nov 13, 2022
@github-actions
Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Dec 14, 2022
@piano-wow
Copy link
Contributor Author

piano-wow commented Dec 14, 2022 via email

@github-actions github-actions bot removed the stale label Dec 15, 2022
@github-actions
Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Jan 15, 2023
@github-actions
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants