-
Notifications
You must be signed in to change notification settings - Fork 69
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
Get coredns working with kubeadm #169
Labels
Comments
@Hong-Chang I'm able to deploy coredns from root environment after the above commit. However @sonyafenge seems to be hitting issues. I'll keep this issue open - can you please investigate this? Thanks |
Assigning to Hong-Chang for further investigation if this is something specific to Sonya's setup. I've had no issues deploying from root account.
|
CoderKevinZhang
pushed a commit
to CoderKevinZhang/arktos
that referenced
this issue
Jan 25, 2021
Co-authored-by: Cathy Zhang <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened:
Vinay suspect it is broken by some change we made to networking that makes node join depend on CNI - not the case with upstream, but I'm guessing at this point). The same code starts with upstream 1.15 starts coreDNS just fine.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
cluster failed to initialize per coredns keeping restarting
Anything else we need to know?:
https://github.com/futurewei-cloud/arktos/pull/127
Environment:
kubectl version
):cat /etc/os-release
):uname -a
):The text was updated successfully, but these errors were encountered: