WIP: [release-4.21] SPLAT-2866: Added support to manage kube-cloud-config for vSphere in openshift-config-managed

[vr4manta]

SPLAT-2866

Changes

Enhanced the cluster-cloud-controller-manager-operator (CCCMO) to manage the openshift-config-managed/kube-cloud-config ConfigMap for vSphere platforms, migrating ownership from the Cluster Config Operator (CCO) to CCCMO. This enables CCCMO to:

1. Convert INI-format cloud configs to YAML
2. Apply transformations to add Infrastructure-derived values (vCenters, labels, networking)
3. Maintain a single source of truth for cloud configuration
4. Gate functionality behind the VSphereMultiVCenterDay2 feature gate

Notes

This PR is backporting the following PRs in relation to the vSphere multi vCenter day 2 support feature:

• SPLAT-2651: Added support to manage kube-cloud-config for vSphere in openshift-config-managed #442
• SPLAT-2792: Fixed issue where old vCenters not removed from new cloud config #469

Since the original PRs require changes to API and library-go, we need to make sure to update the references here to point to the release-4.21 variants to make sure we do not pull in new functionality.

[openshift-ci]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@vr4manta: This pull request references SPLAT-2866 which is a valid jira issue.

Details

In response to this:

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.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 4344a923-5be2-441a-94af-38eb93c4547f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[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 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.

Details

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

[vr4manta]

/test all

[vr4manta]

/pipeline required

[openshift-merge-bot]

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-nutanix-ovn
/test e2e-aws-ovn
/test e2e-aws-ovn-upgrade

[vr4manta]

/retest

[openshift-ci]

@vr4manta: 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/regression-clusterinfra-vsphere-ipi-ccm	92d6b51	link	false	/test regression-clusterinfra-vsphere-ipi-ccm

Full PR test history. Your PR dashboard.

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