do we have plan to support different k8s vendor

[hchenxa]

/kind feature

Describe the solution you'd like
[A clear and concise description of what you want to happen.]

do we have plan to support the different k8s vendor like ICP or some others and the user cases was:

1. If I already have a ICP cluster, I want to use cluster api to deploy the ICP and use the MCM to manage the provided ICP cluster.
2. If I already have a ICP cluster, I can use cluster api to deploy other vendor k8s but I want to use ICP MCM to manage those cluster.
3. If I did not have a ICP cluster, but I want to use ICP to have some IBM application running, so I may use cluster api to deploy an ICP cluster and deploy the IBM application(from ICP catalog) running on ICP k8s.

cc @gyliu513 @xunpan
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

[xunpan]

This project has no plan for doing this.

It is traced in cluster-api kubernetes-sigs/cluster-api#853

[jichenjc]

kubernetes-sigs/cluster-api#997 is on the way
I think we need defer this to align with v1alpha2

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.