[Fix] more resilient post-create cluster preparation (DNS) #780
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
iwilltry42
force-pushed
the
feature/coredns-retry
branch
from
3558b19 to
4df00f6
Compare
iwilltry42
force-pushed
the
feature/coredns-retry
branch
from
002a5af to
7805f32
Compare
|
@iwilltry42 FYI I was not able to start a cluster on my Mac with 5.0.1 (tried 5 times), but after setting |
|
@marckhouzam , v5.1.0 uses a different method to modify CoreDNS... does that work for you? |
|
@iwilltry42 with v5.1.0 I was able to create 5 clusters in a row without issue 🎉 |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
K3D_DEBUG_COREDNS_RETRIES=3to specify number of tries to the CoreDNS patch process