Updated README to point to latest k3d release, added tips to doc section #24
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
|
+1 Already started tracking what is the reason for a flag name change, when I found this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
I went through the demo today and ran into an issue with k3d. The installation instructions for k3d point to an old release, v3.2.0. I installed that version and ran into trouble during cluster creation as one of the k3d command line flags had changed. Initially I thought it was a typo in the
create-k3d-clusterscript and made a change there, only to run into a more errors from k3d. After installing the latest version, v5.2.2, thecreate-k3d-clusterscript worked without any changes and I could continue with the demo by following the README.This makes 2 changes to the demo documentation:
k3dand setting execute permissions. This is similar to what is stated in thejsonnet-bundlersection.