Change main.jsonnet to support current k8 #29
Closed
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
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.
Disclaimer: this is my first time doing anything with kubernetes and there are probably implications here I'm not aware of but I got this working and wanted to show someone.
When going through the readme for this, I didn't install the specified releases and instead just ran the brew command. I think specifically this was an issue for
k3d. It will surprise no one that not following the directions means the install didn't run successfully. Comparing notes on thek8s-libsonnetdocumentation got me to the following edits which do run successfully.If k8s/k3d has breaking changes often then I can see why the readme recommends specific versions to go along with this config. Feel free to close!