-
-
Notifications
You must be signed in to change notification settings - Fork 264
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 startup config flags deprecated - use config file instead #4
Comments
(Same thing in 1.11... and 1.12 was just released.) |
Another point is that a user cannot pass in their own config file currently - you get the error |
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution! Please read this blog post to see the reasons why I mark issues as stale. |
This issue is no longer marked for closure. |
1 similar comment
This issue is no longer marked for closure. |
As I understand it, we need to create a config-file and set |
also: I think it would help to create the config file from the Are there any plans doing that - or doing it in a completely different way? |
Could we overwrite the line and generate I think this would be the easiest way to parse variables to this file - as we can just parse them as 1:1 with jinja2-templates. If you think this is a good way I could try to create a PR for that. |
That would be a good idea, yes, but likely it will break existing usage of the role, so it would need to be done in a major version bump or have some backwards compatibility added. |
Ok, I started to create a PR like discussed above and started testing on my local machine. What do you think? Edit: Here is the link Or is this just for the cgroup-driver? ... confused ... Edit again: Seems like we need to use that with Links:
|
From Kubelet's startup logs via
journalctl -f
, when running Kubernetes 1.10+:See docs: https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/
The text was updated successfully, but these errors were encountered: