Integrate internal/matchers into Komega style test abstraction in Controller Runtime

[killianmuldoon]

User Story

As a developer I would like to have a consistent abstract toolset to quickly write unit tests in Cluster API.

Detailed Description

The matchers package added in #5259 brings generic matching to Cluster API objects and makes it easier to match only on required fields at test time. In controller runtime a similar approach with some differences - called Komega in its current iteration at kubernetes-sigs/controller-runtime#1364

These approaches could be integrated inside controller runtime to bring generic json based matching with the Komega abstraction over the controller runtime client to reduce the amount of boiler plate code involved in writing these tests.

/kind feature
/area testing

[vincepri]

Should we open an issue in Controller Runtime as well?

[killianmuldoon]

Should we open an issue in Controller Runtime as well?

Will do - I'm doing an initial spec test to get a feel for what the integration would look like today, and then I'll put a PR up over there.

[vincepri]

/milestone Next

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[killianmuldoon]

c/f kubernetes-sigs/controller-runtime#1767

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[killianmuldoon]

c/f kubernetes-sigs/controller-runtime#1833

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.

[sbueringer]

/reopen
until CR PR is merged
/remove-lifecycle rotten

[k8s-ci-robot]

@sbueringer: Reopened this issue.

In response to this:

/reopen
until CR PR is merged
/remove-lifecycle rotten

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.

[killianmuldoon]

/close
kubernetes-sigs/controller-runtime#1833 is merged.

[k8s-ci-robot]

@killianmuldoon: Closing this issue.

In response to this:

/close
kubernetes-sigs/controller-runtime#1833 is merged.

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.

[sbueringer]

@killianmuldoon Should we track it somewhere that we actually use it? :)