Remove scheme validation & refac apiexport

[EpicStep]

Summary

I removed the validation for the scheme option since the Options docs say it uses the default scheme from client-go. If this behavior changed after the last PR, please let me know and I’ll update the docs. Also did a bit of refactoring.

What Type of PR Is This?

/kind cleanup

Related Issue(s)

Release Notes

NONE

[kcp-ci-bot]

[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 xrstf for approval. For more information see the Kubernetes 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

[kcp-ci-bot]

Hi @EpicStep. Thanks for your PR.

I'm waiting for a kcp-dev 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/test-infra repository.

[embik]

/ok-to-test

[embik]

/kind cleanup

[mjudeikis]

This is open to discussion. The problem is that if one uses a dedicated schema object when initialising this code, it will not work as the schemas will not match. So, should we be explicit here and ask the user to provide the schema, or are we ok?