-
Notifications
You must be signed in to change notification settings - Fork 596
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
Supporting extra config files for k8s components #7911
Comments
I think we should avoid |
|
I don't like the fact that we leave some files in We don't need these files to persist reboots, we don't even need |
that makes sense 👍 |
Support configuring kubelet credential provider config. Partially fixes: siderolabs#7911 Signed-off-by: Noel Georgi <git@frezbo.dev>
Support configuring kubelet credential provider config. Partially fixes: siderolabs#7911 Signed-off-by: Noel Georgi <git@frezbo.dev>
Support configuring kubelet credential provider config. Partially fixes: siderolabs#7911 Signed-off-by: Noel Georgi <git@frezbo.dev>
Support configuring kubelet credential provider config. Partially fixes: siderolabs#7911 Signed-off-by: Noel Georgi <git@frezbo.dev>
Support configuring kubelet credential provider config. Partially fixes: siderolabs#7911 Signed-off-by: Noel Georgi <git@frezbo.dev>
Support configuring kubelet credential provider config. Partially fixes: siderolabs#7911 Signed-off-by: Noel Georgi <git@frezbo.dev>
Support kube-scheduler config. Fixes: siderolabs#7905 Partially fixes: siderolabs#7911 Signed-off-by: Noel Georgi <git@frezbo.dev>
Support kube-scheduler config. Fixes: siderolabs#7905 Partially fixes: siderolabs#7911 Signed-off-by: Noel Georgi <git@frezbo.dev>
Support kube-scheduler config. Fixes: siderolabs#7905 Partially fixes: siderolabs#7911 Signed-off-by: Noel Georgi <git@frezbo.dev>
Support kube-scheduler config. Fixes: siderolabs#7905 Partially fixes: siderolabs#7911 Signed-off-by: Noel Georgi <git@frezbo.dev>
Feature Request
Kubelet, API server, Kube scheduler etc require extra config files to be passed in as arguments for advanced tweaking. Currently Talos lacks an easy way to configure them. See:
Proposal
Support something in the order of
extraConfigFiles
for the components. Eg:The
value
can be any valid yaml and Talos will not validate the schema.Talos can write down these files to
/etc/kubernetes/<component-name>.d/
directory and fully managed by the configuration in the machine config.These folders would be mounted by default by Talos to the corresponding components. The user would still have to pass in
extraArgs/extraConfig
to use these files.The text was updated successfully, but these errors were encountered: