Operators should support configuring user tags(AWS, Azure, GCP) and labels(GCP) in their API(linked Custom Resource) in such cases where operators reconciles the GCP resources it manages and updates the state of the resources to as defined in OpenShift by user.
Since OpenShift currently doesn't support modifying or deleting the tags and labels added to resources, reconciliation could result in reverting the tags, labels modifications done by user through external interface.
Hence by extending the operator linked custom resource to support tags, labels the desired state could be updated and maintained as required by the user.