-
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
kubelet: The generated config is not loaded (imagefs.available not applied) #5329
Comments
This issue breaks the configuration that disables the default image pruning on disk space pressure. With Would it be possible to increase priority? Our current workaround is to call minikube with |
Yep, this is definitely an issue. We'll move it up the stack and get to it soon. |
@sharifelgamal is this being worked on ?, if not then would be interested to take this but will need bit more context on how to reproduce the issue. |
@nanikjava caafc66 explicitly added configuration in kubeadm to disable kubelet disk eviction (which is the feature we need). The error is there: kubelet should be configured to read that config. See the documentation I linked in my previous comment. |
Will test this out. Thanks @thomas-riccardi |
/assign @nanikjava |
Tried running minikube using VirtualBox and run it with the following command
Can see inside the VM kubelet ran with the following command
...and tried running with the following command
can see the config.yaml is attached to the command line
is this the problem where the config.yaml is not 'attach' as part of the command line to run kubelet ? |
@nanikjava yes, the |
thanks @thomas-riccardi will put a fix for this. |
…es#5329 Kubelet startup parameters does not include the --config flag. This flag pass the location of the configuration file. During minikube startup process this file is copied over to the VM
…es#5329 Kubelet startup parameters does not include the --config flag. This flag pass the location of the configuration file. During minikube startup process this file is copied over to the VM. Fix test cases.
@tstromberg @sharifelgamal PR submitted #5697 |
…es#5329 Kubelet startup parameters does not include the --config flag. This flag pass the location of the configuration file. During minikube startup process this file is copied over to the VM. Fix test cases.
@tstromberg can we close this issue ?. Thanks |
/close
…On Thu, Nov 7, 2019, 1:12 PM Nanik ***@***.***> wrote:
@tstromberg <https://github.com/tstromberg> can we close this issue ?.
Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5329?email_source=notifications&email_token=AAAYYMC3VUQAK2JIVKB5ODTQSSAC7A5CNFSM4IWEG7Y2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDN2PQA#issuecomment-551266240>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAYYMHNJBKUWUE4WEFB2VTQSSAC7ANCNFSM4IWEG7YQ>
.
|
@tstromberg: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Minikube generates a kubelet config file in
/var/lib/kubelet/config.yaml
with eviction thresholds at 0%.However it doesn't seem to be loaded by kubelet.
The exact command to reproduce the issue:
Those are the default thresholds.
The operating system version: Ubuntu 18.04 / Minikube 1.3.1
The text was updated successfully, but these errors were encountered: