🌱 [WIP] [Do not review] Debugging Objects with Changed Resource Versions issue

[arshadd-b]

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[k8s-ci-robot]

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

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

[k8s-ci-robot]

This PR is currently missing an area label, which is used to identify the modified component when generating release notes.

Area labels can be added by org members by writing /area ${COMPONENT} in a comment

Please see the labels list for possible areas.

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.

[arshadd-b]

/pull-cluster-api-e2e-blocking-main

[arshadd-b]

/test pull-cluster-api-e2e-blocking-main

[arshadd-b]

/test pull-cluster-api-e2e-blocking-main

[arshadd-b]

/test pull-cluster-api-e2e-blocking-main

[arshadd-b]

/test pull-cluster-api-e2e-blocking-main

[arshadd-b]

/test pull-cluster-api-e2e-blocking-main

[arshadd-b]

/test pull-cluster-api-e2e-blocking-main

[arshadd-b]

/test pull-cluster-api-e2e-blocking-main

[arshadd-b]

/test pull-cluster-api-e2e-blocking-main

[blind3dd]

@arshadd-b I think we are either going to need to adjust the test logic to include internal and externally scoped conversions to have full test suite, ref kubernetes-sigs/controller-runtime#3335, or with dedicated submodule for conversion that is properly scoped and separate, that could make tests suites easier per module with clear separation.
Question is probably of how far are we between internal and external conversion logic and apis versions having in mind cluster-lifecycle and controller-runtime dependency.

[blind3dd]

I do not know how to make a reference to
https://github.com/kubernetes-sigs/cluster-api/pull/12820
and
https://github.com/kubernetes-sigs/controller-runtime/issues/810
and not sure if have rights for doing so.

[arshadd-b]

/test pull-cluster-api-e2e-blocking-main

[arshadd-b]

/test pull-cluster-api-e2e-blocking-main

[arshadd-b]

/test pull-cluster-api-e2e-blocking-main

[arshadd-b]

/test pull-cluster-api-e2e-blocking-main

[arshadd-b]

/test pull-cluster-api-e2e-blocking-main

[arshadd-b]

/test pull-cluster-api-e2e-blocking-main

[arshadd-b]

/test pull-cluster-api-e2e-blocking-main

[arshadd-b]

/test pull-cluster-api-e2e-blocking-main

[k8s-ci-robot]

@arshadd-b: 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
pull-cluster-api-e2e-blocking-main	b8b7fdb	link	true	/test pull-cluster-api-e2e-blocking-main

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.