docs: Update development setup with preferred kind-based approach #25535
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
christarazi
added
kind/enhancement
maintainer-s-little-helper
bot
added
dont-merge/needs-release-note-label
christarazi
added
area/documentation
This comment was marked as outdated.
This comment was marked as outdated.
aojea
reviewed
May 18, 2023
bimmlerd
approved these changes
May 19, 2023
qmonnet
reviewed
May 19, 2023
christarazi
force-pushed
the
pr/christarazi/better-dev-setup-docs
branch
from
9195288
to
9996d77
Compare
|
@qmonnet Done! |
|
@christarazi 👋🏻
Feel free to re-assign me for review when you're ready! |
|
Oops @zacharysarah, I've hidden that comment now because it's no longer up-to-date. It's ready for review. 🙂 |
|
LGTM But I'm clearly biased ;) |
zacharysarah
previously requested changes
May 26, 2023
christarazi
force-pushed
the
pr/christarazi/better-dev-setup-docs
branch
from
9996d77
to
298524e
Compare
|
Thanks @zacharysarah! Comments addressed. |
For a long time, we discussed how unreliable / clunky it is to use the Vagrant-based development setup. It is a massive struggle for new contributors as well. Many developers hacked their own scripts to make it work, and even more avoid using it altogether. Many in the community including myself use kind already. It is simply much easier to set up and maintain, without being a drain on your local machine in terms of resources. Let's finally document what many in the community have already been running. Signed-off-by: Chris Tarazi <chris@isovalent.com>
christarazi
force-pushed
the
pr/christarazi/better-dev-setup-docs
branch
from
298524e
to
e6cd37e
Compare
joestringer
approved these changes
Jun 12, 2023
christarazi
added
the
ready-to-merge
|
Addresses review comments and have other approving reviews already, marking ready to merge. |
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.
For a long time, we discussed how unreliable / clunky it is to use the
Vagrant-based development setup. It is a massive struggle for new
contributors as well.
Many developers hacked their own scripts to make it work, and even more
avoid using it altogether. Many in the community including myself use
kind already. It is simply much easier to set up and maintain, without
being a drain on your local machine in terms of resources.
Let's finally document what many in the community have already been
running.
Signed-off-by: Chris Tarazi chris@isovalent.com