-
Notifications
You must be signed in to change notification settings - Fork 431
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
kubedns not starting when using custom clusterDomain #2315
Labels
Comments
more info from vcluster logs:
the vcluster works normally if i remove networking. advanced. clusterDomain |
hi @pasztorl i am working on this and will try to raise a PR soon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
created vcluster with customized networking.advanced.clusterDomain then coredns failing to start
if i remove the clusterdomain settings vcluster seems to work normally
What did you expect to happen?
vcluster and coredns start normally
How can we reproduce it (as minimally and precisely as possible)?
vcluster create --values vcluster.values.yaml --connect=false my-cluster
Anything else we need to know?
coredns log output:
Host cluster Kubernetes version
vcluster version
VCluster Config
The text was updated successfully, but these errors were encountered: