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
kubeapi server does not restart after manifest edit #106
Comments
What does |
It seems adding ANY new argument breaks api-server. default api stuff:
if i add any valid arg found in documentation http://kubernetes.io/docs/admin/kube-apiserver/
|
Look at the kubelet logs. |
And look at the kube-apiserver logs as well ( |
@luxas, after edit, it doesnt seem to run the kube-api server (its missing) p.s i added flag |
What about the kubelet logs? |
@mikedanese where is kubelet logs? docker ps and /var/logs doesnt seem to show any location for it. |
You might need to use journalctl. |
@mikedanese with |
journalctl -u kubelet |
I'd love to see that log if possible. |
ah sorry i messed up, after editing the manifest file, here is what i am seeing:
|
|
@luxas @mikedanese it seems its something with the 1.6 changes: note in above video: same AMI (that previously had 1.5 kubeadm) one gets upgraded, the other doesnt |
I have exactly the same problem. I am using kubeadm 1.5.1 |
I'm hitting the same with kubeadm 1.5.1. It looks like this is a duplicate of #25 but that was closed because |
@ravishivt yea seems like the PR from kubernetes/kubernetes#34719 |
Please reopen if this happens with v1.6 as well |
Dear all, does kubelet not support swagger-ui since v1.7? |
@gogeof That's totally unrelated to this issue. |
@luxas Yes, my fault, --enable-swagger-ui is apiserver's API. Thanks a lot. |
@luxas this is still happening for me with kubeadm and Kubernetes 1.10 |
@luxas Same issue with 1.9 |
@luxas I am having the same issue w/ Kubernetes 1.10.1 Never mind, this seems to be more related to 'in place editing of manifests' kubernetes/kubernetes#48219 |
Same here... |
Right, this is not a kubeadm issue |
I am on Kubernetes 1.11 and I have the same issue or worse - I mean any change (even of timestamp) on /etc/kubernetes/manifests/kube-apiserver.yaml causes the api server to dye instantly and never come up again without a kubeadm init. Editing in place - VIM or nano - or editing elsewhere and copy/move over - or just "touch" - same destructive effect. Now is there a way to configure the "defaults" used by kubeadm init when re-creating this file? Thanks |
@debugnetiq1 Can you check |
I have same issue with kubernetes 1.9 created by kops. |
Running Kubernetes 1.11
kubelet log just spams a bunch of these lines:
container
Modified with nano, also tried to copy in from elsewhere - this doesn't matter though... |
further investigation of the failed api container:
|
fixed by removing the |
as per comments in:
kubernetes/kubernetes#34307
you should be able to edit
/etc/kubernetes/manifests/kube-apiserver.json
to add arguments that you need in it. (like args from http://kubernetes.io/docs/admin/kube-apiserver/)in K8s / Kubeadm 1.4 I can do this w/o issue. editing manifest will auto update kube-api server.
but in 1.6, ANY edit to manifest fails to restart api-server
TO VERIFY:
install k8s cluster via kubeadm guide: http://kubernetes.io/docs/getting-started-guides/kubeadm/
install weave: https://www.weave.works/docs/net/latest/kube-addon/
kubectl get nodes
note the correct ouput.netstat -tulpn
note kube-apiserv on 6443vi /etc/kubernetes/manifests/kube-apiserver.json
and then add a valid arg to kube-api server--service-node-port-range=30000-32767
. save and quitkubectl get nodes
will not work anymore.as i said, in kubeadm 1.4 this wasnt an issue, i can edit the manfiest and it works fine with the new manifest information...just not the latest (1.6)
The text was updated successfully, but these errors were encountered: