Pointing two helm charts from nvcf-ncp-staging to the gated selfhosted-ga team - docs 0.6.1
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- kubernetes
- Domain
- devops, documentation
Research direction
Open the v0.6.1 manifest at the control-plane Helm charts section and inspect the entries for helm-nvcf-llm-api-gateway and helm-nvcf-llm-request-router. Update both references from nvcf-ncp-staging to selfhosted-ga, then verify the published documentation points customers to the reachable team.
Written by the indexing model from the issue text.
Description
In version 0.6.1 - https://docs.nvidia.com/nvcf/v0.6.1/manifest#control-plane-helm-charts
The following charts are pointing to nvcf-ncp-staging, and should point to selfhosted-ga
helm-nvcf-llm-api-gateway
helm-nvcf-llm-request-router
Report incorrect documentation
The following charts are pointing to nvcf-ncp-staging, and should point to selfhosted-ga
helm-nvcf-llm-api-gateway
helm-nvcf-llm-request-router
Location of incorrect documentation
https://docs.nvidia.com/nvcf/v0.6.1/manifest#control-plane-helm-charts
Describe the problems or issues found in the documentation
Customers cannot reach nvcf-ncp-staging anymore but they can reach the selfhosted-ga team which also holds the containers for these charts.
Steps taken to verify documentation is incorrect
List any steps you have taken:
- Verified the charts are in selfhosted-ga
Suggested fix for documentation
Renamed the team from nvcf-ncp-staging to selfhosted-ga
- Dominant language
- Go
- Stars
- 218
- Forks
- 72
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 415
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/nvcf
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
good-first-issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·