Ibmcloud router

[libesz]

What this PR does / why we need it:

When HCP contains router publish strategy for the
master services, IBM Cloud platform implementation
will take care of the proper exposure of the
services, without using the actual cluster Router
(similar implementation to Azure). That is, CPO should
not create any LoadBalancer or actual router deployment
as part of reconciling the HCP.
The current change also makes the migration from NodePort
services backward compatible, for existing clusters.
That is, the NodePort services will remain as is
(they are not converted to regular ClusterIP services,
resulting in permanently losing the reserved nodeports)
allowing existing external clients (e.g. kubelet,
master proxy) to work as before, until they are also
upgraded.

The expected behavior is to:

• Do not manage any ingress component (LB Svc, Router)
• Keep NodePort master services (if they are already existing)
• (Re)configure node agents (e.g. connectivity) to use 443 as server port

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 #

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: libesz
Once this PR has been reviewed and has the lgtm label, please assign bryan-cox 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

[openshift-ci]

Hi @libesz. 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.

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.

[rtheis]

Please open this PR on the main branch.

[libesz]

There it is: #6199