Skip to content

fix: add headers to different helm install options #205

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.

Sign up for GitHub

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
merged 1 commit into from
May 11, 2025
Merged

fix: add headers to different helm install options #205

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/getting-started-kubernetes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,7 +110,9 @@ Update Helm repositories

helm repo update

----------------------------------------------------------------------------
Install Network Operator from the NVIDIA NGC chart using the default values:
----------------------------------------------------------------------------

.. code-block:: bash
:substitutions:
Expand All @@ -127,7 +129,9 @@ View deployed resources

kubectl -n nvidia-network-operator get pods

Install the Network Operator from the NVIDIA NGC chart using custom values:
------------------------------------------------------------------------------
OR install the Network Operator from the NVIDIA NGC chart using custom values:
------------------------------------------------------------------------------

.. warning:: Since several parameters should be provided when creating custom resources during operator deployment, it is recommended to use a configuration file. While it is possible to override the parameters via CLI, we recommend to avoid the use of CLI arguments in favor of a configuration file.

Expand Down