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

Minikube with custom profile does not create default service accounts #3299

Closed
gintautassulskus opened this issue Nov 5, 2018 · 1 comment
Labels
area/profiles issues related to profile handling kind/bug Categorizes issue or PR as related to a bug. triage/obsolete Bugs that no longer occur in the latest stable release

Comments

@gintautassulskus
Copy link

BUG REPORT

Environment:

Minikube version (use minikube version):

  • OS: macOS 10.14.1
  • VM Driver : virtualbox
  • ISO version: v0.30.0

What happened:
A minikube instance, started with a custom profile, is missing default service accounts. Minikube with the default profile works just fine.

What you expected to happen:
The minikube instance with the custom profile should work just like the minikube instance with the default profile.

How to reproduce it (as minimally and precisely as possible):

minikube start --profile custom.minikube --memory 3584 --cpus 4 --dns-domain cluster.local --kubernetes-version v1.11.2
(v1.10.0 should not differ)

Output of kubectl get sa --all-namespaces --context custom.minikube:

NAMESPACE     NAME         SECRETS   AGE
kube-system   coredns      0         3m
kube-system   kube-proxy   0         3m

Output of apiserver logs (if applicable): https://pastebin.com/KBTsqenF

Output of controller-manager logs (if applicable): https://pastebin.com/FwR6Kdn0

Output of minikube logs (if applicable): https://pastebin.com/Tu46KAXU

In order to improve readability, I moved logs to pastebin. If any of the logs appear to be relevant, I will edit the post and embed them here directly.

@balopat balopat added kind/bug Categorizes issue or PR as related to a bug. area/profiles issues related to profile handling labels Nov 6, 2018
@tstromberg
Copy link
Contributor

We appear to have fixed this bug in v0.33, at least with it's default of Kubernetes v1.13.2. Tested with kvm2/linux and virtualbox/mac:

$ kubectl get sa --all-namespaces --context=custom-no-sa
NAMESPACE     NAME                                 SECRETS   AGE
default       default                              1         4m
kube-public   default                              1         4m
kube-system   attachdetach-controller              1         4m
kube-system   bootstrap-signer                     1         4m
kube-system   certificate-controller               1         4m
kube-system   clusterrole-aggregation-controller   1         4m
kube-system   coredns                              1         4m
kube-system   cronjob-controller                   1         4m
kube-system   daemon-set-controller                1         4m
kube-system   default                              1         4m
kube-system   deployment-controller                1         4m
kube-system   disruption-controller                1         4m
kube-system   endpoint-controller                  1         4m
kube-system   expand-controller                    1         4m
kube-system   generic-garbage-collector            1         4m
kube-system   horizontal-pod-autoscaler            1         4m
kube-system   job-controller                       1         4m
kube-system   kube-proxy                           1         4m
kube-system   namespace-controller                 1         4m
kube-system   node-controller                      1         4m
kube-system   persistent-volume-binder             1         4m
kube-system   pod-garbage-collector                1         4m
kube-system   pv-protection-controller             1         4m
kube-system   pvc-protection-controller            1         4m
kube-system   replicaset-controller                1         4m
kube-system   replication-controller               1         4m
kube-system   resourcequota-controller             1         4m
kube-system   service-account-controller           1         4m
kube-system   service-controller                   1         4m
kube-system   statefulset-controller               1         4m
kube-system   storage-provisioner                  1         4m
kube-system   token-cleaner                        1         4m
kube-system   ttl-controller                       1         4m

@tstromberg tstromberg added the triage/obsolete Bugs that no longer occur in the latest stable release label Jan 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/profiles issues related to profile handling kind/bug Categorizes issue or PR as related to a bug. triage/obsolete Bugs that no longer occur in the latest stable release
Projects
None yet
Development

No branches or pull requests

3 participants