Use multicluster.Aware in provider.Start function signature

[embik]

Summary

This is not necessarily something to merge, more of a RFC. I realized we were only using Engage in the provider startup, and it seemed to me it would be a nice idea to use multicluster.Aware instead of the whole mcmanager.Manager kitchen sink. This way, you can use the provider in more custom scenarios (in specific, @xrstf and I are currently re-thinking the api-syncagent to move it to multicluster-runtime, and we might not even use the mcmanager.Manager directly).

Any thoughts on this?

What Type of PR Is This?

/kind cleanup
/kind api-change

Related Issue(s)

Fixes #

Release Notes

Replace `mcmanager.Manager` with `multicluster.Aware` in `apiexport.(p *Provider).Start` function signature

[embik]

/hold

for discussion.

[xrstf]

/approve

[kcp-ci-bot]

LGTM label has been added.

Git tree hash: 0b84ba0deb74a1be1baa673cd74d0178978d784c

[kcp-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xrstf

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [xrstf]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[xrstf]

We turned out to use the mcmanager after all, so this PR might not be needed anymore.

[embik]

/close

for now. We will probably implement something similar once kubernetes-sigs/multicluster-runtime#62 is merged.

[kcp-ci-bot]

@embik: Closed this PR.

In response to this:

/close

for now. We will probably implement something similar once kubernetes-sigs/multicluster-runtime#62 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.