[Process] Clarify Stability of Resources Served as v1beta1 but Labeled Alpha

[fkc1e100]

Context

There is confusion regarding the stability and support status of resources that are served as v1beta1 (and often stored as v1beta1) but carry the cnrm.cloud.google.com/stability-level: alpha label.

This mixed signaling leads to:

1. Uncertainty on whether these resources are production-ready.
2. Contradictions in policy/compliance checks that rely on the stability-level label.

Affected Resources (Examples)

The following resources have been identified as having v1beta1 in their spec.versions (often as the storage version) while maintaining the alpha stability label:

• Tags: TagsTagKey, TagsTagValue, TagsTagBinding
• BigQuery: BigQueryRoutine
• ConfigController: ConfigControllerInstance
• VertexAI: VertexAIMetadataStore
• (And potentially others like DataCatalogTaxonomy, DataformRepository)

Goals

The goal of this issue is to establish a clear process for handling these discrepancies and to determine the correct path forward for the affected resources.

Discussion Points

1. Blockers for Promotion: Are there technical reasons or known bugs preventing these resources from being marked as stable (or at least beta) in the stability label?
2. Alignment Process: Should we systematically align the stability-level label with the served v1beta1 version?
3. Documentation: If these resources are indeed "beta" quality but labeled "alpha" for other reasons, how should this be documented?

Proposed Action Items

• Discuss and decide on a policy for aligning stability labels with CRD versions.
• For the listed resources, determine if they can be immediately promoted to beta or stable status.
• If a resource must remain alpha despite being v1beta1, document the specific reasons.
• Create PR(s) to update labels or documentation based on the outcome of this discussion.