Kubeadm: remove "WARNING: kubeadm cannot validate component configs for API groups"

Created on 22 Jul 2020 · 7Comments · Source: kubernetes/kubeadm

there were a number of cases in the #kubeadm slack channel where users are asking why they are getting this warning for commands that do not accept --config - e.g. kubeadm token ...

ideally the warning should be printed only if the user has provided a --config, but i'm pretty sure this logic is difficult to untangle, so we should instead just remove this warning or hide it behind a higher verbosity (e.g. klog.V(1).Infof(....)).

cc @rosti
/help
/kind cleanup
/priority backlog
/milestone v1.20

help wanted kincleanup prioritbacklog

Source

neolit123

All 7 comments

@neolit123:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

there were a number of cases in the #kubeadm slack channel where users are asking why they are getting this warning for commands that do not accept --config - e.g. kubeadm token ...

ideally the warning should be printed only if the user has provided a --config, but i'm pretty sure this logic is difficult to untangle, so we should instead just remove this warning or hide it behind a higher verbosity (e.g. klog.V(1).Infof(....)).

cc @rosti
/help
/kind cleanup
/priority backlog
/milestone v1.20

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.

k8s-ci-robot on 22 Jul 2020

the warning line is located here:
https://github.com/kubernetes/kubernetes/blob/af29f81af6f5afc0ad48cd2d3d5472a9ca4d4cc8/cmd/kubeadm/app/componentconfigs/configset.go#L348

neolit123 on 22 Jul 2020

/assign

ZhiFeng1993 on 22 Jul 2020

Just for records, several slack discussions are:
https://kubernetes.slack.com/archives/C2P1JHS2E/p1578407862006800
https://kubernetes.slack.com/archives/C2P1JHS2E/p1595445960138200

ZhiFeng1993 on 27 Jul 2020

Is there any fix for this yet? I am having the same issues.

pramodsharma62 on 12 Aug 2020

Is there any fix for this yet? I am having the same issues.

We've made the fix in v1.19. In the meantime, you can find the troubleshooting item here: https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm/#kubeadm-upgrade-plan-prints-out-context-deadline-exceeded-error-message

ZhiFeng1993 on 12 Aug 2020

👍1

Is there any fix for this yet? I am having the same issues.

the warning itself is not an issue, it's just warning that kubeadm no longer validates the KubeletConfiguration, KubeProxyConfiguration that it feeds to the kubelet, kube-proxy components.