-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 KubeleteConfiguration
instead of flags
#156
Labels
Comments
errordeveloper
added a commit
that referenced
this issue
Aug 9, 2018
errordeveloper
added a commit
that referenced
this issue
Aug 10, 2018
errordeveloper
added a commit
that referenced
this issue
Aug 10, 2018
errordeveloper
added a commit
that referenced
this issue
Sep 4, 2018
errordeveloper
added a commit
that referenced
this issue
Sep 4, 2018
errordeveloper
added a commit
that referenced
this issue
Sep 4, 2018
2 tasks
We switched to kubelet config in #353, but it's still just a static asset, we should generate it and get rid of all the flags. |
Turns out not all the flags were defined in the config yet, we will migrate what we can. |
errordeveloper
changed the title
use of componentconfig or kubelet config file
use Mar 19, 2019
KubeleteConfiguration
instead of flags
4 tasks
Moving remaining flags would requite some upstream changes, which are far-fetched at this point. |
torredil
pushed a commit
to torredil/eksctl
that referenced
this issue
May 20, 2022
Fix integration Test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We would benefit from not having to worry about kubelet flags. At least a config file would be helpful, but componentconfig would be even better (need to check status).
The text was updated successfully, but these errors were encountered: