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

use KubeleteConfiguration instead of flags #156

Closed
errordeveloper opened this issue Aug 9, 2018 · 4 comments
Closed

use KubeleteConfiguration instead of flags #156

errordeveloper opened this issue Aug 9, 2018 · 4 comments
Labels
area/nodegroup kind/feature New feature or request

Comments

@errordeveloper
Copy link
Contributor

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).

@errordeveloper
Copy link
Contributor Author

errordeveloper commented Dec 18, 2018

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.

@errordeveloper
Copy link
Contributor Author

Turns out not all the flags were defined in the config yet, we will migrate what we can.

@errordeveloper
Copy link
Contributor Author

@errordeveloper errordeveloper changed the title use of componentconfig or kubelet config file use KubeleteConfiguration instead of flags Mar 19, 2019
@errordeveloper
Copy link
Contributor Author

errordeveloper commented May 13, 2019

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/nodegroup kind/feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant