Is your feature request related to a problem? Please describe.
NVCF self-managed users need a public roadmap that explains which capabilities and services are available in source, which are currently delivered only as NGC artifacts, and what work remains before those NGC-delivered services can be fully opened after proprietary references are removed.
Today, several required services are present as deployable artifacts in the self-managed stack but are not yet fully available as public source. There is not yet one public tracking issue that ties these OSS-readiness gaps together.
Describe the solution you'd like
Create and maintain a public roadmap issue for the first wave of NVCF OSS-readiness and self-managed capability work.
The roadmap should track:
- OSS readiness for NVCT API, NVCF API, ICMS API, ESS API, and NAK/API Keys.
- Self-managed support for Autoscaler and BYOO.
- Multi-cluster one-click validation.
- Multiple account support.
- PKI support for multi-cluster QUIC transport.
- LLM Gateway design documentation.
Describe alternatives you've considered
We could track each item only as a standalone issue, but that makes it harder for users and contributors to understand sequencing, dependencies, and overall self-managed readiness.
Additional context
Suggested acceptance criteria:
- Each roadmap item has an owner, linked child issue, target release or status, and public disposition.
- Items not intended for public OSS release are documented with rationale and supported contribution path.
- User-facing docs link to the roadmap where appropriate.
- Maintainers review stale handling and apply
lifecycle-frozen if this issue should remain open as a standing roadmap.
Tracking issues:
Is your feature request related to a problem? Please describe.
NVCF self-managed users need a public roadmap that explains which capabilities and services are available in source, which are currently delivered only as NGC artifacts, and what work remains before those NGC-delivered services can be fully opened after proprietary references are removed.
Today, several required services are present as deployable artifacts in the self-managed stack but are not yet fully available as public source. There is not yet one public tracking issue that ties these OSS-readiness gaps together.
Describe the solution you'd like
Create and maintain a public roadmap issue for the first wave of NVCF OSS-readiness and self-managed capability work.
The roadmap should track:
Describe alternatives you've considered
We could track each item only as a standalone issue, but that makes it harder for users and contributors to understand sequencing, dependencies, and overall self-managed readiness.
Additional context
Suggested acceptance criteria:
lifecycle-frozenif this issue should remain open as a standing roadmap.Tracking issues: