Closed yanggangtony closed 6 months ago
@calvin0327 @lonelyCZ @Poor12 @RainbowMango
@yanggangtony Thanks for pointing this out.
Indeed, now we not support installing karmada on remote clusters. if user provides the cluster APIEndpoint or a kubeconfig secret, we should init a remoteClient with these message.
And there are two clients:
karmadaClinet
: connect to karmada controlplane
remoteClient
: connect to the target cluster to install karmada
If you're interested in it, you can assign this.
@calvin0327 Thanks for the quick response. I will make a pr to the
remoteClient's fuction.
/assign
Sorry for the late response . Recentely have lots of other works to to. Have no more time pay for the pr. 🥲🥲
Please provide an in-depth description of the question you have: I rough read the operator code. I found the operator/pkg/deinit.go 's remoteClient define.
and operator/pkg/init.go 's remoteClient define.
Its just initialized in condition
But in the next logic about the task execute loop. Its will immediate be called by tasks.. Like the init task
Also the deinit case is the same..
I want to know if is a known problem? Or If it is can be initialize like the
If its really a problem . I will assign and handle it.. Thanks.
What do you think about this question?: Karmada operator