OCPBUGS-44230: Add C4A instance types

[barbacbd]

** Add the C4A instance type for GCP. This instance type requires a disk type
of hyperdisk balanced. It is currently under PREVIEW.

** Vendor updates for GCP Machine API Provider in 4.17

This is a manual backport for #9122

[openshift-ci-robot]

@barbacbd: This pull request references Jira Issue OCPBUGS-44230, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-39586 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

** Add the C4A instance type for GCP. This instance type requires a disk type
of hyperdisk balanced. It is currently under PREVIEW.

** Vendor updates for GCP Machine API Provider in 4.17

This is a manual backport for #9122

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.

[barbacbd]

/jira refresh

[openshift-ci-robot]

@barbacbd: This pull request references Jira Issue OCPBUGS-44230, which is invalid:

• expected dependent Jira Issue OCPBUGS-39586 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from barbacbd. For more information see the Kubernetes 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 @r4f4

[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/e2e-gcp-secureboot	fd8b02f	link	false	/test e2e-gcp-secureboot
ci/prow/e2e-gcp-ovn	fd8b02f	link	true	/test e2e-gcp-ovn
ci/prow/e2e-gcp-ovn-xpn	fd8b02f	link	false	/test e2e-gcp-ovn-xpn
ci/prow/e2e-gcp-ovn-byo-vpc	fd8b02f	link	false	/test e2e-gcp-ovn-byo-vpc

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.