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

Envoy initializer failed to start #2

Open
gyliu513 opened this issue Aug 22, 2017 · 4 comments
Open

Envoy initializer failed to start #2

gyliu513 opened this issue Aug 22, 2017 · 4 comments

Comments

@gyliu513
Copy link

It was reporting

root@k8s001:~/cases/kubernetes-initializer-tutorial# docker ps -a | grep envo
51613484f624        gcr.io/hightowerlabs/envoy-initializer@sha256:e2e2d5b6b9e888c102aa9c015db1624aa2165407690199b5c8aae650ce4e2b75                "/envoy-initializer"     3 seconds ago       Exited (1) 2 seconds ago                       k8s_envoy-initializer_envoy-initializer-1254595018-5llvp_default_1bc4e488-8705-11e7-8884-08002759511a_2
b624320910ba        gcr.io/google_containers/pause-amd64:3.0                                                                                      "/pause"                 45 seconds ago      Up 44 seconds                                  k8s_POD_envoy-initializer-1254595018-5llvp_default_1bc4e488-8705-11e7-8884-08002759511a_0
root@k8s001:~/cases/kubernetes-initializer-tutorial# docker logs 51613484f624
2017/08/22 06:43:29 Starting the Kubernetes initializer...
2017/08/22 06:43:29 Initializer name set to: envoy.initializer.kubernetes.io
2017/08/22 06:43:29 configmaps "envoy-initializer" is forbidden: User "system:serviceaccount:default:default" cannot get configmaps in the namespace "default".

Can anyone help check what is wrong? Thanks!

@gyliu513
Copy link
Author

I can workaround this via the following

kubectl create clusterrolebinding cluster-admin-1 --clusterrole=cluster-admin --user=system:serviceaccount:default:default

@kelseyhightower
Copy link
Owner

I'll get a proper fix for this.

@kelseyhightower
Copy link
Owner

Can you share your cluster details?

@gyliu513
Copy link
Author

gyliu513 commented Sep 2, 2017

I have only one node with master branch

root@k8s001:~# kubectl version
Client Version: version.Info{Major:"1", Minor:"8+", GitVersion:"v1.8.0-alpha.2.2134+38053c3e4486e6", GitCommit:"38053c3e4486e6a7fafd00b2784a1e67e0357f45", GitTreeState:"clean", BuildDate:"2017-08-18T08:01:14Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"8+", GitVersion:"v1.8.0-alpha.2.2134+38053c3e4486e6", GitCommit:"38053c3e4486e6a7fafd00b2784a1e67e0357f45", GitTreeState:"clean", BuildDate:"2017-08-18T08:01:14Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
root@k8s001:~# kubectl get nodes --show-labels
NAME      STATUS    AGE       VERSION                              LABELS
k8s001    Ready     45d       v1.8.0-alpha.2.2134+38053c3e4486e6   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=k8s001

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

Successfully merging a pull request may close this issue.

2 participants