-
Notifications
You must be signed in to change notification settings - Fork 80
add k3s cluster setup doc #427
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
Merged
Conversation
This file contains hidden or 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
bpmct
commented
Jun 22, 2021
jawnsy
reviewed
Jun 22, 2021
✨ Coder.com for PR #427 deployed! It will be updated on every commit.
|
khorne3
reviewed
Jun 23, 2021
khorne3
reviewed
Jun 23, 2021
khorne3
approved these changes
Jun 25, 2021
jawnsy
reviewed
Jun 26, 2021
jawnsy
reviewed
Jun 26, 2021
Co-authored-by: Jonathan Yu <jonathan@coder.com>
bpmct
commented
Jun 28, 2021
setup/kubernetes/k3s.md
Outdated
Comment on lines
47
to
49
If you enable Networking v2 after installing Coder (in | ||
`Manage > Admin > Infrastructure`), this step is not necessary to SSH into | ||
workspaces, as TURNS is used instead. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@deansheather added a note :)
I noticed that networking v2 is not mentioned anywhere else in docs so I specifically referenced how this can be done.
deansheather
approved these changes
Jul 2, 2021
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.
This PR documents the steps necessary to install a K3s cluster on an Ubuntu machine as an alternative to Local Preview (functioning SSH, dev URLs, works for prod use) or a managed Kubernetes solution.
Open questions:
This doc is currently Ubuntu-specific, but for no particular reason other than "it works." Should I test on some other operating systems or better describe requirements? The goal by mentioning the OS is that this works best on a new machine.Can this have a better title to explain it's a good "single-host" solution versus managed KubernetesAre there any anti-patterns / inaccuracies?Others in PR comments :)
References: