Checklist

• I did not find a related open enhancement request.
• I understand that enhancement requests filed in the GitHub repository are by default low priority.
• If this request is time-sensitive, I have submitted a corresponding issue with GCP support.

Describe the feature or resource

What happened?

When trying to label a GKE cluster via the ContainerCluster resource in Config Connector, the field resourceLabels is not available.
In the generated Go client (container.cnrm.cloud.google.com/v1beta1) and in the CRD, there is no field for cluster-level labels.

What did you expect to happen?

The ContainerCluster spec should expose the resourceLabels field (as supported by the GKE API) so that cluster-level labels can be declared and managed declaratively via Config Connector.

Additional information

• Labels at the node level are supported via spec.nodeConfig.labels, but cluster-level resource labels are missing.
• This limits our ability to enforce consistent cost-allocation and governance tags across GKE clusters declaratively.

Importance

No response