-
Notifications
You must be signed in to change notification settings - Fork 48
feat: Added an update to CoreDNS #530
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
Conversation
… create-pathways is used, it will default to CoreDNS.
…cessary' function.
…tions, along with some helper functions.
This PR is from #501 due to fork issue |
@pawloch00 Please review it again. |
@sharabiani ptal |
@wstcliyu @pawloch00 It also seems to be caused by an IP connection refused error. |
The test that failed wasn't any of paths mentioned in PR description |
Right, the problem only appeared after I update the branch. |
Please add github workflow test that will clearly test this path and check for presence of coreDNS deployment. Also, if possible add checks to existing tests, that existing DNS deployment was not changed. |
Fixes / Features
Enhance DNS Scalability for Large-Scale Testing:
Testing / Documentation
When using the command
python3 xpk.py cluster create-pathways and python3 xpk.py cluster create
to create a cluster, CoreDNS will be used by default.