configuable timeoutKubeconfigReady

[xunpan]

/kind feature

Describe the solution you'd like
For deploying a different release of Kubernetes, e.g. ICP, the default time out for 20m may be not enough in waiting for cluster ready.

It should be better configurable by command line options.

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

[wanghh2000]

@xunpan You want a parameter like "--timeoutForWaitingTargetCluster 30" from Clusterctl to update timeoutKubeconfigReady in case creating a cluster is very long process. Right?

[gyliu513]

@wanghh2000 @xunpan You can post a PR like this kubernetes-sigs/cluster-api-provider-openstack#262 which was fixed by @jichenjc for OpenStack.

[wanghh2000]

@gyliu513
Shouldn't the timeout be a common feature from clusterctl for all provider projects?
Do you mean that add a timeout in each provider to handle instead of a common clusterctl parameter?

[jichenjc]

that's doable, It will increase a lot of options since we have a set of timeout options...
and our provider is running in container (statefulset), we need transfer that from clusterctl exec file to the container as well

[wanghh2000]

@jichenjc OK, I will reference what you did.

[vincepri]

/lifecycle active