-
Notifications
You must be signed in to change notification settings - Fork 47
Add comprehensive macOS installation and development guide to Quick Start documentation #217
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for kmesh-net ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
Summary of Changes
Hello @AkarshSahlot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
The pull request introduces a comprehensive guide for installing and developing Kmesh on macOS, specifically addressing the need for a Linux environment due to Kmesh's reliance on eBPF and Linux kernel features. This new documentation covers both Intel and Apple Silicon Macs, providing detailed steps for setting up development environments using virtualization or Docker.
Highlights
- macOS Development Guide: I've added a new, extensive guide to the quick-start.md documentation, detailing how to set up a Kmesh development environment on macOS for both Intel and Apple Silicon users.
- Virtualization and Containerization: The guide outlines two primary methods for macOS development: using UTM for virtual machines (recommended for Apple Silicon) or Docker Desktop for a containerized environment, acknowledging macOS's lack of native eBPF support.
- Detailed Setup Instructions: The new documentation includes step-by-step instructions for installing prerequisites, configuring virtual machines or Docker, installing necessary development tools like Go and build dependencies, and building Kmesh.
- Testing and Kubernetes Integration: It also provides guidance on running various tests (unit, BPF unit, integration) and setting up local Kubernetes clusters using kind or minikube for development and testing purposes.
- Troubleshooting and Best Practices: To assist developers, the guide incorporates a dedicated troubleshooting section for common build, performance, and networking issues, alongside best practices for resource management, development efficiency, and security.
- Documentation Restructuring: As part of this update, I've removed two older documentation files, docs/developer-guide/Kmeshctl-usage/installation.md and docs/developer-guide/website/versioning-doc.md, streamlining the documentation structure.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
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.
Code Review
This pull request adds a comprehensive guide for installing and developing Kmesh on macOS, which is a valuable addition for developers on that platform. The guide is well-structured and covers various aspects from prerequisites to troubleshooting.
My review includes several suggestions to improve the clarity and correctness of the documentation, mainly focusing on formatting and command accuracy in the new macOS guide. These changes will enhance the readability and user experience for developers following the instructions.
```bash | ||
|
||
Memory: 8GB minimum (16GB recommended) | ||
CPU Cores: 4-6 cores | ||
Storage: 64GB (SSD recommended) | ||
Network: Shared Network | ||
``` |
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.
Using a bash
code block for a list of resource recommendations is semantically incorrect. For better readability and correctness, please use a standard markdown list.
For example:
- Memory: 8GB minimum (16GB recommended)
- CPU Cores: 4-6 cores
- Storage: 64GB (SSD recommended)
- Network: Shared Network
```bash | ||
Memory: 8GB minimum | ||
CPU: 4+ cores | ||
Disk: 64GB | ||
``` |
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.
curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-arm64 # ARM64 | ||
# curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64 # x86_64 | ||
|
||
sudo install minikube-linux-* /usr/local/bin/minikube |
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.
The use of a wildcard in sudo install minikube-linux-*
can be ambiguous and error-prone. It's clearer and safer to provide explicit, self-contained commands for each architecture. This also cleans up the downloaded binary after installation.
curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-arm64 # ARM64 | |
# curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64 # x86_64 | |
sudo install minikube-linux-* /usr/local/bin/minikube | |
# For ARM64 | |
curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-arm64 && sudo install minikube-linux-arm64 /usr/local/bin/minikube && rm minikube-linux-arm64 | |
# For x86_64 | |
# curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64 && sudo install minikube-linux-amd64 /usr/local/bin/minikube && rm minikube-linux-amd64 | |
|
||
--- | ||
|
||
**Next Steps**: Once your development environment is set up, proceed to the main [Quick Start Guide](../setup/quick-start.md) to install Kmesh in your Kubernetes cluster. |
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.
The link ../setup/quick-start.md
points to the current file, which will cause a full page reload. For a better user experience, you can link to the top of the page using an anchor link like #quick-start-guide
.
**Next Steps**: Once your development environment is set up, proceed to the main [Quick Start Guide](../setup/quick-start.md) to install Kmesh in your Kubernetes cluster. | |
**Next Steps**: Once your development environment is set up, proceed to the main [Quick Start Guide](#quick-start-guide) to install Kmesh in your Kubernetes cluster. |
```bash | ||
|
||
This comprehensive guide covers everything a macOS user needs to successfully develop with Kmesh, from initial setup through advanced configuration and troubleshooting. | ||
``` |
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.
Signed-off-by: AkarshSahlot <[email protected]> Signed-off-by: AkarshSahlot <[email protected]>
Signed-off-by: AkarshSahlot <[email protected]>
Signed-off-by: AkarshSahlot <[email protected]>
7458693
to
9c78f43
Compare
Description
This PR addresses the documentation gap for macOS developers working with Kmesh by adding a dedicated macOS installation section to the Quick Start guide. The addition provides platform-specific guidance for both Intel and Apple Silicon Mac users.
#216