-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Support serviceaccounts #10
Comments
ServiceAccount should be present. |
This is how hyperkube sets up service accounts: They generate tokens using urandom and pass them into the api server via --token-auth-file |
Yes, we're using |
This should be working now with #48. |
Update linker flags and strip binaries to shrink download
Running the `minikube addons enable registry` yields `registry was successfully enabled` but no `registry` Pod ends up being run. I've narrowed it down to this `env` entry not being quoted. Logs from `kube-addon-manager-minikube` Pod show this error: ``` Error from server (BadRequest): error when creating "/etc/kubernetes/addons/registry-rc.yaml": ReplicationController in version "v1" cannot be handled as a ReplicationController: v1.ReplicationController.Spec: v1.ReplicationControllerSpec.Template: v1.PodTemplateSpec.Spec: v1.PodSpec.Containers: []v1.Container: v1.Container.Env: []v1.EnvVar: v1.EnvVar.Value: ReadString: expects " or n, but found t, error found in kubernetes#10 byte of ...|,"value":true}],"ima|..., bigger context ...|"name":"REGISTRY_STORAGE_DELETE_ENABLED","value":true}],"image":"registry.hub.docker.com/library/reg|... ```
Bump gcp-auth-webhook image version to v0.0.4
Without them DNS addon won't work (and lots of other things as well)
It is not an issue if we keep relying on weave in localkube.
The text was updated successfully, but these errors were encountered: