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

Jump to bottom

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

Closed
neolit123 opened this issue Jul 22, 2020 · 7 comments · Fixed by kubernetes/kubernetes#93483
Closed

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

neolit123 opened this issue Jul 22, 2020 · 7 comments · Fixed by kubernetes/kubernetes#93483
Assignees
@helenfeng737
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/backlog Higher priority than priority/awaiting-more-evidence.
Milestone
v1.20

Comments

@neolit123
Copy link
Member

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
@k8s-ci-robot
Copy link
Contributor

@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 k8s-ci-robot added this to the v1.20 milestone Jul 22, 2020
@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/backlog Higher priority than priority/awaiting-more-evidence. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Jul 22, 2020
@neolit123
Copy link
Member Author

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

@helenfeng737
Copy link

/assign

@helenfeng737
Copy link

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

@helenfeng737 helenfeng737 mentioned this issue Jul 27, 2020
Merged
@helenfeng737 helenfeng737 mentioned this issue Aug 10, 2020
Closed
6 tasks
@pramodsharma62
Copy link

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

@helenfeng737
Copy link

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

@neolit123
Copy link
Member Author

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.

context deadline exceeded

this is a separate problem around kubeadm plan not fetching the etcd versions properly for external etcd clusters.

@ming-ddtechcg ming-ddtechcg mentioned this issue Sep 1, 2020
Closed
@neolit123 neolit123 mentioned this issue Oct 1, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@helenfeng737 helenfeng737

Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
v1.20
Development

Successfully merging a pull request may close this issue.

Remove false positive warning in kubeadm cmd helenfeng737/kubernetes
4 participants
@neolit123 @helenfeng737 @k8s-ci-robot @pramodsharma62