Infrastructure Feature Support
Getting started
When a GitLab feature is released to Production, it can be released at one of these levels: Experiment, Beta, Generally Available. (See the product documentation for further details.)
The availability of a feature is closely related with our ability to support the feature on our SaaS Platforms.
These guidelines ensure that features in our Production environments can be operated by our Reliability teams to match the expected level of support.
Requesting and creating new GCP infrastructure resources
Please use the Sandbox Cloud GCP Group Project issue template to request new resources. After the GCP project is created, it can be configured as needed, this provides initial provisioning and IAM management. This provides basic resources and is available to anyone team-member.
As we make progress on Project Runway, we will encourage development teams to use Runway to provision new resources. Runway projects will include automated configuration and Runway provides many of the Infrastucture Readiness requirements as standard. Using Runway will make it easier and faster to promote new features into a Generally Available state in Production.
Severity levels for different product maturity
- Incidents for Experimental and Beta features are assigned as Severity 4
- Incidents for Generally Available features are assigned according to the incident severity table listed on the Incident Management page.
How to expedite features to General Availability
We are able to help expedite features to General Availability.
In order to expedite a prototype feature, on the epic tracking the work required to reach General Availability, include the label ~expedite_prototype.
Infrastructure leadership are subscribed to this label and will be notified that the intention is to expedite this feature.
Infrastructure leadership will confirm with the epic DRI if they are able to support this.
Epics with this label are visible in the Prototype Status epic board.
05571984)
