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

Support extra volumes for Kubeadm #2767

Closed
vinceho opened this issue Apr 26, 2018 · 7 comments
Closed

Support extra volumes for Kubeadm #2767

vinceho opened this issue Apr 26, 2018 · 7 comments
Labels
co/kubeadm Issues relating to kubeadm kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@vinceho
Copy link

vinceho commented Apr 26, 2018

This is a feature request.

Support for configuring these fields in the kubeadm.yaml configuration file (implemented by kubernetes/kubeadm#441).

APIServerExtraVolumes
ControllerManagerExtraVolumes
SchedulerExtraVolumes

This will help support extra options like --extra-config=apiserver.token-auth-file. Currently, this does not work because the kube-apiserver docker container could not find the file. The path of the token file must be mounted first.

Environment:

  • Minikube version: v0.26.1
  • OS: Ubuntu 16.04
  • VM Driver: virtualbox
  • ISO version: v0.26.0
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 25, 2018
@vinceho
Copy link
Author

vinceho commented Aug 2, 2018

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 2, 2018
@tstromberg tstromberg added kind/feature Categorizes issue or PR as related to a new feature. co/kubeadm Issues relating to kubeadm labels Sep 19, 2018
@oz123
Copy link

oz123 commented Nov 9, 2018

This is already implemented in kubernetes/kubernetes#49840

@tstromberg
Copy link
Contributor

Is this issue obsolete then?

@tstromberg tstromberg added the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label Jan 24, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 29, 2019
@tstromberg
Copy link
Contributor

Closing this bug as it hasn't seen activity in awhile, and there does not appear to be any plans to address it. Please re-open if interested.

@mecampbellsoup
Copy link

This is already implemented in kubernetes/kubernetes#49840

Hi guys - @tstromberg @vinceho @oz123 can you please elaborate on how this could be used with minikube? Is it possible to pass it as an additional option to minikube start e.g.?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/kubeadm Issues relating to kubeadm kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Development

No branches or pull requests

6 participants