Propagate an application without specify all the resources

[IonBoleac]

Is there a method for propagating an application between clusters without specifying wich resources should be propagated? For example, can an app be propagated using the namespace where it's deployed?

[XiShanYongYe-Chang]

It sounds simple for users. How does this application work (actually, we have also been thinking about how to represent the application)? The existing feature that can take effect may be the dependency propagation feature, which can propagate the resources associated with the workload to the target cluster, and this following relationship can be defined by the user through the resource interpreter.

[IonBoleac]

Transitioning a microservices application from a single-cluster to a multi-cluster environment can indeed be complex.
I make an example to explain myself easily.

I have a microservices application, like this Google app: https://raw.githubusercontent.com/GoogleCloudPlatform/microservices-demo/v0.3.7/release/kubernetes-manifests.yaml, which is deployed in a single-cluster system. If I want to transfer this app to a cross-cluster system I must create a PropagationPolicy for every resource. So, creating a PropagationPolicy for each resource manually is time-consuming and prone to errors. It's a little "pain".

I think that developing a new Custom Resource Definition (CRD) that simplifies the deployment process across multiple clusters is quite innovative. Such a CRD could act as a high-level abstraction, allowing users to specify the target clusters and namespaces, thereby streamlining the propagation process. This approach would not only reduce the manual overhead but also minimize the risk of configuration mistakes. It's a solution that could potentially benefit many organizations looking to scale their applications efficiently in a cross-cloud-native ecosystem.

@XiShanYongYe-Chang what do you thinks?