[Docs] Use $RELEASE_NAME in helm docs instead of hardcoded skypilot

[romilbhardwaj]

Tested (run the relevant ones):

• Code formatting: install pre-commit (auto-check on commit) or bash format.sh
• Any manual or new tests for this PR (please specify below)
• All smoke tests: /smoke-test (CI) or pytest tests/test_smoke.py (local)
• Relevant individual tests: /smoke-test -k test_name (CI) or pytest tests/test_smoke.py::test_name (local)
• Backward compatibility: /quicktest-core (CI) or pytest tests/smoke_tests/test_backward_compat.py (local)

[gemini-code-assist]

Summary of Changes

Hello @romilbhardwaj, I'm Gemini Code Assist¹! 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!

This pull request enhances the Helm deployment documentation for the SkyPilot API server by introducing a dynamic release name. Instead of hardcoding 'skypilot' in all helm upgrade --install commands, the documentation now uses the $RELEASE_NAME variable. This modification provides greater flexibility for users who wish to customize their Helm release names during deployment, improving the overall clarity and reusability of the provided commands.

Highlights

• Documentation Update: Replaced the hardcoded Helm release name 'skypilot' with the $RELEASE_NAME environment variable in the API server deployment documentation.
• Improved Flexibility: This change allows users to define their own Helm release name, making the deployment instructions more adaptable and user-friendly.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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

1. 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. ↩

[gemini-code-assist]

Code Review

This pull request updates the Helm deployment documentation by replacing the hardcoded skypilot release name with the $RELEASE_NAME variable in various helm upgrade commands. This change improves the documentation's consistency and makes the commands more user-friendly and less error-prone, as users can now define their release name once and reuse it. The changes are correct and have been applied thoroughly across the api-server-admin-deploy.rst file. The PR is a good improvement to the documentation.

[aylei]

LGTM, thanks @romilbhardwaj !