CORENET-6229: Use networking.advertiseAddress for CNO apiserver override for IBMCloud PlatformType

[bradbehle]

What this PR does / why we need it:
This tells the cluster network operator to use the HostedCluster Spec.Networking.APIServer.AdvertiseAddress and Port when connecting to the apiserver on clusters in IBM Cloud. This is needed so that OVN (and probably other components) does not try to use the external apiserver URLs, which might either be blocked by firewall rules or using named certificates which OVN doesn't handle.

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes # https://issues.redhat.com/browse/CORENET-6229

Checklist

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.
• This change includes docs.
• This change includes unit tests.

[openshift-ci-robot]

@bradbehle: This pull request references CORENET-6229 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 story to target the "4.20.0" version, but no target version was set.

Details

In response to this:

What this PR does / why we need it:
This tells the cluster network operator to use the HostedCluster Spec.Networking.APIServer.AdvertiseAddress and Port when connecting to the apiserver on clusters in IBM Cloud. This is needed so that OVN (and probably other components) does not try to use the external apiserver URLs, which might either be blocked by firewall rules or using named certificates which OVN doesn't handle.

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes # https://issues.redhat.com/browse/CORENET-6229

Checklist

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.
• This change includes docs.
• This change includes unit tests.

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]

Hi @bradbehle. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[csrwng]

/ok-to-test

[cwbotbot]

Test Results

e2e-aws

• Status: ✅ PASS
• Started: 2025-08-01T17:44:59Z
• View Job
• View Job History

e2e-aks

• Status: ✅ PASS
• Started: 2025-08-01T20:09:09Z
• View Job
• View Job History

[rtheis]

/ok-to-test

[bryan-cox]

/approve

[rtheis]

/lgtm

[rtheis]

/ok-to-test

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bradbehle, bryan-cox, rtheis

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [bryan-cox]

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 4882e8f and 2 for PR HEAD ae8dc35 in total

[rtheis]

/retest-required
/ok-to-test

[bryan-cox]

e2e-aks is flaky at the moment due to a new test added yesterday. We are working to fix it though.

[rtheis]

/retest