CORS-3190: GCP: Add load balancer info to cluster infra

[barbacbd]

** After the internal and external load balancer ip addresses are output from terraform, add this data to the cluster infrastructure manifest. This will ensure that the data is present in the cluster.

CORS-3190: Spike to generalize the addition of load balancer information to platform status fields in the infrastructure CR.

[openshift-ci-robot]

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

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the spike to target the "4.16.0" version, but no target version was set.

In response to this:

** After the internal and external load balancer ip addresses are output from terraform, add this data to the cluster infrastructure manifest. This will ensure that the data is present in the cluster.

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]

/cc @patrickdillon @sadasu

[openshift-ci-robot]

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

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the spike to target the "4.16.0" version, but no target version was set.

In response to this:

** After the internal and external load balancer ip addresses are output from terraform, add this data to the cluster infrastructure manifest. This will ensure that the data is present in the cluster.

CORS-3190: Spike to generalize the addition of load balancer information to platform status fields in the infrastructure CR.
CORS-3166: Used to backport to 4.15.

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-robot]

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

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the spike to target the "4.16.0" version, but no target version was set.

In response to this:

** After the internal and external load balancer ip addresses are output from terraform, add this data to the cluster infrastructure manifest. This will ensure that the data is present in the cluster.

CORS-3190: Spike to generalize the addition of load balancer information to platform status fields in the infrastructure CR.
CORS-3166: Used to backport to 4.15.

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-robot]

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

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the spike to target the "4.16.0" version, but no target version was set.

In response to this:

** After the internal and external load balancer ip addresses are output from terraform, add this data to the cluster infrastructure manifest. This will ensure that the data is present in the cluster.

CORS-3190: Spike to generalize the addition of load balancer information to platform status fields in the infrastructure CR.

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.

[sadasu]

/lgtm

[barbacbd]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: barbacbd

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [barbacbd]

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

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 585a01a and 2 for PR HEAD 48cbc4a in total

[sadasu]

This has to be APILoadBalancerIPs: apiLbs.

[sadasu]

/lgtm

[jhixson74]

/cc

[openshift-ci]

@barbacbd: The following test 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/okd-e2e-aws-ovn-upgrade	a2713ff	link	false	/test okd-e2e-aws-ovn-upgrade

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/test-infra repository. I understand the commands that are listed here.

[barbacbd]

/cherry-pick release-4.15

[openshift-cherrypick-robot]

@barbacbd: new pull request created: #7903

In response to this:

/cherry-pick release-4.15

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/test-infra repository.