Promote Helm Chart Registry from Beta to General Availability (GA)

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

The GitLab Helm Chart Registry has been in beta for some time and has reached maturity. With the recent resolution of the 1k chart display limit issue (the last major architectural blocker), this feature is ready for promotion to General Availability status.

Background

The Helm Chart Registry feature has been available in beta, providing GitLab users with the ability to store, manage, and distribute Helm charts directly within their GitLab projects. This feature has proven stable and valuable to the community.

Problem Statement

The Helm Chart Registry remains in beta status despite:

  • Stable functionality and user adoption
  • Resolution of major architectural issues
  • The recent fix for the 1k chart display limit (previously the primary blocker for GA)

Keeping this feature in beta creates uncertainty for enterprise users who may be hesitant to rely on beta features for production workloads.

Proposal

Promote the Helm Chart Registry feature to General Availability (GA) status.

Benefits

  • Increased confidence: Users can rely on this feature for production use cases
  • Enhanced adoption: Enterprise customers are more likely to adopt GA features
  • Clear support expectations: GA status provides clearer SLA and support commitments
  • Feature completeness: Signals that the feature has reached maturity

Success Criteria

  • Feature documentation updated to remove beta warnings
  • Any remaining beta flags or feature flags removed from codebase
  • Support documentation updated to reflect GA status
  • Release notes include GA announcement
  • Performance benchmarks verified at scale

Technical Considerations

With the 1k chart limit issue resolved, the major architectural concerns have been addressed. The feature should undergo final validation to ensure:

  • Performance at scale meets production requirements
  • Error handling is robust
  • Monitoring and observability are adequate for production support

Documentation Updates Required

  • Update feature documentation to remove beta designation
  • Update API documentation if applicable
  • Update user guides and tutorials
  • Add any missing production-ready configuration examples

Rollout Plan

Suggest a phased approach:

  1. Internal testing and validation
  2. Documentation updates
  3. Announcement in release notes
  4. Monitor adoption and feedback post-GA

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited by 🤖 GitLab Bot 🤖