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
Need to expose Kubelet --config flag in KubeletConfigSpec #5070
Comments
I'm not seeing it exposed in https://github.com/kubernetes/kops/blob/master/pkg/apis/kops/componentconfig.go so it'll have to be added. It's super easy to expose, see: https://github.com/kubernetes/kops/blob/master/docs/development/api_updates.md Add the struct value, generate api machinery and you'll be good to |
Yeah, not only that. KubeletConfiguration needs to be exposed, file needs to be generated. Put on disk, point --config on it and more importantly all old flags from KubeletConfigSpec have to be transformed and only on > 1.10 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle rotten I am currently hitting this. This is what I see when I
But then in the logs you see the same messages shown above, one of those being:
Did anybody get anywhere on this or should I take a look? |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle rotten Any updates? |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: 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. |
/remove-lifecycle rotten I think this is still a desirable feature. |
/reopen |
@mars64: You can't reopen an issue/PR unless you authored it or you are a collaborator. 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. |
/reopen |
@tvi: Reopened 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. |
Agreed, given that kubelet is deprecating the old style of providing its configuration I definitely think we should migrate to defining the config file automatically. /lifecycle frozen |
We are running 1.10.1 cluster and our logs contain following log line
The problem is that we cannot specify --config file and KubeletConfiguration spec.
The text was updated successfully, but these errors were encountered: