Update Vagrantfile for (hacky) air-gapped local environment #1
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
added 7 commits
August 28, 2020 08:34
Instead of only deleting the default route, also add a default route pointing to the private network adapter of the VM. Configuration was validated by a successful manual air-gap install of k3s.
This was referenced Feb 27, 2024
This was referenced Feb 5, 2025
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.
Clarified perquisites in Vagrantfile, modified default gateway, and validated configuration with a manual install of k3s. Added local copies of all artifacts required for k3s v1.18.8+k3s1 installation into the vagrant VM, and added vagrant-specific prep and install scripts.