-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Use dedicated service account for machine controller pod #92
Labels
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
Comments
rsdcastro
added
apiserver
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
labels
Apr 17, 2018
This is very important, but it seems that it can be added as alpha without major changes to the system, so moving it to beta. |
This issue was moved to kubernetes-sigs/cluster-api-provider-gcp#16 |
chuckha
pushed a commit
to chuckha/cluster-api
that referenced
this issue
Oct 2, 2019
chuckha
pushed a commit
to chuckha/cluster-api
that referenced
this issue
Oct 2, 2019
…it-locker Restore control plane init locker
jayunit100
pushed a commit
to jayunit100/cluster-api
that referenced
this issue
Jan 31, 2020
This adds the options related to glog on the command line like `--v=4` Resolves kubernetes-sigs#91 Change-Id: I0b4756b63d4581e1560e15568b03f380eea1d9bb
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
From @medinatiger on February 5, 2018 20:0
The current code is using default service account combined an admin privileged kubeconfig. We need to strip down to appropriate access permission with a dedicated service account.
Copied from original issue: kubernetes-retired/kube-deploy#567
The text was updated successfully, but these errors were encountered: