Add post-join actions after child cluster joins in parent cluster successfully. about clusternet HOT 2 OPEN

I wonder whether it is feasible to use a predefined Subscription that matches all clusters (or a group of selected clusters with specific labels, name prefixes, etc) to help deploy all needed dependencies/initializations (aka post-install). On this occasion, such a Subscription is working like a DaemonSet. This is exactly how CNI plugins are initialized/installed for any new joined nodes.

Clusternet has the capability to deploy any objects to matching child clusters. We could follow the same principle of CNI installation to help us finish all the post-join actions for child clusters.

from clusternet.

After discussion, we thought it would be better to add a condition for ManagedCluster to indicate the result/status of post-join steps. And this condition could be used to represent whether the clusters are ready/not-ready for scheduling.

For our predefined Subscription objects, we could add tolerations for scheduling.

Here there are several remaining issues to be considered.

• Backwards compatibility. How should we apply those predefined Subscription objects to existing already-joined clusters?
• The orders. What would happen if we add a new Subscription object for post-join actions?
• Will multiple such Subscription objects result in action conflicts, cluster status flapping, etc?

from clusternet.