CORS-4041: Remove the TagManager from the GCP Custom Endpoints

[barbacbd]

** The tag manager or tagging does appear to have a service in GCP, but this particular one is NOT used. Instead openshift uses the cloud resource manager service, so there is no need to support Tag Manager.
** The origin of the changes stemmed from https://issues.redhat.com/browse/CORS-2389. The [tech-preview] feature gate was added during the openshift-4.19 release. The TagManager value is removed during the openshift-4.20 release. The feature as a whole was not officially released during openshift-4.19, and the openshift installer is currently the only user for this feature, so the impact is very low.

[openshift-ci-robot]

@barbacbd: This pull request references CORS-4041 which is a valid jira issue.

In response to this:

** The tag manager or tagging does appear to have a service in GCP, but this particular one is NOT used. Instead openshift uses the cloud resource manager service, so there is no need to support Tag Manager.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Hello @barbacbd! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: barbacbd
Once this PR has been reviewed and has the lgtm label, please assign joelspeed for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[barbacbd]

/cc @JoelSpeed

[JoelSpeed]

When did this API ship initially? What is happening in the cluster today for folks who already specify this value? What will happen when we drop support? Do you have any idea how many people this change might affect?

[JoelSpeed]

What happens to existing resources when you remove this value? This API has shipped so to be able to remove a value we would need to be certain that it won't break existing resources.

Can you please add a ratcheting validation test (see tests/README.md) to make sure this change will allow existing resources with this value set to:

• Update the field itself to remove the bad value
• Update the field value to add a new value
• Update other fields around the field while leaving an invalid value in place

[openshift-ci-robot]

@barbacbd: This pull request references CORS-4041 which is a valid jira issue.

In response to this:

** The tag manager or tagging does appear to have a service in GCP, but this particular one is NOT used. Instead openshift uses the cloud resource manager service, so there is no need to support Tag Manager.
** The origin of the changes stemmed from https://issues.redhat.com/browse/CORS-2389. The [tech-preview] feature gate was added during the openshift-4.19 release. The TagManager value is removed during the openshift-4.20 release. The feature as a whole was not officially released during openshift-4.19, and the openshift installer is currently the only user for this feature, so the impact is very low.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@barbacbd: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/verify-crd-schema	0cd9658	link	true	/test verify-crd-schema
ci/prow/e2e-aws-serial-techpreview-2of2	0cd9658	link	true	/test e2e-aws-serial-techpreview-2of2

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.