You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to be added:
If we don't consider that there is only single side network communication from member cluster to karmada control plane. We can enable karmadactl get to support pull mode. There are two way to do this.
Using --cluster-kubeconfig and --cluster-context.
Add access secret of member cluster of pull mode to karmada control plane.
Why is this needed:
This command can be used with the migrate command, we also add a field that can check if the workload are managed by karmada through karmadactl get.
The text was updated successfully, but these errors were encountered:
What would you like to be added:
If we don't consider that there is only single side network communication from member cluster to karmada control plane. We can enable
karmadactl get
to supportpull mode
. There are two way to do this.--cluster-kubeconfig
and--cluster-context
.pull mode
to karmada control plane.Why is this needed:
This command can be used with the
migrate
command, we also add a field that can check if the workload are managed by karmada throughkarmadactl get
.The text was updated successfully, but these errors were encountered: