We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As of 1.11, coredns is the kubeadm default. But unlike kubedns, coredns has neither pod priority nor the experimental "critical pod" annotation.
The annotation is deprecated in 1.13, and kubeadm may define pod priority for coredns in 1.14.
The text was updated successfully, but these errors were encountered:
@ojmhetar @sarun87 Your thoughts?
Sorry, something went wrong.
It seems that kube-dns never had the critical pod annotation, so the behavior would be consistent as 1.10? ¯\_(ツ)_/¯
An option could be to apply a patch.
I submitted kubernetes/kubernetes#73649 for the future.
Thanks for fixing upstream.
I think it's worth patching. Just to note, I'd prefer patching from cctl, rather than nodeadm.
No branches or pull requests
As of 1.11, coredns is the kubeadm default. But unlike kubedns, coredns has neither pod priority nor the experimental "critical pod" annotation.
The annotation is deprecated in 1.13, and kubeadm may define pod priority for coredns in 1.14.
The text was updated successfully, but these errors were encountered: